First impressions of a system update with yum

[Matthias Saou]

Hi,

Here are my very first impressions of a system update from FC6 to F7
using yum. Note that I haven't "insisted" yet, but it's not looking
good.

First thought : Try "yum update" after updating fedora-release (and
fedora-release-notes which it requires).
No go, because some F7 updates are required to fix my system's upgrade
path (in this case it's audacious-plugins which is newer in FC6 and
requires an older version of curl).

Second thought : I'll break down the transaction in smaller bits, which
can only be a good thing. So "yum install kernel yum".
No go, it stops about rpm-libs and rpm-devel still needing the FC6 rpm.
Possibly a multiarch problem since it appears I have i386 rpm-libs and
rpm-devel installed for some reason.

Third thought : Try an even smaller transaction. "yum install kernel"
No go, because it would update the x86_64 ncurses, which then conflicts
with the older i386 ncurses. Possibly the same problem as the previous
transaction.

Current thought : do a "yum remove glibc.i686" to get rid of all 32bit
packages before trying anything else. But this scares me a little,
since last time I did this, many applications stopped working
(segfaults inside gconv libs) until I upgraded all x86_64 glibc
packages. Might work here since the F7 update will do so...

Other current thought : To hell with it, format "/" and reinstall from
DVD...

Last current thought : This used to be much easier. I'm not an
unexperienced user, and it's annoying for me, which is not a good sign.
Oh, and I hate multilib, and most of all that one-arch-only proprietary
flash plugin.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.20-1.2952.fc6
Load : 0.21 0.25 0.42

[Jon Ciesla]

Doing one as we speak on a purely 32-bit system, will post back with results.

>  Hi,
>
>  Here are my very first impressions of a system update from FC6 to F7
>  using yum. Note that I haven't "insisted" yet, but it's not looking
>  good.
>
>  First thought : Try "yum update" after updating fedora-release (and
>  fedora-release-notes which it requires).
>  No go, because some F7 updates are required to fix my system's upgrade
>  path (in this case it's audacious-plugins which is newer in FC6 and
>  requires an older version of curl).
>
>  Second thought : I'll break down the transaction in smaller bits, which
>  can only be a good thing. So "yum install kernel yum".
>  No go, it stops about rpm-libs and rpm-devel still needing the FC6 rpm.
>  Possibly a multiarch problem since it appears I have i386 rpm-libs and
>  rpm-devel installed for some reason.
>
>  Third thought : Try an even smaller transaction. "yum install kernel"
>  No go, because it would update the x86_64 ncurses, which then conflicts
>  with the older i386 ncurses. Possibly the same problem as the previous
>  transaction.
>
>  Current thought : do a "yum remove glibc.i686" to get rid of all 32bit
>  packages before trying anything else. But this scares me a little,
>  since last time I did this, many applications stopped working
>  (segfaults inside gconv libs) until I upgraded all x86_64 glibc
>  packages. Might work here since the F7 update will do so...
>
>  Other current thought : To hell with it, format "/" and reinstall from
>  DVD...
>
>  Last current thought : This used to be much easier. I'm not an
>  unexperienced user, and it's annoying for me, which is not a good sign.
>  Oh, and I hate multilib, and most of all that one-arch-only proprietary
>  flash plugin.
>
>  Matthias
>
>  --
>  Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
>  Fedora release 7 (Moonshine) - Linux kernel 2.6.20-1.2952.fc6
>  Load : 0.21 0.25 0.42
>
>  --
>  fedora-devel-list mailing list
>  fedora-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-devel-list
>  

-- 
novus ordo absurdum

[Matthias Saou]

Jon Ciesla wrote :

>  Doing one as we speak on a purely 32-bit system, will post back with
> results. 
I'm pretty sure it'll be soooooo much smoother.

Right now, I just got :

Transaction Check Error:
  file /etc/esd.conf from install of esound-libs-0.2.38-1.fc7 conflicts
with file from package esound-0.2.36-3
  file /usr/share/man/man1/esd.1.gz from install of esound-0.2.38-1.fc7
conflicts with file from package esound-0.2.36-3

After trying a single big fat "yum update" again. Seems more like a
multilib issue (*sigh*) than a broken upgrade path.

