Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2011-06-05 at 17:31 -0400, Michael H. Warfield wrote: 
> On Sat, 2011-06-04 at 12:33 +0100, Timothy Murphy wrote: 
> > Michael H. Warfield wrote:
> > 
> > > Classically, for those servers (some of which originally started out on
> > > FC1) have been upgraded using the yum upgrade method.
> > 
> > As a matter of interest, what exactly is _the_ yum upgrade method?
> > I've seen the term used by several people,
> > but as far as I can see they refer to different methods.
> 
> > And don't all upgrade methods use yum in some way?
> 
> http://fedoraproject.org/wiki/YumUpgradeFaq
> 
> This is a pure yum upgrade from F{x} to F{x+1} (some people have
> reported success with x+2 but I would personally avoid that like the
> plague) on a live running system without taking it down for the upgrade
> process..
> 
> So (in very shortened abbreviated summary form), to upgrade from F14 to
> F15 you run...

> yum update
> yum clean all
> rpm --import https://fedoraproject.org/static/069C8460.txt
> yum --releasever=15 --disableplugin=presto distro-sync

Ok...  My apologies.  That really wasn't playing fair and very bad of me
over simplifying things a bit too much.  That summarizes the process
described on the FAQ page (which I strong, STRONGLY recommend reading)
but there's gotcha's in there.

First off, I should mention, this is the newer process.  The
"--releasever" option and the "distro-sync" command are relatively new
additions to yum.  You use to have to manually download the release rpm,
the release-notes rpm, and the GPG key and install them using rpm then
run a "yum update" or "yum upgrade" (which are actually identical
functions - they don't do anything different now, if they ever did
anything different every in the past).

You will often run into dependency failures and it may recommend using
"--skip-broken" or something like that.  I've had terrible luck with
that where yum would enter in to infinite dependency resolution loops!

The procedure I use is to start off with this command:

rpm -qa --qf '%{NAME}\n' | sort -u > rpm.list

Then do the steps above.  If things slam into a dependency error, run
"yum erase" to remove the trouble makers, provided it doesn't try to
remove your entire system (saw that once around F11, iirc, that was fun
to work around).  Once the above workflow runs to completion with no
dependency problems, then you run this:

yum install `cat rpm.list`

You'll get a lot of bitch about packages already installed but anything
missing will get installed or you will get an error.  Currently, it
looks like avidmux from rpmfusion isn't reinstalling for me.  Oh well.
It eventually will.

So this isn't necessarily a "fire and forget process" and it use to be
worse.  But...  Then again...  Neither is preupgrade.

> (After a half an hour or so you'll probably complete this and reboot)
> 
> yum groupupdate Base
> 
> Now, I'm not quite sure exactly why that FAQ page recommends running
> "yum update yum" since the first "yum update" should take care of that.
> I have not been doing that step and it's never burned me (in fact, when
> I have done that step, it's done nothing).
> 
> You should also read the caveats in that FAQ about cleaning up config
> files and looking for any strange .rpmsave or .rpmorg types of things.
> I think, in the past, squid was notorious for changing configuration
> file formats and you have to port.
> 
> Also if you use Postgres, PAY CAREFUL ATTENTION TO DUMPING THE DATABASE
> TO AN SQL DUMP FILE FIRST!  That is not mentioned on that page but
> almost every Fedora click has taken Postgres through and upgrade click
> which can not automagically migrate the databases.  I don't think
> preupgrade or disk upgrades to any better here so it's not the fault of
> yum upgrade.
> 
> Mike
> 
> > -- 
> > Timothy Murphy  
> > e-mail: gayleard /at/ eircom.net
> > tel: +353-86-2336090, +353-1-2842366
> > s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
> > 
> > -- 
> > users mailing list
> > users@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > 
> 

-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  mhw@xxxxxxxxxxxx
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux