Роман Кирилич wrote:
> Hi! I'm trying ro upgrade glibc-2.3.6-2 and get this:
>
> Targets: kernel-headers-2.6.12.0-1 glibc-2.4-2
>
> Total Package Size:   10.9 MB
>
> Proceed with upgrade? [Y/n]
> checking package integrity... done.
> loading package data... done.
> checking for file conflicts...
> error: the following file conflicts were found:
>   glibc: /usr/include/bits/link.h: exists in filesystem
>   glibc: /usr/include/bits/socket2.h: exists in filesystem
>   glibc: /usr/include/bits/unistd.h: exists in filesystem
>   glibc: /usr/include/gnu/stubs-32.h: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1025.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1122.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1137.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1153.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1154.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1155.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1156.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1157.so: exists in filesystem
>   glibc: /usr/lib/gconv/IBM1158.so: exists in filesystem
>   glibc: /usr/share/locale/ru/LC_MESSAGES/libc.mo: exists in filesystem
>   glibc: /usr/share/locale/rw/LC_MESSAGES/libc.mo: exists in filesystem
>
>
> errors occurred, no packages were upgraded.
>
> This is strange. My other Linux machines upgraded without file
> conflicts. I don't remember which glibc was on them though.
>
>   

All those files are included in glibc 2.4-2, but not in 2.3.6-2, so it 
is safe to force the install - pacman -Sf. As to why it happened, did 
you have 2.4 on the machine before, maybe when it was in testing, 
followed by a downgrade to 2.3.6 in current? I seem to remember someone 
else having this problem with leftover files in the same situation.

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to