Bug#994388: dpkg currently warning about merged-usr systems
On Fri, Apr 08, 2022 at 09:39:30AM -0700, Josh Triplett wrote:
> It sounds like at least one patch has already been rejected, not with comments about the patch needing work (which it absolutely does), but AIUI with "usrmerge is broken by design". That seems like sufficient proof that the problem is not a lack of engagement or patches. I don't think it's reasonable to expect further one-sided engagement by way of further "proof" of futility. That's leaving aside the (likely also accurate) expectation based on reported experiences with multiarch that any patch will go through extreme amounts of rework and iteration in that hostile environment, even *if* there were enough trust left to expect good faith.
While this may sound convincing at first, there is another aspect to it.
We basically agree that dpkg is buggy with regard to our current
aliasing approach. We vehemently disagree on how severe those bugs are,
but at least we've stopped selling them as features it seems. So sooner
or later, we want dpkg fixed. Now the ctte cannot tell anyone to fix
dpkg. All it can do is select between available options. And while
Guillem has his own reasons on disliking the existing patch everyone
else basically agrees that it is not ready for other reasons. If that
patch were to be decided upon by the ctte in its current form, the
answer would most likely be "no", not due to change in principle, but
due to the patch being unfinished. So even if Guillem is not being
constructive here, that does not remove the need to fix dpkg. And if
Guillem does not want to review the patch in a constructive way, then
maybe we should not consider his review relevant. Also putting it to
test would be a relevant data point. (Rumor has it that someone is
working on the latter. :)
Helmut
Reply to: