Status of Fedup'ng F17->F18; when in doubt, yum upgrade ...

[Max Pyziur]

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.

At some point, the kernel went into a panic, and the machine became 
unusable.

Initially, I tried to do a fresh install of F18; but since there are two 
disks on the machine, /dev/sdb mounted on /home, the installer kepting 
hosing when specifying the disk setup.

So, I decided to a fresh 'Minimal Install' of F17, and proceed to F18 from 
there.

First, I tried fedup (the version that is currently available from 
updates, not updates-testing); kernel went into panic mode again.

Re-installed the F17-minimal again, and then did a yum upgrade. Buried in 
the wiki
http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_F...

there is a reference to a fedora-upgrade script packaged as an rpm. It 
pulled everything into F18.

So now with a minimal F18 install, I'm adding packages to bring it back as 
close as possible to its status-quo working state.

Ironically, thanks to Reindl for the link to the Yum Upgrade Wiki page.

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 Postgresql 9.2 and PostGIS 1.5.

Max Pyziur
pyz(a)brama.com

[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. 
Complaining about it here will not get it fixed.

In the future you need to file bugs at https://bugzilla.redhat.com 
against the correct component. This will get the attention of the 
package maintainer. They may not know that PostGIS needs to be updated.

It looks like they do know, though, and an update was queued but it 
failed to pass QA.

https://admin.fedoraproject.org/updates/FEDORA-2013-1551

Feel free to open a bug as no action has been taken in a month.

PostGIS/Postgresql, was Re: Status of Fedup'ng F17->F18; when in doubt, yum upgrade ...

[Reindl Harald]

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 while until F15 both was the case

>  So if not users@... , then where? 
devel@?

PostGIS/Postgresql, was Re: Status of Fedup'ng F17->F18; when in doubt, yum upgrade ...

[Max Pyziur]

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.
>
>  Complaining about it here will not get it fixed. 
I also posted on postgis-users.

>  In the future you need to file bugs at https://bugzilla.redhat.com
> against 
>  the correct component. This will get the attention of the package maintainer. 
>  They may not know that PostGIS needs to be updated. 
>  It looks like they do know, though, and an update was queued but it
> failed to 
>  pass QA. 
They did know; so there's no point in saying that no one knew.

PostGIS has an active user base; they have clearly stated dependencies. 
Releasing F18 with a mismatched release of PostGIS and PostgreSQL should 
not have been done.


>  https://admin.fedoraproject.org/updates/FEDORA-2013-1551
>
>  Feel free to open a bug as no action has been taken in a month. 
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.

That's one of the problems.

The other is diffusion and specialization. What is the correct forum in 
which to raise issues.

Back in usenet days with character-based readers and clear threading, it 
was easy to participate and find discussions relating. These days it is 
more email lists.

So if not users@... , then where?

MP
pyz(a)brama.com

[Reindl Harald]

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.
>  
>  Complaining about it here will not get it fixed.
>  
>  In the future you need to file bugs at https://bugzilla.redhat.com against the correct
> component. This will get the
>  attention of the package maintainer. They may not know that PostGIS needs to be updated
which is a really poor sign

why do people maintain packages they not use at all?
how does anybody imagine such people know what they are doing?

[Max Pyziur]

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 Postgresql 9.2 and PostGIS 1.5.
> >
> >  Max Pyziur
> >  pyz(a)brama.com
> > 
>  I can only hope that the transitions from F18 to 19....to 20....etc. 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! 
As I mentioned previously and to clarify here, this is the third machine 
that I've had to setup/move to F18
  - the first was a fresh install on x64 Dell Latitude D630; since only one 
disk needed to be partitioned (there is a problem if more than one), so 
the install went flawlessly.
  - the second was an i386 Dell Inspiron 600m; fedup worked flawlessly
  - this third one, a home-build dual-core,failed consistently using fedup, 
and failed on a fresh install (the more than one disk issue).

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.

Enough from me on this.

Can you tell me how to gussie-up my Xfce panels; or do I need to learn how 
to use google?

;-)

>  EGO II
>  
MP
pyz(a)brama.com

[Reindl Harald]

Am 10.03.2013 23:58, schrieb Eddie G. O'Connor Jr.:
>  I can only hope that the transitions from F18 to 19....to 20....etc.
> 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 transitions are all painlessif you not install useless
packages and avoid fedup/preupgrde and however the official
upgrade method will be called

yum upgrades are wokring sicne many years, gives you full control
BEFORE reboot in the new system and anyrhing else is bullshit

[EGO-II.1]

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 process of 'yum remove'-ing of F18 duplications.
>
>  At some point, the kernel went into a panic, and the machine became 
>  unusable.
>
>  Initially, I tried to do a fresh install of F18; but since there are 
>  two disks on the machine, /dev/sdb mounted on /home, the installer 
>  kepting hosing when specifying the disk setup.
>
>  So, I decided to a fresh 'Minimal Install' of F17, and proceed to F18 
>  from there.
>
>  First, I tried fedup (the version that is currently available from 
>  updates, not updates-testing); kernel went into panic mode again.
>
>  Re-installed the F17-minimal again, and then did a yum upgrade. Buried 
>  in the wiki
>  http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_F... 
>
>
>  there is a reference to a fedora-upgrade script packaged as an rpm. It 
>  pulled everything into F18.
>
>  So now with a minimal F18 install, I'm adding packages to bring it 
>  back as close as possible to its status-quo working state.
>
>  Ironically, thanks to Reindl for the link to the Yum Upgrade Wiki page.
>
>  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 Postgresql 9.2 and PostGIS 1.5.
>
>  Max Pyziur
>  pyz(a)brama.com
>  
I can only hope that the transitions from F18 to 19....to 20....etc. 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!


EGO II