On Sat, 26 Jan 2013, Jeff Lake wrote:
They probably have been packaged as RPM's yet if that is the case, You will need to compile from source
Sorry, but that isn't what the message says. They have been packaged into RPMs and placed into a testing repository. The question is which testing repository, since a standard yum command can't retrieve these RPMs.
This is particularly frustrating, since F18 was released with Postgresql 9.2.x, and PostGIS 1.5.x, the latter not being able to function with the former.
If you had data and projects running on F17 on Postgresql 9.1.x and PostGIS 1.5.x, and accepted a default upgrade from F17 to F18, you would be seriously stuck.
As it is, I have three machines, only one of which that I've migrated to F18 from F17.
So, I'm not that stuck.
But I would like to know where the testing RPMs are so that my data and projects are current across the three machines.
Jeff Lake MichiganWxSystem AllisonHouse GRLevelXStuff
Max Pyziur pyz@brama.com
On 1/26/2013 10:12, Max Pyziur wrote: On Sat, 26 Jan 2013, Devrim GÜNDÜZ wrote:
Hi, On Thu, 2013-01-24 at 15:42 -0500, Max Pyziur wrote: This is a known issue, and there is already a bugzilla entry about this. I hope to fix it in a few days, by updating GeOS to 3.3.7 and PostGIS to 2.0.2. I'm sure that there are for more than myself who appreciate these efforts. Looking forward to the new releases. Pushed updates:https://admin.fedoraproject.org/updates/player-3.0.2-24.fc18,gdal-1.9.1-15.f... a15a0e72ae05f17db
If you have a chance go test the packages, please do. They will be available in the next 7 days or so, unless 2 people give +1 before then. I've tried finding the packages in the following way: yum --enablerepo=updates-testing update gd\* postg\* geos\* gras\* None of the versions of these packages appear. Is there an alternative way of getting them and installing them? Regards, Thanks. Max Pyziur pyz@brama.com
postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Am 26.01.2013 17:28, schrieb Max Pyziur:
On Sat, 26 Jan 2013, Jeff Lake wrote:
They probably have been packaged as RPM's yet if that is the case, You will need to compile from source
Sorry, but that isn't what the message says. They have been packaged into RPMs and placed into a testing repository. The question is which testing repository, since a standard yum command can't retrieve these RPMs
what is a "standard yum command" for you? sorry but you should be specific which such things!
for me it is "yum clean metadata && yum --enablerepo=updates-testing upgrade" or "yum --enablerepo=updates-testing update package1 package2..."
Am 26.01.2013 17:32, schrieb Reindl Harald:
Am 26.01.2013 17:28, schrieb Max Pyziur:
On Sat, 26 Jan 2013, Jeff Lake wrote:
They probably have been packaged as RPM's yet if that is the case, You will need to compile from source
Sorry, but that isn't what the message says. They have been packaged into RPMs and placed into a testing repository. The question is which testing repository, since a standard yum command can't retrieve these RPMs
what is a "standard yum command" for you? sorry but you should be specific which such things!
for me it is "yum clean metadata && yum --enablerepo=updates-testing upgrade" or "yum --enablerepo=updates-testing update package1 package2..."
additionally there is the koji buildserver http://koji.fedoraproject.org/koji/buildinfo?buildID=380648
you have a search box right on top
On Sat, 26 Jan 2013, Reindl Harald wrote:
Am 26.01.2013 17:28, schrieb Max Pyziur:
On Sat, 26 Jan 2013, Jeff Lake wrote:
They probably have been packaged as RPM's yet if that is the case, You will need to compile from source
Sorry, but that isn't what the message says. They have been packaged into RPMs and placed into a testing repository. The question is which testing repository, since a standard yum command can't retrieve these RPMs
what is a "standard yum command" for you? sorry but you should be specific which such things!
for me it is "yum clean metadata && yum --enablerepo=updates-testing upgrade" or "yum --enablerepo=updates-testing update package1 package2..."
yum --enablerepo=updates-testing update gd* postg* geos* gras*
is the command that I used, 24 hours after the announcement.
fyi,
Max Pyziur pyz@brama.com
-
Max Pyziur -
Reindl Harald