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

[Dale Scheetz <dwarf@polaris.net>]

On Thu, 19 Nov 1998, Jason Gunthorpe wrote:

> 
> On Thu, 19 Nov 1998, Gergely Madarasz wrote:
> 
> > As I noted in one of my previous posts, please add a conflict against
> > current libstdc++ because this new libc will break all c++ apps linked
> > against libstdc++2.9 (i'm not sure if it is just the library or the apps
> > too :( ), like apt, dselect, etc...
> > And please add conflicts to broken dpkg and apt too so we dont get a
> > broken package management system. I guess then these packages will have to
> > be compiled with dpkg from hamm.
> 
> APT 0.1.8 should work perfectly fine (only 0.1.9 will have problems) with
> the new libc, it was compiled against hamm. http://www.debian.org/~jgg/
> I'll go about getting a new out out when a new libstdc++ is available. 

Anything compiled against the hamm glibc will work with any of the 2.0.7u
releases, including the fixed one I am preparing.

It is only those packages compiled against 2.0.7u that are at risk once
the fixed version is installed.

I'm not convinced that Conflicts: is a reasonable way to deal with this
problem. The size of this field in libc6 is already large, and none of
them can ever be removed, but I don't see any other way to move forward
here.

Waiting is,

Dwarf
--
_-_-_-_-_-   Author of "The Debian Linux User's Guide"  _-_-_-_-_-_-

aka   Dale Scheetz                   Phone:   1 (850) 656-9769
      Flexible Software              11000 McCrackin Road
      e-mail:  dwarf@polaris.net     Tallahassee, FL  32308

_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-