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. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
