On Wed, Jun 29, 2011 at 10:48:49AM -0500, Jonathan Nieder wrote: > Hi Andreas, > > Andreas Mohr wrote: > > > Don't tell me that this upgrade just successfully and singlehandedly > > broke any and all libc4/5 compat... (not that I personally would still much > > rely on that at this moment ;-)). > > This upgrade indeed broke libc4/5 compat. If there is anyone still > using it (you?), my hunch is that the best thing to do is to get in > touch with us and we can work on an unofficial package to get it > working again using the new paths with <triplet> in the name. > Supporting installations with libc installed at two paths would be > much more painful.
If I still had that main Debian gateway which had been running since 1996 (usability-killed recently, by boot/network setup complications after that ill-fated Squeeze upgrade, read: dead box at a most unwelcome time), then I'd have remained happy to use the binary-only estic config app for ISTEC PBXes. And the other box won't be available to run it either (has been breakage-converted to Windoze 7 e.g. due to annoyances caused by idiotic Firefox (and thus: iceweasel) versioning incompatible with similarly idiotic versioning expectations of the banking site [but sure, they'll readily support IE6]). Apart from that, no more use cases for libc5 stuff here. Since you appear to say that current status is official breakage of libc4/5, the (very confusing) abort message should best be reworded to indicate that this applies to "officially" managed binaries as well (e.g. ldso package etc.) and not just rogue manually installed ones. And perhaps even directly indicate that 4/5 support is currently not offered any more, which is the reason for the conflict. Thanks a lot for your support! Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
