Am 11.03.2013 01:02, schrieb Max Pyziur:
> If you follow the discussions on postgis-users, there are pending issues
> elsewhere in fedoraproject, that have held
> up (don't know why) software more fundamental to the stack.
becasue fedora tends to be first and not to be best since
a few years wh
On Sun, 10 Mar 2013, Michael Cronenworth wrote:
On 03/10/2013 06:27 PM, Max Pyziur wrote:
However, the frustration comes more into play, seeing that in F18
PostGIS 1.5 is distributed along with PostgreSQL 9.2. If you look at the
PostGIS Wiki, it says that two will not work together.
Compla
Am 11.03.2013 00:43, schrieb Michael Cronenworth:
> On 03/10/2013 06:27 PM, Max Pyziur wrote:
>> However, the frustration comes more into play, seeing that in F18
>> PostGIS 1.5 is distributed along with PostgreSQL 9.2. If you look at the
>> PostGIS Wiki, it says that two will not work together.
On 03/10/2013 06:27 PM, Max Pyziur wrote:
However, the frustration comes more into play, seeing that in F18
PostGIS 1.5 is distributed along with PostgreSQL 9.2. If you look at the
PostGIS Wiki, it says that two will not work together.
Complaining about it here will not get it fixed.
In the fu
On Sun, 10 Mar 2013, Eddie G. O'Connor Jr. wrote:
On 03/10/2013 03:36 PM, Max Pyziur wrote:
Greetings,
[...]
At this point, I think that it's fair to say that F18 has been the most
challenging of all for me since F2: this fedup experience, coupled with
mis-matched release of Postgres
Am 10.03.2013 23:58, schrieb Eddie G. O'Connor Jr.:
> I can only hope that the transitions from F18 to 19to 20etc. are a
> lot less painful than THIS sounds! I had
> the most troubel going from 16 to 17.,.but my move from 17 to 18 wasn't
> anywhere near as problematic as THIS!
the
On 03/10/2013 03:36 PM, Max Pyziur wrote:
Greetings,
Because using an updates-testing version of fedup left my F17->F18
upgrade on a dual-core desktop in a mixed state (lots of F18 rpms
interlaced w/ F17 ones).
For a while the machine would boot in an F17 kernel; while went
through a proce
Greetings,
Because using an updates-testing version of fedup left my F17->F18 upgrade
on a dual-core desktop in a mixed state (lots of F18 rpms interlaced w/
F17 ones).
For a while the machine would boot in an F17 kernel; while went through a
process of 'yum remove'-ing of F18 duplications.
