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

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

Luca Boccassi <bluca@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.

(The biggest concrete piece of feedback that I have is that there is some
weirdness with how searches work that I believe is a result of not having
dpkg convert all of its on-disk databases in a flag-day change.  The point
about having to convert triggers on the fly is very good and one that I
hadn't picked up on before, but I think a flag-day conversion of some of
the other databases would still be better to avoid some edge cases.  I
also suspect it will be easier to merge if we can find a way to provide
cleaner support for non-merged systems even if Debian itself will no
longer support such systems, and I don't think it would be *too*
challenging to do so.  There's also just some super-minor stuff like tabs
vs. spaces, formatting of function signatures, etc., that I'm happy to
help clean up to smooth the path.)

Russ Allbery (rra@debian.org)              <https://www.eyrie.org/~eagle/>

Reply to: