Yum Upgrade Faq

[seth vidal]

I've added a wiki page here:
http://fedoraproject.org/wiki/YumUpgradeFaq

It's about upgrading from release to release via yum. If you find any
other odd gotchas - add them there.

-sv

[David Hollis]

On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  I've added a wiki page here:
>  http://fedoraproject.org/wiki/YumUpgradeFaq
>  
>  It's about upgrading from release to release via yum. If you find any
>  other odd gotchas - add them there.
>  
>  -sv 

I'm finding that even trying to upgrade yum i have problems with
openoffice due to the package name changes.  I have:

libdb_cxx-4.2.so needed by openoffice.org-libs
libedataserver.so.3 needed by openoffice.org
libebook.so.8 needed by openoffice.org

Looks like I'll need to manually install openoffice.org-core to take
care of those

-- 
David Hollis <dhollis(a)davehollis.com&gt;

[Emily Brantley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Hollis wrote:
>  On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  
> >I've added a wiki page here:
> >http://fedoraproject.org/wiki/YumUpgradeFaq
> >
> >It's about upgrading from release to release via yum. If you find any
> >other odd gotchas - add them there.
> >
> >-sv
>  
>  
>  
>  I'm finding that even trying to upgrade yum i have problems with
>  openoffice due to the package name changes.  I have:
>  
>  libdb_cxx-4.2.so needed by openoffice.org-libs
>  libedataserver.so.3 needed by openoffice.org
>  libebook.so.8 needed by openoffice.org
>  
>  Looks like I'll need to manually install openoffice.org-core to take
>  care of those 
maybe you should note that on the FAQ wiki so that others can benefit
from knowing about it.

Em
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFCrw8Sl/fI0i0h13cRAkmbAJ9ScvNLBu/ilOAzZ3BxlcwZvW4qpwCcCWLR
> AEb5Td2e/cVw+lkKpjZ1/kc=
> =0hTt
> -----END PGP SIGNATURE-----

[seth vidal]

On Tue, 2005-06-14 at 13:00 -0400, David Hollis wrote:
>  On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  > I've added a wiki page here:
>  > http://fedoraproject.org/wiki/YumUpgradeFaq
>  > 
>  > It's about upgrading from release to release via yum. If you find any
>  > other odd gotchas - add them there.
>  > 
>  > -sv
>  
>  
>  I'm finding that even trying to upgrade yum i have problems with
>  openoffice due to the package name changes.  I have:
>  
>  libdb_cxx-4.2.so needed by openoffice.org-libs
>  libedataserver.so.3 needed by openoffice.org
>  libebook.so.8 needed by openoffice.org
>  
>  Looks like I'll need to manually install openoffice.org-core to take
>  care of those 
what're you upgrading FROM? Fc3?

-sv

[David Hollis]

On Tue, 2005-06-14 at 13:11 -0400, seth vidal wrote:
>  On Tue, 2005-06-14 at 13:00 -0400, David Hollis wrote:
>  > On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  > > I've added a wiki page here:
>  > > http://fedoraproject.org/wiki/YumUpgradeFaq
>  > > 
>  > > It's about upgrading from release to release via yum. If you find any
>  > > other odd gotchas - add them there.
>  > > 
>  > > -sv
>  > 
>  > 
>  > I'm finding that even trying to upgrade yum i have problems with
>  > openoffice due to the package name changes.  I have:
>  > 
>  > libdb_cxx-4.2.so needed by openoffice.org-libs
>  > libedataserver.so.3 needed by openoffice.org
>  > libebook.so.8 needed by openoffice.org
>  > 
>  > Looks like I'll need to manually install openoffice.org-core to take
>  > care of those
>  
>  what're you upgrading FROM? Fc3? 
Yep, FC3.

-- 
David Hollis <dhollis(a)davehollis.com&gt;

[seth vidal]

>  > 
>  > what're you upgrading FROM? Fc3?
>  
>  Yep, FC3.
>   
what ver of yum were you using to do the upgrade?

-sv

[David Hollis]

On Tue, 2005-06-14 at 16:03 -0400, seth vidal wrote:
>  > > 
>  > > what're you upgrading FROM? Fc3?
>  > 
>  > Yep, FC3.
>  > 
>  
>  what ver of yum were you using to do the upgrade?
>  
>  -sv
>  
>   
yum-2.2.0-0.fc3  is what I was starting with.  After pulling down the
new fedora-release and installing it, I tried to yum -y update yum.  It
wanted to pull in a large amount of stuff which led to the openoffice
problem.

-- 
David Hollis <dhollis(a)davehollis.com&gt;

[David Cary Hart]

On Tue, 2005-06-14 at 21:04 -0400, David Hollis wrote:
>  > 
>  
>  yum-2.2.0-0.fc3  is what I was starting with.  After pulling down the
>  new fedora-release and installing it, I tried to yum -y update yum.  It
>  wanted to pull in a large amount of stuff which led to the openoffice
>  problem.
>   
Is there a listing somewhere of known issues. FC4 breaks yumex which is
no big deal. Moreover, I was unable to install madwifi on my laptop. On
the other hand, I'm concerned about things like leafnode. I'm testing
rbldnsd on a workstation and it seems to be fine.

I'm thinking that I should wait a few weeks before updating the primary
server.
-- 
      * Eliminate Spam:         http://www.TQMcube.com/spam_trap.htm
      * RBLDNSD HowTo:          http://www.TQMcube.com/rbldnsd.htm
      * Multi-RBL Check:        http://www.TQMcube.com/rblcheck.htm

[Matthew Miller]

On Tue, Jun 14, 2005 at 10:07:28PM -0400, David Cary Hart wrote:
>  Is there a listing somewhere of known issues. FC4 breaks yumex which
> is
>  no big deal. Moreover, I was unable to install madwifi on my laptop. On 

For yumex: have you tried this:
<http://linux.rasmil.dk/cms/modules/news/article.php?storyid=8>


-- 
Matthew Miller           mattdm(a)mattdm.org        <http://www.mattdm.org/>
Boston University Linux      ------>                <http://linux.bu.edu/>
Current office temperature: 81 degrees Fahrenheit.

[seth vidal]

>  yum-2.2.0-0.fc3  is what I was starting with.  After pulling down
> the
>  new fedora-release and installing it, I tried to yum -y update yum.  It
>  wanted to pull in a large amount of stuff which led to the openoffice
>  problem. 
okay - just run:
yum upgrade

and see what it does.

-sv

[Dimi Paun]

On Wed, 2005-06-15 at 03:07 -0400, seth vidal wrote:
>  okay - just run:
>  yum upgrade
>  
>  and see what it does. 
I'm having a bit of a problem too:

[root@dimi ~]# rpm -e kernel-utils
--> Processing Dependency: kernel-utils for package: kernel-smp
--> Processing Dependency: kernel-utils for package: kernel
--> Processing Dependency: kernel-utils for package: kernel
--> Finished Dependency Resolution
Error: Missing Dependency: kernel-utils is needed by package kernel
Error: Missing Dependency: kernel-utils is needed by package kernel-smp

Here are the details:

[root@dimi ~]# rpm -q kernel-utils
kernel-utils-2.4-13.1.49_FC3
[root@dimi ~]# rpm -e kernel-utils-2.4-13.1.49_FC3
error: Failed dependencies:
   kernel-utils is needed by (installed) lm_sensors-2.8.7-2.i386
   kernel-utils is needed by (installed) kernel-2.6.11-1.14_FC3.i686
   kernel-utils is needed by (installed) kernel-smp-2.6.11-1.27_FC3.i686
   kernel-utils is needed by (installed) kernel-2.6.11-1.27_FC3.i686

Why is kernel-2.6.11 dependent on kernel-utils-2.4.13 I don't know...

-- 
Dimi Paun <dimi(a)lattica.com&gt;
Lattica, Inc.

[Rahul Sundaram]

Dimi Paun wrote:

> On Wed, 2005-06-15 at 03:07 -0400, seth vidal wrote:
>   
>
> >okay - just run:
> >yum upgrade
> >
> >and see what it does.
> >    
> >
>
> I'm having a bit of a problem too:
>
> [root@dimi ~]# rpm -e kernel-utils
> --> Processing Dependency: kernel-utils for package: kernel-smp
> --> Processing Dependency: kernel-utils for package: kernel
> --> Processing Dependency: kernel-utils for package: kernel
> --> Finished Dependency Resolution
> Error: Missing Dependency: kernel-utils is needed by package kernel
> Error: Missing Dependency: kernel-utils is needed by package kernel-smp
>
> Here are the details:
>
> [root@dimi ~]# rpm -q kernel-utils
> kernel-utils-2.4-13.1.49_FC3
> [root@dimi ~]# rpm -e kernel-utils-2.4-13.1.49_FC3
> error: Failed dependencies:
>    kernel-utils is needed by (installed) lm_sensors-2.8.7-2.i386
>    kernel-utils is needed by (installed) kernel-2.6.11-1.14_FC3.i686
>    kernel-utils is needed by (installed) kernel-smp-2.6.11-1.27_FC3.i686
>    kernel-utils is needed by (installed) kernel-2.6.11-1.27_FC3.i686
>
> Why is kernel-2.6.11 dependent on kernel-utils-2.4.13 I don't know...
>
>   
>  
Its documented well in http://fedoraproject.org/wiki/YumUpgradeFaq

regards
Rahul

[David Hollis]

On Wed, 2005-06-15 at 03:07 -0400, seth vidal wrote:
>  > yum-2.2.0-0.fc3  is what I was starting with.  After pulling
> down the
>  > new fedora-release and installing it, I tried to yum -y update yum.  It
>  > wanted to pull in a large amount of stuff which led to the openoffice
>  > problem.
>  
>  okay - just run:
>  yum upgrade
>  
>  and see what it does.
>  
>  -sv 
Unfortunately, I just pulled out OO and the upgrade went fine.  My next
question, though really not yum related, is:  What is the proper,
recommended, cleanest, easiest, safest way to upgrade PostgreSQL since
we've gone from 7.4.x to 8.0.x?  This certainly is something that can
bite a lot of folks that don't know that it won't start after the
upgrade.


-- 
David Hollis <dhollis(a)davehollis.com&gt;

[seth vidal]

>  Unfortunately, I just pulled out OO and the upgrade went fine.  My
> next
>  question, though really not yum related, is:  What is the proper,
>  recommended, cleanest, easiest, safest way to upgrade PostgreSQL since
>  we've gone from 7.4.x to 8.0.x?  This certainly is something that can
>  bite a lot of folks that don't know that it won't start after the
>  upgrade.
>   
I'm afraid I don't have much experience with postgresql upgrades.

anyone else know?

-sv

[Oskari Saarenmaa]

On Wed, Jun 15, 2005 at 08:56:22AM -0400, seth vidal wrote:
>  > Unfortunately, I just pulled out OO and the upgrade went fine. 
> My next
>  > question, though really not yum related, is:  What is the proper,
>  > recommended, cleanest, easiest, safest way to upgrade PostgreSQL since
>  > we've gone from 7.4.x to 8.0.x?  This certainly is something that can
>  > bite a lot of folks that don't know that it won't start after the
>  > upgrade.
>  > 
>  
>  I'm afraid I don't have much experience with postgresql upgrades.
>  
>  anyone else know? 
Here are the steps I have usually used to upgrade my PostgreSQL
installations: first dump the old database, upgrade the system and create a
fresh database, and finally reload the old data in the new database.

  # su postgres -c "pg_dumpall" > /var/lib/pgsql/backups/pg-data-7.4.dump
  # service postgresql stop
  # mv /var/lib/pgsql/data /var/lib/pgsql/backups/pg-data-7.4

  # yum update

  # service postgresql start
  # su postgres -c "psql -U postgres template1" <
/var/lib/pgsql/backups/pg-data-7.4.dump

Note that you will have to manually update the *.conf files in
/var/lib/pgsql/data as the old version's configuration files are not
neccessarily compatible with the new version.  I am not sure if 7.4 config
files can be used with 8.0, but at least version 7.3's configs weren't
usable in a 7.4 installation.

Also some of the SQL in your table defaults or custom functions might have
changed its meaning, so you should check your upgraded database to make sure
that things are as expected.  For example in 7.3 or 7.4 update the meaning
of 'now' as a column default changed to mean now() at the table creation
time instead of row creation time, and the fix was to default to now()
instead of 'now'.

So I don't think there really is a totally safe way to upgrade a PostgreSQL
installation, and I guess that's why the RPM doesn't do it automatically.

Cheers,

Oskari

[David Hollis]

On Wed, 2005-06-15 at 18:20 +0300, Oskari Saarenmaa wrote:

>  
>  Note that you will have to manually update the *.conf files in
>  /var/lib/pgsql/data as the old version's configuration files are not
>  neccessarily compatible with the new version.  I am not sure if 7.4 config
>  files can be used with 8.0, but at least version 7.3's configs weren't
>  usable in a 7.4 installation.
>  
>  Also some of the SQL in your table defaults or custom functions might have
>  changed its meaning, so you should check your upgraded database to make sure
>  that things are as expected.  For example in 7.3 or 7.4 update the meaning
>  of 'now' as a column default changed to mean now() at the table creation
>  time instead of row creation time, and the fix was to default to now()
>  instead of 'now'.
>  
>  So I don't think there really is a totally safe way to upgrade a PostgreSQL
>  installation, and I guess that's why the RPM doesn't do it automatically.
>   

This is pretty good stuff and should probably be included on the Wiki.
I can only imagine how many folks are going to be bitten by the PG
upgrade.  

-- 
David Hollis <dhollis(a)davehollis.com&gt;

[Steven Pritchard]

On Wed, Jun 15, 2005 at 01:32:50PM -0400, David Hollis wrote:
>  I can only imagine how many folks are going to be bitten by the PG
>  upgrade.   
On a similar note, I upgraded a client's box running openldap, and
after the upgrade (via anaconda) slapd wouldn't start.  Apparently db4
4.3 won't open db4 4.2 files.  :-/  (Luckily I had my FC3 notebook
handy so I could just copy /etc/openldap and /var/lib/ldap over to it
to run slapcat.)

