On 25/03/2022 16:25, Russ Allbery wrote:
Luca Boccassi <bl...@debian.org> writes:
But anyway, it turns out it's all moot because - drum roll - there is a
patch:
https://0x0.st/oNFG.diff
This was shared just now on #debian-devel IRC by user 'uau', linked
here with explicit permission.
This is fantastic, thank you so much! Is the author following this
thread? Could they get this patch into a git repository forked from dpkg
so that interested parties could start iterating? I have some concrete
feedback on the patch, and obviously there are a few things that need to
be done before it really could be merged (such as handling the other
architecture directories as noted in the patch introduction), so it needs
some iteration.
That's probably not a good topic for a TC bug, and for various reasons it
may not be best to do early iteration on the dpkg mailing list, so we may
need some other forum. I'm happy to help out as I have time with patch
review and further feedback.
I'd like to second Russ' note that it's great that a patch exists :)
I'd also like to second the note that the TC (and this bug in
particular) is emphatically not the place to be working on this patch.
Also, I think the presence and suitability of this patch doesn't change
the discussion about the warnings that dpkg is currently emitting, which
are the subject of this bug.
FTR, I think the current warning is inappropriate; a reportbug script
that flags the known issues with dpkg's support for /usr-merge seems
like the more appropriate place.
Regards,
Matthew
