So what's it been like half a decade that debian has been doing this multiarch stuff, and I still have to make local changes to fundamental things like glibc just to get an equivalent install to what the distro gets?

As the GLIBC release manager I just want to install the thing on one of
my sparc machines and do some basic install smoke testing.  But I've lost several afternoons trying to figure out what still-not-merged-upstream local changes I have to apply to get the multiarch stuff to all pan out properly.  Otherwise I'll get a botched install and it will have nothing to do with any bug upstream.

This is rather unacceptable.  I really don't care what gains debian gets from this mutliarch crap, you are crippling the upstream maintainers from testing these fundamental tools (and thus working more closely with you) by doing things like this.

If it's going to take more than a year to upstream your stuff, you can't deploy it in the distro first.  Otherwise you have absolutely no incentive to do whatever it takes to get upstream acceptance of all of your changes, and it's just going to languish and cause insane amounts of pain for any upstream maintainer who wants to get work done on your system.

This sounds bitter, but I've been dealing with this crap this entire time in all of gcc, binutils, and glibc.  It's a complete nightmare seemingly without end.
Shared publiclyView activity