If there isn't going to be an automatic backup script for things like
this (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=148972),
perhaps Extras should include an openldap-snapshot rpm that just
includes the cron job.  (I was thinking the other day that
postgresql-snapshot, mysql-snapshot, etc. would be good ideas too.)

Steve
-- 
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve(a)kspei.com             http://www.kspei.com/
Phone: [phone]               Mobile: [phone]

[David Hollis]

On Tue, 2005-06-14 at 15:56 -0400, David Hollis wrote:
>  On Tue, 2005-06-14 at 13:11 -0400, seth vidal wrote:
>  > On Tue, 2005-06-14 at 13:00 -0400, David Hollis wrote:
>  > > On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  > > > I've added a wiki page here:
>  > > > http://fedoraproject.org/wiki/YumUpgradeFaq
>  > > > 
>  > > > It's about upgrading from release to release via yum. If you find any
>  > > > other odd gotchas - add them there.
>  > > > 
>  > > > -sv
>  > > 
>  > > 
>  > > I'm finding that even trying to upgrade yum i have problems with
>  > > openoffice due to the package name changes.  I have:
>  > > 
>  > > libdb_cxx-4.2.so needed by openoffice.org-libs
>  > > libedataserver.so.3 needed by openoffice.org
>  > > libebook.so.8 needed by openoffice.org
>  > > 
>  > > Looks like I'll need to manually install openoffice.org-core to take
>  > > care of those
>  > 
>  > what're you upgrading FROM? Fc3?
>  
>  Yep, FC3. 

