[arch-general] Still Glibc problems

[Norbert Zeh]

D. R. Evans [2012.07.20 1541 -0600]:
> Norbert Zeh said the following at 07/19/2012 06:08 PM :
> 
> > 
> > Well, the filesystem instructions are older and applied at the time the glibc
> > upgrade was not an issue yet.  Combining the two instructions, I would guess the
> > following should work:
> > 
> > pacman -Syu --ignore filesystem --ignore glibc
> 
> OK.
> 
> > pacman -S --force filesystem --ignore glibc
> 
> OK.
> 
> > pacman -Sd <everything you couldn't upgrade due to ignored glibc>
> 
> OK. FWIW, the list of packages was:
> 
> attica  binutils  boost-libs  eclipse  eclipse-cdt  faac  ffmpeg  gcc
> gcc-libs  gnutls  grep  gstreamer0.10-bad-plugins  icu  jedit  kdebase-runtime
>  kdelibs  libcups  libgl  liblrdf  libmp4v2  libproxy  libtool  libva  linux
> mesa mkinitcpio  openjdk6  pcre  poppler  poppler-glib  qt  raptor  soprano
> swig  xine-lib  xorg-server-xephyr
> 
> > pacman -Su
> > 
> 
> Not OK:
> 
> > [root at shack n7dr]# pacman -Su
> > :: Starting full system upgrade...
> > resolving dependencies...
> > looking for inter-conflicts...
> > 
> > Targets (1): glibc-2.16.0-2
> > 
> > Total Installed Size:   33.94 MiB
> > Net Upgrade Size:       0.83 MiB
> > 
> > Proceed with installation? [Y/n] 
> > (1/1) checking package integrity                                                                                                                  [##########################################################################################] 100%
> > (1/1) loading package files                                                                                                                       [##########################################################################################] 100%
> > (1/1) checking for file conflicts                                                                                                                 [##########################################################################################] 100%
> > error: failed to commit transaction (conflicting files)
> > glibc: /lib exists in filesystem
> > Errors occurred, no packages were upgraded.

I got the same error at that point.  What this means is that you either have
some unowned (by any package) files in /lib (/lib/modules/* is a good candidate)
or you have some other packages (most likely from AUR) owning files under /lib.
The wiki page explains well how to look for them.  At least, I followed those
instructions and managed to identify the packages that blocked the upgrade.  The
key here really seems to be to make sure that glibc is the only package which at
this point owns anything under /lib.  I think in my case it also helped to
uninstall some packages and reinstall them after the glibc upgrade.  Keep
pushing, you're almost there ;)

Cheers,
Norbert