Re: transition to usrmerge to start around 2022-09-15 (next Thursday)
Luca Boccassi <email@example.com> writes:
> Nothing was ignored.
In the spirit of good faith I'll assume you meant "Nothing new was
It's a fact that you are ignoring a few issues caused by usrmerge. This
is thoroughly documented in the BTS.
Arrogance is not on the bug list, but maybe it should be? It's
definitely something Debian will have to work on before releasing with
usrmerge in the current state.
usrmerge adds bugs which you so far have been unable to fix. That's
nothing to be ashamed of. Just try to be honest about it.
I assume that you plan to fix the bugs before the release. Note that the
CTTE did not request the addition of any bugs, or make any exceptions
for the usrmerge package. What to do about usrmerge if it conflicts
with other goals is not decided yet.
So if you don't want another round of pointless discussions, then I
suggest that you start working on those bugs now. That's the smart thing
to do if you want to make *sure* usrmerge is part of the release. If
there is no conflict between release goals, then there will be no need
for a discussion.
I find it quite disappointing to read https://bugs.debian.org/848622 . I
don't know if it is arrogance or ignorance, but this bug is undoubtedly
caused by usrmerge:
frtest2:~# ls -l /usr/bin/bash
-rwxr-xr-x 1 root root 1283864 Aug 25 16:03 /usr/bin/bash
frtest2:~# dpkg -S /usr/bin/bash
dpkg-query: no path found matching pattern /usr/bin/bash
Pointing at other maintainers/packages to fix your bugs is anti-social.
Don't force Debian decide whether the usrmerge bugs should be accepted
in the next release. Just fix them. The alternative is ugly. And I'm
not thinking about the actual bugs, but about the discussion...
It's fine to oversell the advantages of usrmerge. It's not fine to try
to hide the disadvantages.