And for reference, I had version 1.1.3-11.5.0.fc3 installed.

-- 
David Hollis <dhollis(a)davehollis.com&gt;

[Todd Wells]

Using a similar procedure to the FAQ, which included everything but the yum
update yum, I did yum upgrade and get an error -  It is looking for libpython,
which is installed.

#yum upgrade 
--> Running transaction check
--> Processing Dependency: libpython2.3.so.1.0 for package: koffice
--> Finished Dependency Resolution
Error: Missing Dependency: libpython2.3.so.1.0 is needed by package 
koffice
# rpm -ql python | grep libpython2.3.so.1.0
/usr/lib/libpython2.3.so.1.0
# rpm -q yum
yum-2.2.0-0.fc3

I removed koffice, upgraded yum and am trying again.

On Tue, 14 Jun 2005, David Hollis wrote:

>  On Tue, 2005-06-14 at 15:56 -0400, David Hollis wrote:
> > On Tue, 2005-06-14 at 13:11 -0400, seth vidal wrote:
> >> On Tue, 2005-06-14 at 13:00 -0400, David Hollis wrote:
> >>> On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
> >>>> I've added a wiki page here:
> >>>> http://fedoraproject.org/wiki/YumUpgradeFaq
> >>>>
> >>>> It's about upgrading from release to release via yum. If you find
> any
> >>>> other odd gotchas - add them there.
> >>>>
> >>>> -sv
> >>>
> >>>
> >>> I'm finding that even trying to upgrade yum i have problems with
> >>> openoffice due to the package name changes.  I have:
> >>>
> >>> libdb_cxx-4.2.so needed by openoffice.org-libs
> >>> libedataserver.so.3 needed by openoffice.org
> >>> libebook.so.8 needed by openoffice.org
> >>>
> >>> Looks like I'll need to manually install openoffice.org-core to take
> >>> care of those
> >>
> >> what're you upgrading FROM? Fc3?
> >
> > Yep, FC3.
>
>
>  And for reference, I had version 1.1.3-11.5.0.fc3 installed.
>
>

