Re: glibc recompiling was Re: libc resolver problem solved (critical bug)

[Richard Braakman <dark@xs4all.nl>]

Hi... sorry for jumping into this thread so late; I've been recovering
from SANE :)

I checked dpkg 1.4.0.31, and it seems to me that only dselect will break when
libc6 is upgraded:

% nm -oDp usr/lib/libdpkg.so.0.0.0 usr/bin/dpkg usr/bin/dpkg-deb usr/bin/dpkg-split usr/bin/md5sum usr/bin/dselect sbin/start-stop-daemon | grep register_frame_info
usr/bin/dselect:         U __deregister_frame_info
usr/bin/dselect:         U __register_frame_info

(The command-line for nm lists all ELF binaries in the dpkg package)

dselect is the only program that requires __register_frame_info as a 
dynamic symbol.  This is what I expected, since dselect is linked with
libstdc++.

The essential packaging tools (dpkg, dpkg-deb) will probably _not_ break
when a fixed libc6 is installed.

Dale, given this, do you think you can skip the Conflicts entries?
Is it worthwhile to have this tested?

Richard Braakman