[arch-dev-public] When to remove provides/conflicts/replaces?

Thomas Bächler thomas at archlinux.org
Sun Jun 13 07:53:27 EDT 2010

Am 13.06.2010 13:18, schrieb Thomas Bächler:
> I'd leave the replaces in for mktemp at least, a system from early 2008
> might still be upgraded.

I just tried to upgrade a system I hadn't touched since June 2007:

The problem was this:
debug: missing dependency 'sh' for package 'xz'
which triggered bash installation. I created a dummy package called 'sh'
with nothing in it:

And now there is fun:
# pacman -Syu
pacman: /lib/libc.so.6: version `GLIBC_2.7' not found (required by
pacman: /lib/libc.so.6: version `GLIBC_2.7' not found (required by

This system has glibc 2.6.1 installed. I am running this in a chroot
right now. On a real machine, I could extract a new glibc manually and
try to use that to upgrade the 'glibc' package properly. However, if I
was on the machine itself, I would be running, making it
impossible to use this glibc version.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20100613/4885430f/attachment.bin>

More information about the arch-dev-public mailing list