Hi Release team,
Bug #1017441 was filed against debhelper in related to a change to
dh_installtmpfiles that made it apply an unconditional dependency on
"systemd | systemd-tmpfiles".
My concern is not the dependency itself (as I understand it, the systemd
GR ratifies that). What might be concerning is that the dependency
appears in lower levels of the build stack causing additional package to
appear in our chroot according to Santiago Vila (quoted below in full).
The bug was originally filed as RC but has now been degraded to
wishlist. Admittedly, it is not clear to me the downgrade was done with
the knowledge that the bug affected our chroots.
The question is whether you feel this is an RC bug and would like me to
revert the change immediately / before the transition freeze?
The alternative is you do not feel this bug is concerning/RC in which
case I will keep the current version until people have come to a
conclusion on the bug.
What is your view on the above question?
Thanks,
~Niels
PS: Please include the bug in CC with your (formal) answer to that question.
Santiago Vila:
Hello.
As of today, upgrading a sid chroot containing debhelper to the sid of
today, systemd, mount, and several other packages are installed into the
chroot. This is usually undesired because we want build chroots to be as
minimal as possible.
Users of debootstrap can certainly use --include and --exclude to
fine-tune the contents of the chroot, but as a user of debootstrap, I
would expect it to do the right thing (minimal chroot) by default and
without having to fine-tune it.
On amd64, I've checked that installing systemd-standalone-tmpfiles
allows systemd and all the extra packages to be removed again.
So I wonder if reversing the dependency created by debhelper:
systemd | systemd-tmpfiles
would improve this state of things.
(Trimming Cc list a little bit, I don't want to spam everybody)
Thanks.