[seth vidal]

On Tue, 2005-06-14 at 14:09 -0700, Todd Wells wrote:
>  Using a similar procedure to the FAQ, which included everything but
> the yum
>  update yum, I did yum upgrade and get an error -  It is looking for libpython,
>  which is installed.
>  
>  #yum upgrade 
>  --> Running transaction check
>  --> Processing Dependency: libpython2.3.so.1.0 for package: koffice
>  --> Finished Dependency Resolution
>  Error: Missing Dependency: libpython2.3.so.1.0 is needed by package 
>  koffice
>  # rpm -ql python | grep libpython2.3.so.1.0
>  /usr/lib/libpython2.3.so.1.0
>  # rpm -q yum
>  yum-2.2.0-0.fc3
>  
>  I removed koffice, upgraded yum and am trying again. 
koffice was removed from core and not picked up by anyone else and/or
obsoleted so it will need to be removed to upgrade your whole system.

-sv

[Jesse Keating]

On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  I've added a wiki page here:
>  http://fedoraproject.org/wiki/YumUpgradeFaq
>  
>  It's about upgrading from release to release via yum. If you find any
>  other odd gotchas - add them there. 
This works for going from FC4test3 to FC4 Final as well, I tested on x86
(with a lot of extras and livna installed, so make sure your repos for
extras and livna is updated as well).

-- 
Jesse Keating RHCE      (http://geek.j2solutions.net)
Fedora Legacy Team      (http://www.fedoralegacy.org)
GPG Public Key
(http://geek.j2solutions.net/jkeating.j2solutions.pub)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating

[David Hollis]

On Mon, 2005-06-13 at 02:08 -0400, seth vidal wrote:
>  I've added a wiki page here:
>  http://fedoraproject.org/wiki/YumUpgradeFaq
>  
>  It's about upgrading from release to release via yum. If you find any
>  other odd gotchas - add them there.
>   
A new problem that has popped up twice is that after getting 'yum
upgrade yum' to work, yum no longer works!  It says that it can't find
it's libraries to run.  The fix is to upgrade rpm-* (which leads me to
believe that rpm-python is the culprit) and all is well again.

-- 
David Hollis <dhollis(a)davehollis.com&gt;