[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#994388: dpkg currently warning about merged-usr systems

On Fri, 2022-03-25 at 14:30 +0100, Helmut Grohne wrote:
> On Fri, Mar 25, 2022 at 10:46:01AM +0000, Luca Boccassi wrote:
> > Let me reverse the question: this stuff has been known and going on for
> > what, 3 years? Why do _you_ think it is that nobody has stepped up to
> > write a patch? In the same time lapse everybody involved has written
> > mountains of code elsewhere. Why do you think this is different?
> I think there are basically three kinds of people in this debate. I'm
> overgeneralizing a little, but I hope you get the message anyway.
> I call the first group "proponents". Those want the /usr-merge to
> happen. Their use cases are not impacted by dpkg -S being broken or dpkg
> deleting files during moves, so they don't care much about the remaining
> bugs. Why would they write the code? It all just works for them.  Most
> likely, Luca is part of this group.

I am part of that group, and that is definitely _not_ why I wouldn't
touch dpkg with a barge pole as things stand (and have stood for
years). You are making a gigantic leap with that assumption, not sure
what you base it on. As a downstream and upstream maintainer in several
large projects I fix things that don't impact me all the time, all over
the place.

But anyway, it turns out it's all moot because - drum roll - there is a


This was shared just now on #debian-devel IRC by user 'uau', linked
here with explicit permission.

So it looks like you, Russ and others who chimed in this thread should
now be in a position to test your theory that a missing patch was the
only issue. Care to take it forward?

Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: