CentOS - Oct 2006 - Yum, duplicate packages, 4.3->4.4 upgrade.

Hi,

I am running a CentOS 4.3 machine.  I wish to move on to 4.4.
My problem is that I have some 60 duplicate packages listed
below.  The kernel and gpg-pubkey packages are different
versions of the same (none for the gpg) architecture.  All the
rest are a x86_64 and i[356]86 pairs.

1. Is this a problem?

2. If yes, what should I do?
   a) remove the duplicates (the i[356]86) and then 4.3 -> 4.4?
   b) 4.3 -> 4.4 and only after that remove duplicates?
   c) something else?

3. How to actually do the removal? Simply 'yum remove ...' or are 
   there some packages that require special care? 

4. I have enabled the dries, kbsingh, and rpmforge, repositories
   for few packages (acroread, pine,...).  However, I didn't
   keep track which packages come from those repos so I can't 
   apply the 'includepkgs' instruction on them.  What's the 
   easiest way to recover that information?  (Default
   'yum list installed' doesn't provide the repository.)

Thanks in advance,
       Itay

################################################################
  List of packages follows:
  prompt> rpm -qa --qf "%{NAME}\n" | sort | uniq -d
################################################################

alsa-lib
atk
audiofile
audit-libs
bzip2-libs
compat-libstdc++-33
cracklib
cracklib-dicts
cyrus-sasl
db4
dbus
dbus-glib
device-mapper
e2fsprogs
esound
evolution-data-server
expat
fontconfig
freetype
gamin
GConf2
gdbm
glib2
glibc
gnome-vfs2
gnutls
gpg-pubkey
gtk2
hal
kernel
kernel-devel
kernel-smp
krb5-libs
libart_lgpl
libbonobo
libcap
libgcc
libgcrypt
libgnome
libgpg-error
libIDL
libjpeg
libpng
libselinux
libsoup
libstdc++
libtiff
libxml2
openldap
openssl
ORBit2
pam
pango
popt
redhat-artwork
startup-notification
xorg-x11-libs
xorg-x11-Mesa-libGL
zlib

################################################################
    End of list
################################################################

On 10/9/06, itayf at nospammail.net <itayf at nospammail.net>
wrote:
>
> I am running a CentOS 4.3 machine.  I wish to move on to 4.4.
> My problem is that I have some 60 duplicate packages listed
> below.
Some of those are supposed to be duplicated.  If you have an x86_64
architecture, you get both the 64-bit and 32-bit versions of some
packages.

See the thread "Yum upgrade to 4.4 problem" in the August 31 - early
September time span in the CentOS list archives at
http://lists.centos.org/pipermail/centos/.

In particular this:
>   prompt> rpm -qa --qf "%{NAME}\n" | sort | uniq -d
is the wrong "rpm" incantation to detect the real duplications on
x86_64.  You need to
include %{ARCH} in there somewhere.

On Mon, 2006-10-09 at 17:15 +0200, itayf at nospammail.net
wrote:
> Hi,
> 
> <snip>
> 4. I have enabled the dries, kbsingh, and rpmforge, repositories
>    for few packages (acroread, pine,...).  However, I didn't
>    keep track which packages come from those repos so I can't 
>    apply the 'includepkgs' instruction on them.  What's the 
>    easiest way to recover that information?  (Default
>    'yum list installed' doesn't provide the repository.)
I  /var/log/rpmpkgs is a (weeklyupdated?) list of file names. Some have
".rf" in them, other "plus" etc. This should tell you for
most packages
from where they came.

I would then read up on some of the yum stuff (plugins) and use a
combination of "includepkgs=", "exclude=" and
"protect=" to get you
going. Set this stuff up before you do any other changes.
> 
> Thanks in advance,
>        Itay
> <snip pkg list>
HTH
--
Bill

On Mon, 9 Oct 2006, itayf at nospammail.net wrote:
> Date: Mon, 9 Oct 2006 17:15:28 +0200 (IST)
> From:  <itayf at nospammail.net>
> Reply-To: CentOS mailing list <centos at centos.org>
> To:  <centos at centos.org>
> Subject: [CentOS] Yum, duplicate packages, 4.3->4.4 upgrade.
> 
> 
> Hi,
> 
> I am running a CentOS 4.3 machine.  I wish to move on to 4.4.
> My problem is that I have some 60 duplicate packages listed
> below.  The kernel and gpg-pubkey packages are different
> versions of the same (none for the gpg) architecture.  All the
> rest are a x86_64 and i[356]86 pairs.
Thanks to Will and Bart for the help so far.

'yum deplist' on the list of installed packages revealed many 
cases in which both x86_64 and i[356]86 packages provide the same 
dependency.  Example:

package: gdbm.x86_64 1.8.0-24
  dependency: libc.so.6()(64bit)
   provider: glibc.x86_64 2.3.4-2.25
  dependency: /sbin/ldconfig
   provider: glibc.i686 2.3.4-2.25	<<=============   provider:
glibc.x86_64 2.3.4-2.25	<<=============  dependency:
libc.so.6(GLIBC_2.2.5)(64bit)
   provider: glibc.x86_64 2.3.4-2.25

Note that both glibc.i686 and glibc.x86_64 are installed on my 
machine. 
I'm sorry if this is a newbie question - but how do I proceed 
from here?
Shouldn't I try to remove the i686 package provided that all its 
dependencies are satisfied by the x86_64 package as above?

	Thanks,
	Itay