I'll start by removing as many 32bit packages as I can...

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.20-1.2952.fc6
Load : 0.22 0.51 0.48

[Jesse Keating]

On Thursday 31 May 2007 13:41:23 Matthias Saou wrote:
>  I'm pretty sure it'll be soooooo much smoother.
>
>  Right now, I just got :
>
>  Transaction Check Error:
>    file /etc/esd.conf from install of esound-libs-0.2.38-1.fc7 conflicts
>  with file from package esound-0.2.36-3
>    file /usr/share/man/man1/esd.1.gz from install of esound-0.2.38-1.fc7
>  conflicts with file from package esound-0.2.36-3
>
>  After trying a single big fat "yum update" again. Seems more like a
>  multilib issue (*sigh*) than a broken upgrade path.
>
>  I'll start by removing as many 32bit packages as I can... 
yeah, esound grew an esound-libs in F7, esound-libs is multilib now, esound is 
not.  You'll have to fiddle with that one by hand.  Anaconda deals with it 
forcefully as well.

-- 
Jesse Keating
Release Engineer: Fedora

[Matthias Saou]

Jesse Keating wrote :

>  On Thursday 31 May 2007 13:41:23 Matthias Saou wrote:
>  > I'm pretty sure it'll be soooooo much smoother.
>  >
>  > Right now, I just got :
>  >
>  > Transaction Check Error:
>  >   file /etc/esd.conf from install of esound-libs-0.2.38-1.fc7 conflicts
>  > with file from package esound-0.2.36-3
>  >   file /usr/share/man/man1/esd.1.gz from install of esound-0.2.38-1.fc7
>  > conflicts with file from package esound-0.2.36-3
>  >
>  > After trying a single big fat "yum update" again. Seems more like a
>  > multilib issue (*sigh*) than a broken upgrade path.
>  >
>  > I'll start by removing as many 32bit packages as I can...
>  
>  yeah, esound grew an esound-libs in F7, esound-libs is multilib now, esound is 
>  not.  You'll have to fiddle with that one by hand.  Anaconda deals with it 
>  forcefully as well. 
Oh well. This worked :

rpm -e --nodeps esound.i386

But it's not something I like to do... and I'll have to check after the
update if any i386 esound packages are still missing. But hey, it's
running :-)

Install     97 Package(s)         
Update    1030 Package(s)         
Remove       2 Package(s)

Off for the evening now. I'll have a (nice? bad?) surprise when I get
back to the office tomorrow morning ;-)

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.20-1.2952.fc6
Load : 1.35 1.58 0.98

[Jesse Keating]

On Thursday 31 May 2007 14:12:27 Matthias Saou wrote:
>  Oh well. This worked :
>
>  rpm -e --nodeps esound.i386
>
>  But it's not something I like to do... and I'll have to check after the
>  update if any i386 esound packages are still missing. But hey, it's
>  running :-)
>
>  Install     97 Package(s)        
>  Update    1030 Package(s)        
>  Remove       2 Package(s)
>
>  Off for the evening now. I'll have a (nice? bad?) surprise when I get
>  back to the office tomorrow morning ;-) 
You may run into it as well for hal -> hal-libs.

-- 
Jesse Keating
Release Engineer: Fedora

[Gerry Reno]

Are you doing a 'yum upgrade' or 'yum update'?  I think the first 
obsoletes the current packages.

Jon Ciesla wrote:
>  Doing one as we speak on a purely 32-bit system, will post back with
> results

[Jesse Keating]

On Thursday 31 May 2007 13:45:24 Gerry Reno wrote:
>  Are you doing a 'yum upgrade' or 'yum update'?  I
> think the first
>  obsoletes the current packages. 
Both do the same now.

-- 
Jesse Keating
Release Engineer: Fedora

[Jon Ciesla]

Not according to 'man yum' on the patched FC6 system I just looked it up
on.  I'll look again after update/grade. :)

>  On Thursday 31 May 2007 13:45:24 Gerry Reno wrote:
> > Are you doing a 'yum upgrade' or 'yum update'?  I think the first
> > obsoletes the current packages.
>
>  Both do the same now.
>
>  --
>  Jesse Keating
>  Release Engineer: Fedora
>  --
>  fedora-devel-list mailing list
>  fedora-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-devel-list 

-- 
novus ordo absurdum

[Jon Ciesla]

rpm -Uvh fedora-release* (for fedora-release and -notes)
yum update

Should have done yum upgrade, but yum update has worked for me in the
past.  I may try yum upgrade on the next machine.

>  Are you doing a 'yum upgrade' or 'yum update'?  I
> think the first
>  obsoletes the current packages.
>
>  Jon Ciesla wrote:
> > Doing one as we speak on a purely 32-bit system, will post back with
> > results
>  

-- 
novus ordo absurdum

[Schlaegel]

On 5/31/07, Matthias Saou
<thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
wrote:
>  Other current thought : To hell with it, format "/" and
> reinstall from
>  DVD... 
This is my normal course of action. I don't want to deal with the
leftover packages and the missing new packages. I just let Anaconda do
its job.

I have two partitions for root, the current release, and the new or
old release. That way my old root with a working system is available
if some hardware seems to not work.

Also, I don't bother with a DVD or CD, I just use the grub hack.

-Schlaegel

[Matthias Saou]

Schlaegel wrote :

>  On 5/31/07, Matthias Saou
>  <thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
>  wrote:
>  > Other current thought : To hell with it, format "/" and reinstall from
>  > DVD...
>  
>  This is my normal course of action. I don't want to deal with the
>  leftover packages and the missing new packages. I just let Anaconda do
>  its job. 
This is quite easily dealt with :

Running "package-cleanup --orphans" (from yum-utils) will list you all
the packages currently installed which aren't listed in any configured
repository.

Then "yum groupinstall Base" will show/install the base packages which
you don't have installed, usually because they were added in the last
Fedora release.

Of course, this doesn't remove unused stuff, nor does it deal so
gracefully with configuration changes or even low-level install
changes, for instance if anaconda now chooses different defaults for
LVM layouts, sizes or even ext3 formatting options.

Right now I've gotten back to the office, where my workstation freshly
updated to F7 was waiting at the (new!) gdm login screen.

FWIW, here are the annoyances I've seen so far :
- My gnome-panel didn't start
- I was seeing many denies regarding /dev/nvidia* accesses (yeah..)
-> I disabled selinux and rebooted :-(
- My desktop came up with metacity, I had to manually switch back to
Beryl (probably because of the previous errors)
- My GNOME menu icon is gone. Even if I add a new main GNOME menu to my
panel, it doesn't have any icon. The name probably changed and I'll
need to get a newer theme. *sigh*
- All my fonts look different, in firefox as well as claws-mail...

Note that many of my "annoyances" aren't related to packages
themselves, more to the fact that I kept my /home intact. As always,
there is clearly room for upgrade improvements, but as always... it's
not that easy to get right in all possible scenarios.

Oh, the "yum update" finished OK on my x86_64 after the esound hack,
and on my i386 laptop (Dell X1) it went absolutely fine. I just need to
get S3 working again, as I wanted to start fresh and removed all the
kernel boot options I had in case they weren't useful anymore...

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.21-1.3194.fc7
Load : 0.08 0.54 0.54

[Richard Hughes]

On Fri, 2007-06-01 at 10:52 +0200, Matthias Saou wrote:
>  I just need to get S3 working again, as I wanted to start fresh and
>  removed all the kernel boot options I had in case they weren't useful
>  anymore... 
If you are talking about s3 (suspend), see
http://people.freedesktop.org/~hughsient/quirk/

Richard.

[Matthias Saou]

Richard Hughes wrote :

>  On Fri, 2007-06-01 at 10:52 +0200, Matthias Saou wrote:
>  > I just need to get S3 working again, as I wanted to start fresh and
>  > removed all the kernel boot options I had in case they weren't useful
>  > anymore...
>  
>  If you are talking about s3 (suspend), see
>  http://people.freedesktop.org/~hughsient/quirk/ 
That page was incredibly helpful. I actually understood what all those
different "quirks" did! :-)

For my Dell "Latitude X1", which is not yet in the F7 HAL files, I had
to enable the --quirk-vbe-post quirk, as otherwise the screen never
turned on.

With FC6 I was using the i810 Xorg driver, with 855resolution to be
able to get the native 1280x768 resolution, I had to hack my way
through the ACPI scripts to get S3 working (tg3 was causing trouble at
some point), and the LCD backlight never turned on properly on resume,
I had to always press Fn+Up to increase the brightness for it to light
up completely again.

With F7, I switched to the "intel" modesetting driver (also removed
855resolution), added the "power_management.quirk.vbe_post" key to true
in a string="Latitude X1" section of the Dell HAL file, and it all just
works now! Awesome! :-)

I had a last question, though : The Dell models seem to be identified
with system.hardware.product contains="Foo". This seems like a pretty
bad idea, since it would be contains="X1" in this case, and will/would
match a future Dell "Latitude X10" laptop... It would seem wiser to use
string="Latitude X1", even though it would be partly redundant with the
earlier prefix="Latitude". Or maybe there is a suffix="Bar"?

Matthias

PS: Congratulations on your diploma, Richard ;-)

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.21-1.3194.fc7
Load : 0.50 0.32 0.29

[Richard Hughes]

On Tue, 2007-06-05 at 10:25 +0200, Matthias Saou wrote:
>  Richard Hughes wrote :
>  
>  > On Fri, 2007-06-01 at 10:52 +0200, Matthias Saou wrote:
>  > > I just need to get S3 working again, as I wanted to start fresh and
>  > > removed all the kernel boot options I had in case they weren't useful
>  > > anymore...
>  > 
>  > If you are talking about s3 (suspend), see
>  > http://people.freedesktop.org/~hughsient/quirk/
>  
>  That page was incredibly helpful. I actually understood what all those
>  different "quirks" did! :-) 
Good :-)

I'll continue to add content as required. Soon multimedia keyboard will
be quirks in hal-info and the same site will be used to make keyboards
just work in the future.

>  For my Dell "Latitude X1", which is not yet in the F7 HAL
> files, I had
>  to enable the --quirk-vbe-post quirk, as otherwise the screen never
>  turned on. 
Cool.

>  With F7, I switched to the "intel" modesetting driver (also
> removed
>  855resolution), added the "power_management.quirk.vbe_post" key to true
>  in a string="Latitude X1" section of the Dell HAL file, and it all just
>  works now! Awesome! :-) 
Cool.

>  I had a last question, though : The Dell models seem to be
> identified
>  with system.hardware.product contains="Foo". This seems like a pretty
>  bad idea, since it would be contains="X1" in this case, and will/would
>  match a future Dell "Latitude X10" laptop... It would seem wiser to use
>  string="Latitude X1", even though it would be partly redundant with the
>  earlier prefix="Latitude". Or maybe there is a suffix="Bar"? 
There is such a thing:

<!ELEMENT match (match|merge|prepend|append|addset|remove|spawn)*
>  
<!ATTLIST match 
    key              CDATA #REQUIRED
    string           CDATA #IMPLIED
    int              CDATA #IMPLIED
    bool             (false|true) #IMPLIED
    exists           (false|true) #IMPLIED
    empty            (false|true) #IMPLIED
    is_ascii         (false|true) #IMPLIED
    is_absolute_path (false|true) #IMPLIED
    contains         CDATA #IMPLIED
    contains_ncase   CDATA #IMPLIED
    contains_not     CDATA #IMPLIED
    prefix           CDATA #IMPLIED
    prefix_ncase     CDATA #IMPLIED
    suffix           CDATA #IMPLIED
    suffix_ncase     CDATA #IMPLIED
    compare_lt       CDATA #IMPLIED
    compare_le       CDATA #IMPLIED
    compare_gt       CDATA #IMPLIED
    compare_ge       CDATA #IMPLIED
    compare_ne       CDATA #IMPLIED
    sibling_contains CDATA #IMPLIED
>  
You can either use suffix or just use string for the whole text.

I would be very appreciative if you could generate a patch and sent it
to the mailing list. I'm glad things are now working.

Richard.

[Jon Ciesla]

I've now completed 2 yum upgrades of x86 32-bit only systems, with no
gotchas.

This can't be right. . .;)

