Andreas Metzler wrote... > I am all for declaring a cutoff date (and release) which makes usrmerge > mandatory and the only supported setup. (Or alternatively make usrmerge > an unsupported setup.) The current state where we are trying to support > both and end up dealing with fallout and cannot make real progress to > the clean state (bash being shipped as /usr/bin/bash and therefore dpkg > knowing about it) is a waste of developer time.
Indeed. I just lost two hours to realize the build failures of one of my
packages resulted from upstream being post-usrmerge in mind while the
buildds are appearently pre-, and with my local build chroots already
migrated I hadn't noticed beforehand. And now I can only hope the
resulting binaries will run everywhere. The sooner we get out of this
mess the better.
Christoph
signature.asc
Description: PGP signature
