This bug was fixed in the package debhelper - 13.6ubuntu1
---------------
debhelper (13.6ubuntu1) jammy; urgency=medium
* Merge from Debian unstable (LP: #1960248). Remaining changes:
- Generate ddebs from debhelper instead of pkg-create-dbgsym:
- Set DBGSYM_PACKAGE_TYPE to ddeb to get correct debian/files output.
- dh_installchangelogs: Do not install upstream changelog in compat level
7 and higher to avoid pointlessly bloating installed packages.
- dh_strip: Strip LTO sections unless --keep-lto is given.
- dh_strip: For a static archive, test if any .text sections are non-
empty. Warn on empty archives.
- objcopy/strip changed in 2.36.1, not keeping file attributes of the
original file. Work around that in dh_strip to write to a temporary file
and cat'ing this to the original file to keep the original attributes.
- Imply '<!noudeb>' profile if not set on package type udeb.
- dh_strip: Set a unique build-id before stripping files.
- Allow dh_strip to be larger for the tests
* Add awk dependency implied by empty .text section check
* Fix restart behaviour of packages marked either
- no-stop-on-upgrade or --no-restart-after-upgrade (LP: #1959054)
debhelper (13.6) unstable; urgency=medium
[ Niels Thykier ]
* dh_assistant: Avoid creating `debian/.debhelper` when the
which-build-system sub command is invoked. Thanks to
Jelmer Vernooij for spotting that bug.
* dh_assistant: Add new active-compat-level command, which
outputs information about which compat level is declared
and active. It also tells how the compat level was
declared.
* Dh_Lib.pm: Add new function, get_non_binnmu_date_epoch,
only needed for dh_strip_nondeterminism.
* dh_installcron: Add support for `cron.yearly` packaging
file. Thanks to Martin-Éric Racine for the suggestion.
(Closes: #1000363)
* Dh_Lib.pm: Remove support for compat 5 and 6.
* debhelper.pod,debhelper-obsolete-compat.pod: Update to
reflect the new status for compat 5 and 6.
[ Guillem Jover ]
* dh: Add missing _ in execute_after example in POD.
[ Sandro Tosi ]
* dh_compress: Exclude .woff and .woff2 by default.
[ Translations ]
* Update Portuguese translation (Américo Monteiro)
(Closes: #1000719)
-- Dave Jones <dave.jo...@canonical.com> Mon, 07 Feb 2022 15:59:07
+0000
** Changed in: debhelper (Ubuntu Jammy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
Status in debconf package in Ubuntu:
New
Status in debhelper package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Confirmed
Status in libvirt package in Ubuntu:
Triaged
Status in debconf source package in Jammy:
New
Status in debhelper source package in Jammy:
Fix Released
Status in docker.io source package in Jammy:
Confirmed
Status in libvirt source package in Jammy:
Triaged
Status in debhelper package in Debian:
New
Bug description:
Debian bug #994204 (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
results in the postinst being generated in such a fashion that
services marked --no-stop-on-upgrade (or its deprecated alias --no-
restart-on-upgrade), restart anyway.
Please note: this is nothing to do with the --no-restart-after-upgrade
flag (which is, somewhat confusingly IMO, unrelated).
I've confirmed that the flaw appears to be present in the jammy
version of debhelper (though not impish) and that packages generated
with it appear to contain the flawed postinst (I first encountered
this whilst working on the open-iscsi merge), though I haven't yet
managed to test that the flaw exhibits itself on upgrade (though I'd
say from the presence of the flaw in the postinst, that it's a
reasonable inference that it will).
In dbus (the merge of which I'm currently working on), Debian has
worked around this but given I've now run into two affected packages
(open-iscsi and dbus), only one of which has a work-around, I'd much
rather we got debhelper fixed up and rebuilt affected packages?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