>  On Tue, 2007-06-05 at 10:25 +0200, Matthias Saou wrote:
> > Richard Hughes wrote :
> >
> > > On Fri, 2007-06-01 at 10:52 +0200, Matthias Saou wrote:
> > > > I just need to get S3 working again, as I wanted to start fresh and
> > > > removed all the kernel boot options I had in case they weren't
> > useful
> > > > anymore...
> > >
> > > If you are talking about s3 (suspend), see
> > > http://people.freedesktop.org/~hughsient/quirk/
> >
> > That page was incredibly helpful. I actually understood what all those
> > different "quirks" did! :-)
>
>  Good :-)
>
>  I'll continue to add content as required. Soon multimedia keyboard will
>  be quirks in hal-info and the same site will be used to make keyboards
>  just work in the future.
>
> > For my Dell "Latitude X1", which is not yet in the F7 HAL files, I had
> > to enable the --quirk-vbe-post quirk, as otherwise the screen never
> > turned on.
>
>  Cool.
>
> > With F7, I switched to the "intel" modesetting driver (also removed
> > 855resolution), added the "power_management.quirk.vbe_post" key to true
> > in a string="Latitude X1" section of the Dell HAL file, and it all just
> > works now! Awesome! :-)
>
>  Cool.
>
> > I had a last question, though : The Dell models seem to be identified
> > with system.hardware.product contains="Foo". This seems like a pretty
> > bad idea, since it would be contains="X1" in this case, and will/would
> > match a future Dell "Latitude X10" laptop... It would seem wiser to use
> > string="Latitude X1", even though it would be partly redundant with the
> > earlier prefix="Latitude". Or maybe there is a suffix="Bar"?
>
>  There is such a thing:
>
>  <!ELEMENT match (match|merge|prepend|append|addset|remove|spawn)* >
>  <!ATTLIST match
>      key              CDATA #REQUIRED
>      string           CDATA #IMPLIED
>      int              CDATA #IMPLIED
>      bool             (false|true) #IMPLIED
>      exists           (false|true) #IMPLIED
>      empty            (false|true) #IMPLIED
>      is_ascii         (false|true) #IMPLIED
>      is_absolute_path (false|true) #IMPLIED
>      contains         CDATA #IMPLIED
>      contains_ncase   CDATA #IMPLIED
>      contains_not     CDATA #IMPLIED
>      prefix           CDATA #IMPLIED
>      prefix_ncase     CDATA #IMPLIED
>      suffix           CDATA #IMPLIED
>      suffix_ncase     CDATA #IMPLIED
>      compare_lt       CDATA #IMPLIED
>      compare_le       CDATA #IMPLIED
>      compare_gt       CDATA #IMPLIED
>      compare_ge       CDATA #IMPLIED
>      compare_ne       CDATA #IMPLIED
>      sibling_contains CDATA #IMPLIED
> >
>
>  You can either use suffix or just use string for the whole text.
>
>  I would be very appreciative if you could generate a patch and sent it
>  to the mailing list. I'm glad things are now working.
>
>  Richard.
>
>
>  --
>  fedora-devel-list mailing list
>  fedora-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-devel-list
>  

-- 
novus ordo absurdum

Missing pkgs in F7!?

[Oliver Falk]

- snort is missing in f7, but avail in -devel and fc6
- openldap-servers missing in f7, but avail in -devel and fc6
- bind-sdb missing in f7, but avail in -devel and fc6
- net-snmp-utils missing in f7, but avail in -devel and fc6
- stonith and heartbeat missing in f7, but avail in -devel and fc6

That's all I stumbled across at the moment...

Maybe it's a fault on my side (corrupt ISOs? I don't think so sha1sum-ed
it). I also checked download.fedora.redhat.com and didn't find the pkgs.

-of

Missing pkgs in F7!?

[Oliver Falk]

On 06/01/2007 11:33 AM, Oliver Falk wrote:
>  - snort is missing in f7, but avail in -devel and fc6
>  - openldap-servers missing in f7, but avail in -devel and fc6
>  - bind-sdb missing in f7, but avail in -devel and fc6
>  - net-snmp-utils missing in f7, but avail in -devel and fc6
>  - stonith and heartbeat missing in f7, but avail in -devel and fc6
>  
>  That's all I stumbled across at the moment...
>  
>  Maybe it's a fault on my side (corrupt ISOs? I don't think so sha1sum-ed
>  it). I also checked download.fedora.redhat.com and didn't find the pkgs. 
kk. it was clarified in irc. those pkgs are not on the distribution dvd,
they can be found in the 'Everything' 'tree'...

