[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
Dave Jones
1965758 at bugs.launchpad.net
Mon Mar 21 16:59:13 UTC 2022
Having looked at the versions of debhelper in play, and the versions
that introduced / fixed various bugs, my current reading of the
situation is as follows:
All current bionic and focal versions in release, updates, and backports
(11.1.6, 12.10, and 13.5.2) will be producing packages where the old
version's prerm is responsible for stopping services when --no-restart-
after-upgrade is selected. In other words, these are affected by debian
bug 989155 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989155)
which was the ultimate issue that (indirectly) caused the fix in
13.6ubuntu1. *If* want to fix this in bionic and focal, a full SRU will
be required (plus additional rebuilds, see below).
Additionally, the bionic and focal -backport versions (both 13.5.2) will
be restarting services with --no-stop-on-upgrade, i.e. affected by
debian bug 994204 (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=994204) as presumably they include the original
(problematic) fix for 989155 that was included in 13.4. This should
definitely be fixed, so at a minimum a backport of 13.6ubuntu1 is
warranted.
In the former case (SRU), we will additionally want to perform a no-
change rebuild on all affected packages (all packages using --no-
restart-after-upgrade and/or --no-{restart,stop}-on-upgrade). For
reference, this was ~90 packages in jammy (I would assume similar
numbers in bionic/focal).
In the latter case (backport only) we will want to perform a no-change
rebuild on all packages that were built with the backport version
although it sounds (given teward's comment #5 above) that this may be a
minimal number.
Personally, I suspect this comes down to how many packages would be
seriously affected by 989155. I know openldap was but are we planning on
any SRUs for that in bionic/focal? If we are, we may wish to consider
the full SRU option (however painful that might be). If not, the
backport option is almost certainly preferable.
** Bug watch added: Debian Bug tracker #989155
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989155
** Bug watch added: Debian Bug tracker #994204
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994204
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debhelper in Ubuntu.
https://bugs.launchpad.net/bugs/1965758
Title:
[BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
Status in debhelper package in Ubuntu:
Fix Released
Status in debhelper source package in Bionic:
New
Status in debhelper source package in Focal:
New
Status in debhelper source package in Impish:
New
Bug description:
Please backport debhelper (>= 13.6ubuntu1) to Bionic and Focal.
Currently we have
debhelper | 13.5.2ubuntu1~bpo18.04.1 | bionic-backports | source, all
debhelper | 13.5.2ubuntu1~bpo20.04.1 | focal-backports | source, all
Those versions are affected by LP: #1959054, which is fixed in
13.6ubuntu1. Especially bad about that bug is that it requires
rebuilding packages which were built against the buggy debhelper to
update their maintainer scripts.
I'm not preparing the upload myself as [1] specifies debhelper is
handled by the Backports team.
[1] https://wiki.ubuntu.com/UbuntuBackports#Special_Cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions
More information about the foundations-bugs
mailing list