[Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

Andrea Bolognani eof at kiyuko.org
Sat Jun 1 11:11:08 BST 2024


On Thu, May 30, 2024 at 08:05:34PM +0200, Chris Hofstaedtler wrote:
> Hi,
> 
> please make sure the usrmerge changes land in trixie well before the
> transition freeze.
> Now would be a great time.

I have been making slow but steady progress over the past months. I
hope to have something suitable for initial review in a few weeks.

> On Tue, Feb 27, 2024 at 10:53:12PM +0100, Andrea Bolognani wrote:
> > Suppose that I made the usr-merge upload today, and the package
> > restructure upload in a month. At that point, dumat would detect that
> > file loss could occur, report it and... What then?
> 
> Then you get to fix them manually in various maintainer scripts,
> hoping they can be fixed.

That doesn't sound very appealing. The libvirt package is already
fairly complex, I'd rather not make things even worse if it can be
avoided.

This further convinces me that it would be better to perform all file
moves as part of a single upload to experimental, lowering the
chances that broken packages make their way to unstable and testing.

> > Have reliable mitigations been developed for all possible file loss
> > scenarios?  Is it guaranteed that such mitigations, when applied,
> > will protect from file loss not just the people running stable, but
> > also those running testing and unstable?
> 
> No. The mitigations are fragile; bugs in dpkg and/or policy have
> been discovered. Extensive testing is required for all scenarios you
> can envision.
> Even then, some things are just not fixable in a reliable manner.

Not exactly confidence-inducing :) Hopefully moving a few files in
what is a relatively leaf package is among the easiest and most
tested scenarios.

> > My instincts tell me that it would be much easier to reason about
> > this if the two transitions happened at the same time rather than
> > potentially months apart. This is my main concern with applying the
> > usr-merge changes when we still don't have a clear picture of what
> > the final state of the package will look like.
> 
> The best is to have as few file moves as possible in trixie. In
> forky, moving files becomes easier again.

forky is ~3 years away though... That's a long time to deliver
changes that are, realistically speaking, already overdue.

-- 
Andrea Bolognani <eof at kiyuko.org>
Resistance is futile, you will be garbage collected.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20240601/f8e1bd7a/attachment.sig>


More information about the Pkg-libvirt-maintainers mailing list