Re: Is an MBF and unblock for packages introducing new files in /bin or /sbin or /lib in Bookworm acceptable at this stage?
Hi Luca,
On Mon, 22 May 2023 00:03:46 +0100
Luca Boccassi <bluca@debian.org> wrote:
> On Sun, 21 May 2023 at 20:31, Luca Boccassi <bluca@debian.org> wrote:
> >
> > On Sun, 21 May 2023 at 20:29, Christoph Berg <myon@debian.org>
> > wrote:
> > >
> > > Re: Luca Boccassi
> > > > If we were to do a MBF against packages that in _Bookworm_ have
> > > > introduced new files in /bin, /sbin or /lib*, would you accept
> > > > the consequent mass unblock request?
> > >
> > > Fwiw, I would restrict that to packages that didn't have files in
> > > these directories before. Telling a maintainer that they should
> > > continue install foo.service to /lib/systemd, but the newly
> > > introduced bar.service needs to got to /usr/lib/systemd seems
> > > like a lot of extra work and asking for bugs to happen.
> >
> > Yes, this (the number of files mentioned) already excludes things
> > that are installed by dh addons and so, such as unit files.
>
> Here's the list of affected packages for binaries:
>
> abpoa
> eprover
> coq-hierarchy-builder
> intel-cmt-cat
> nbd-server
> systemd
> toybox
> drbd-utils
> finit
> finit-plugins
> multipath-tools
> runit
Please exclude runit from the list as /lib/runit/ was not empty in
Bullseye.
Regards,
Lorenzo
> nut-modbus
> nut-i2c
> nut-server
> open-iscsi
> openrc
> resolvconf
> iproute2
> f2fs-tools
> ifupdown-ng
> multipath-tools
> libpam-modules-bin
>
> PAM modules:
>
> cockpit-tests
> libpam-python
> libpam-alreadyloggedin
> libpam-chroot
> google-compute-engine-oslogin
> systemd-homed
>
> Library new ABI or minor versions:
>
> libbrlapi0.8
> libc6
> libcap2
> libcgroup2
> libdbus-1-3
> libdmraid1.0.0.rc16
> libcap-ng0
> libexpat1
> libfuse3-3
> libgpg-error0
> xfsprogs
> libreadline8
> libkeyutils1
> liblzma5
> libncurses6
> libncursesw6
> libntfs-3g89
> libnutclient2
> libnutscan2
> libparted-fs-resize0
> libparted2
> libproc2-0
> libsepol2
> libtinfo6
> libupsclient6
> zlib1g
>
> The libraries are just minor version increase in most cases, so the
> symlinks are often unchanged and cannot be moved, so I'd leave them
> where they are. So that's 23 packages for binaries and 5 for PAM
> modules moving from un-triplet to triplet location.
>
> Kind regards,
> Luca Boccassi
>
Reply to: