Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12516 - Glibc upgrade to 2.9-2 repeated at each system upgrade

Attached to Project: Arch Linux
Opened by mutlu inek (mutlu_inek) - Saturday, 20 December 2008, 15:34 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 22 December 2008, 15:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a curious problem with upgrading glibc. It seems to be up-to-date, but keeps updating to the present version each time I issue "pacman -Su." pacman.log does show the update to have been successful, but a second system upgrade updates glibc again.


Yaourt also confirms glibc 2.9-2 to be installed:

$ yaourt glibc
1 core/glibc 2.9-2 [installed] (base)
GNU C Library



If I update, this happens:

$ sudo pacman -Syu
Password:
:: Synchronizing package databases...
kde-unstable is up to date
core is up to date
extra 414.1K 388.7K/s 00:00:01 [####################################################################################] 100%
community 348.7K 377.5K/s 00:00:01 [####################################################################################] 100%
unstable is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
warning: akonadi: local (1.0.80-2) is newer than kde-unstable (1.0.80-1)
warning: mysql: local (5.0.68-2) is newer than extra (5.0.68-1)
warning: phonon: local (4.2.80-2) is newer than kde-unstable (4.2.80-1)
resolving dependencies...
looking for inter-conflicts...

Targets (1): glibc-2.9-2

Total Download Size: 0.00 MB
Total Installed Size: 33.92 MB

Proceed with installation? [Y/n] Y
checking package integrity...
(1/1) checking for file conflicts [####################################################################################] 100%
(1/1) upgrading glibc [####################################################################################] 100%
Generating locales...
en_US.UTF-8... done
Generation complete.



A second (and third, ...) upgrade repeats the installation:

$ sudo pacman -Su
:: Starting full system upgrade...
warning: akonadi: local (1.0.80-2) is newer than kde-unstable (1.0.80-1)
warning: mysql: local (5.0.68-2) is newer than extra (5.0.68-1)
warning: phonon: local (4.2.80-2) is newer than kde-unstable (4.2.80-1)
resolving dependencies...
looking for inter-conflicts...

Targets (1): glibc-2.9-2

Total Download Size: 0.00 MB
Total Installed Size: 33.92 MB

Proceed with installation? [Y/n] n
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 22 December 2008, 15:53 GMT
Reason for closing:  Not a bug
Comment by Andreas Radke (AndyRTR) - Saturday, 20 December 2008, 21:00 GMT
please check for curruption in /var/lib/pacman/local/glibc* and double fresh your repo list with pacman -Syy. also check if you applied all changes from /etc/pacman.conf.pacnew.

this is surely a local issue on your system.
Comment by Alessandro Doro (adoroo) - Sunday, 21 December 2008, 15:43 GMT
Or try to run pacman as root (no sudo).
It could be a permission problem in /var/lib/pacman/local/glibc*; see  FS#12333  and  FS#12263 .
Comment by mutlu inek (mutlu_inek) - Sunday, 21 December 2008, 21:46 GMT
The files in /var/lib/pacman/local/glibc* look fine. I compared those for glibc-2.9-2 with the 2.8-3 entries and nothing looks corrupted. Permissions are the same. Running pacman -Su as root (not sudo) does not help, either.

My /etc/pacman.conf is fine. I looked at the pacman.conf.pacnew (which is from August) and nothing seems to be missing. I attached the current pacman.conf.

   pacman.conf (2.6 KiB)
Comment by Jan de Groot (JGC) - Monday, 22 December 2008, 11:38 GMT
Do you have multiple glibc-* entries in /var/lib/pacman/local?
Comment by mutlu inek (mutlu_inek) - Monday, 22 December 2008, 14:21 GMT
Yes. Duh... I didn't realize the weirdness of this. This does seem to be the culprit. Or is it a symptom?

$ ls -la /var/lib/pacman/local/glibc*
/var/lib/pacman/local/glibc-2.8-3:
total 100
drwxr-xr-x 2 root root 4096 2008-09-04 01:08 .
drwxr-xr-x 744 root root 40960 2008-12-21 21:17 ..
-rw-r--r-- 1 root root 808 2008-09-01 03:57 changelog
-rw-r--r-- 1 root root 46 2008-09-04 01:08 depends
-rw-r--r-- 1 root root 292 2008-09-04 01:08 desc
-rw-r--r-- 1 root root 38788 2008-09-04 01:08 files
-rw-r--r-- 1 root root 4009 2008-09-01 03:57 install

/var/lib/pacman/local/glibc-2.9-2:
total 100
drwxr-xr-x 2 root root 4096 2008-12-21 21:17 .
drwxr-xr-x 744 root root 40960 2008-12-21 21:17 ..
-rw-r--r-- 1 root root 916 2008-12-14 14:18 changelog
-rw-r--r-- 1 root root 54 2008-12-21 21:17 depends
-rw-r--r-- 1 root root 292 2008-12-21 21:17 desc
-rw-r--r-- 1 root root 39202 2008-12-21 21:17 files
-rw-r--r-- 1 root root 3949 2008-12-14 14:18 install
Comment by mutlu inek (mutlu_inek) - Monday, 22 December 2008, 14:31 GMT
I moved the glibc-2.8-3 directory out of /var/lib/pacman/local and did pacman -Rd glibc & pacman -S glibc. Problem solved! Thanks a lot! I should have seen it myself.

The only thing I wonder about is how those files could remain in /var/lib/pacman/local.

Loading...