Ansgar dijo [Thu, May 18, 2023 at 07:55:03PM +0200]: > Why not? > > Do you think the implications of removing the warning are unclear? > > Do you think we need to explore alternative solutions?
(I am no longer part of the Committee, answering just as another developer) dpkg has many bits that make it special. It has been discussed whethe dpkg should be a native package or it should become non-native; if it were non-native, having a patch that contradicts the upstream author's wishes would be easier (and I'm not saying that I'd be up for patching this warning out as it is). If we were to force a patch silencing out this warning right now and for all of the Bookworm cycle, and the dpkg authors disagree with it, they could remove (even omit to include it) in any updates. Upstream has repeatedly expressed their opposition to the way usrmerge has been brought forward, and the warning silenced specifically for Debian is already the best compromise situation we have been able to reach -- even though we are aware the situation is far from ideal.