Re: dpkg 220.127.116.11.1 bug
Carlos Carvalho <firstname.lastname@example.org> writes:
> dpkg is broken, and libc for x86 is also broken...
Uh, yeah, right. a) please stop this x86 stuff, it's ia32, m68k and
probably others, b) what were they meant to do? Break binary
compatibility in glibc 2.0.x when 2.0.x was deployed? That would be
good, oh yeah. *narf*
What was done on ia32/m68k et al. is the only decision that makes
sense afaics; it allows binary compatibility to be broken at a
suitable time (i.e. the next major release of glibc, or whatever).
> there's a libc bug on x86.
~Yawn And Walk North~
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org