-of

Missing pkgs in F7!?

[Thorsten Leemhuis]

On 01.06.2007 11:33, Oliver Falk wrote:
>  - snort is missing in f7, but avail in -devel and fc6
>  - openldap-servers missing in f7, but avail in -devel and fc6
>  - bind-sdb missing in f7, but avail in -devel and fc6
>  - net-snmp-utils missing in f7, but avail in -devel and fc6
>  - stonith and heartbeat missing in f7, but avail in -devel and fc6
>  
>  That's all I stumbled across at the moment...
>  
>  Maybe it's a fault on my side (corrupt ISOs? I don't think so sha1sum-ed
>  it). I also checked download.fedora.redhat.com and didn't find the pkgs. 
Did you look in releases/7/Everything/${arch}/os/Fedora/ ? See for example:

http://ftp-stud.fht-esslingen.de/pub/Mirrors/fedora.redhat.com/linux/rele...
http://ftp-stud.fht-esslingen.de/pub/Mirrors/fedora.redhat.com/linux/rele...

(that's a German mirror, but should be there on
download.fedoraproject.org as well)

CU
thl

[Jon Ciesla]

My first 32-bit x86 yum upgrade is finished, with no major complications. 
So far.  I'll let you know. . .

>  On 5/31/07, Matthias Saou
>  <thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
>  wrote:
> > Other current thought : To hell with it, format "/" and reinstall from
> > DVD...
>
>  This is my normal course of action. I don't want to deal with the
>  leftover packages and the missing new packages. I just let Anaconda do
>  its job.
>
>  I have two partitions for root, the current release, and the new or
>  old release. That way my old root with a working system is available
>  if some hardware seems to not work.
>
>  Also, I don't bother with a DVD or CD, I just use the grub hack.
>
>  -Schlaegel
>
>  --
>  fedora-devel-list mailing list
>  fedora-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-devel-list
>  

-- 
novus ordo absurdum

[Benjamin Lewis]

Same here, no problems - this is the first time its worked for me too!

Jon Ciesla wrote:
>  My first 32-bit x86 yum upgrade is finished, with no major
> complications. 
>  So far.  I'll let you know. . .
>
>    
> > On 5/31/07, Matthias Saou
> > <thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
> > wrote:
> >     
> >> Other current thought : To hell with it, format "/" and reinstall from
> >> DVD...
> >>       
> > This is my normal course of action. I don't want to deal with the
> > leftover packages and the missing new packages. I just let Anaconda do
> > its job.
> >
> > I have two partitions for root, the current release, and the new or
> > old release. That way my old root with a working system is available
> > if some hardware seems to not work.
> >
> > Also, I don't bother with a DVD or CD, I just use the grub hack.
> >
> > -Schlaegel
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
> >     
>
>
>     
-- 

Benjamin Lewis
Fedora Ambassador
ben.lewis(a)benl.co.uk

-----------------------------------------------------------------------
http://benl.co.uk./                                 PGP Key: 0x647E480C

"In cases of major discrepancy, it is always reality that got it wrong"
                                                        -- RFC 1118

[Jon Ciesla]

Actually, I've done this several times, I have a server that began life as
FC3, and another as RH8.  I've been yum upgrading since FC3, and this was
just my first for F7.  I several more to do yet. :)

>  Same here, no problems - this is the first time its worked for me
> too!
>
>  Jon Ciesla wrote:
> > My first 32-bit x86 yum upgrade is finished, with no major
> > complications.
> > So far.  I'll let you know. . .
> >
> >
> >> On 5/31/07, Matthias Saou
> >> <thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
> >> wrote:
> >>
> >>> Other current thought : To hell with it, format "/" and reinstall
> from
> >>> DVD...
> >>>
> >> This is my normal course of action. I don't want to deal with the
> >> leftover packages and the missing new packages. I just let Anaconda do
> >> its job.
> >>
> >> I have two partitions for root, the current release, and the new or
> >> old release. That way my old root with a working system is available
> >> if some hardware seems to not work.
> >>
> >> Also, I don't bother with a DVD or CD, I just use the grub hack.
> >>
> >> -Schlaegel
> >>
> >> --
> >> fedora-devel-list mailing list
> >> fedora-devel-list(a)redhat.com
> >> https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >>
> >>
> >
> >
> >
>
>  --
>
>  Benjamin Lewis
>  Fedora Ambassador
>  ben.lewis(a)benl.co.uk
>
>  -----------------------------------------------------------------------
>  http://benl.co.uk./                                 PGP Key: 0x647E480C
>
>  "In cases of major discrepancy, it is always reality that got it wrong"
>                                                          -- RFC 1118
>
>  

-- 
novus ordo absurdum

[Benjamin Lewis]

Yeah, its just it usually explodes when I do it, so I'm happy - now to
sort out my laptop...

Jon Ciesla wrote:
>  Actually, I've done this several times, I have a server that
> began life as
>  FC3, and another as RH8.  I've been yum upgrading since FC3, and this was
>  just my first for F7.  I several more to do yet. :)
>
>    
> > Same here, no problems - this is the first time its worked for me too!
> >
> > Jon Ciesla wrote:
> >     
> >> My first 32-bit x86 yum upgrade is finished, with no major
> >> complications.
> >> So far.  I'll let you know. . .
> >>
> >>
> >>       
> >>> On 5/31/07, Matthias Saou
> >>> <thias(a)spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net&gt;
> >>> wrote:
> >>>
> >>>         
> >>>> Other current thought : To hell with it, format "/" and
> reinstall from
> >>>> DVD...
> >>>>
> >>>>           
> >>> This is my normal course of action. I don't want to deal with the
> >>> leftover packages and the missing new packages. I just let Anaconda do
> >>> its job.
> >>>
> >>> I have two partitions for root, the current release, and the new or
> >>> old release. That way my old root with a working system is available
> >>> if some hardware seems to not work.
> >>>
> >>> Also, I don't bother with a DVD or CD, I just use the grub hack.
> >>>
> >>> -Schlaegel
> >>>
> >>> --
> >>> fedora-devel-list mailing list
> >>> fedora-devel-list(a)redhat.com
> >>> https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >>>
> >>>
> >>>         
> >>
> >>       
> > --
> >
> > Benjamin Lewis
> > Fedora Ambassador
> > ben.lewis(a)benl.co.uk
> >
> > -----------------------------------------------------------------------
> > http://benl.co.uk./                                 PGP Key: 0x647E480C
> >
> > "In cases of major discrepancy, it is always reality that got it wrong"
> >                                                         -- RFC 1118
> >
> >
> >     
>
>
>     
-- 

Benjamin Lewis
Fedora Ambassador
ben.lewis(a)benl.co.uk

-----------------------------------------------------------------------
http://benl.co.uk./                                 PGP Key: 0x647E480C

"In cases of major discrepancy, it is always reality that got it wrong"
                                                        -- RFC 1118

[Gerry Reno]

I successfully upgraded from FC5 to FC6 by having only packages 
installed using yum.  Before that I always has a lot of tarball installs 
on the system and then upgrading to a new release was just a disaster 
every time I had tried it.  Of course the upgrade to FC6 wasn't without 
problems, like i586 kernel, and the upgrade breaking in the middle and 
leaving a huge number of duplicate packages installed.  So there was a 
lot of cleanup to do.  But I'm really encouraged to hear that it looks 
like a FC6 - FC7 upgrade is going good without major problems (at least 
on 32-bit).  :-)


Benjamin Lewis wrote:
>  Yeah, its just it usually explodes when I do it, so I'm happy -
> now to
>  sort out my laptop...
>
>  Jon Ciesla wrote:
>    
> > Actually, I've done this several times, I have a server that began life as
> > FC3, and another as RH8.  I've been yum upgrading since FC3, and this was
> > just my first for F7.  I several more to do yet. :)
> >
> >   
> >     
> >> Same here, no problems - this is the first time its worked for me too!
> >>
> >> Jon Ciesla wrote:
> >>     
> >>       
> >>> My first 32-bit x86 yum upgrade is finished, with no major
> >>> complications.
> >>> So far.  I'll let you know. . .
> >>>
> >>>
> >>>       
> >>>