** Changed in: debhelper (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To
See bug 1965758 this also breaks focal-backports - please upload the fix
there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked
** Changed in: debhelper (Ubuntu Jammy)
Assignee: Dave Jones (waveform) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked
** Changed in: libvirt (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: libvirt (Ubuntu Jammy)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To manage notifications about this bug go
This bug was fixed in the package debconf - 1.5.79ubuntu1
---
debconf (1.5.79ubuntu1) jammy; urgency=medium
* dpkg-reconfigure: fix restart of services declared with
--no-restart-after-upgrade (LP: #1959054)
-- Dave Jones Sun, 20 Feb 2022 14:42:49
+
** Changed in:
Excellent, happy with that. I'm attaching a debdiff for the debconf
change, and will see if I can rustle up a sponsor on Monday to finally
put all this to bed!
** Patch added: "1-1959054.debdiff"
It worked
ii debconf1.5.79ubuntu1 all Debian configuration
management system
root@j-slapd-reconfigure:~# pidof slapd
105004
root@j-slapd-reconfigure:~# dpkg-reconfigure -fnoninteractive -pcritical slapd
Backing up /etc/ldap/slapd.d in
Gladly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To manage notifications about this bug go to:
** Changed in: debconf (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To manage
@ahasenack Could you try the debconf version from [1]? I've patched that
with the same fix that I've proposed upstream [2]. I'll add the relevant
debian bug here too. I realize this is *technically* a separate issue,
but it's all so interconnected and related that I'd prefer to keep it
all in one
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
Many thanks to Andreas for the report, and the logs. I suppose it was
too much to hope that this went through entirely smoothly, and so it has
come to pass! After digging into the logs above, and then dpkg-
reconfigure's code it appears that it does the following (see [1] for
details):
* Run the
Here is a little reproducer I'm using.
apt update
DEBIAN_FRONTEND=noninteractive apt-get -y --allow-unauthenticated -o
Dpkg::Options::='--force-confold' install slapd ldap-utils
debconf-set-selections -v << EOF
slapd slapd/domain string example.com
slapd shared/organization string example
slapd
** Attachment added: "slapd-reconfigure-proposed.log"
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+attachment/5561895/+files/slapd-reconfigure-proposed.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hit a problem in a dep8 test that relies on slapd (from openldap) to
be restarted after a "dpkg-reconfigure slapd". This restart stopped
happening in 2.5.11+dfsg-1~exp1ubuntu3, which was built with
13.6ubuntu1.
See how the authentication only works after I restart slapd manually:
The fix has now been merged upstream in debhelper, so we're just waiting
on sponsorship of LP: #1960248 to get the fix into our version as well.
In the meantime, I've gone through the list sarnold provided; here's the
list of source packages which will need a no-change rebuild once the
debhelper
> @Dave - you can do things like:
> https://codesearch.debian.net/search?q=dh_installsystemd.*--no-start=0
Ah, very useful. sarnold has kindly run a similar search on all
components of the Ubuntu archive for jammy. I'm currently going through
this, and comparing it to a similar run on
FYI - For libvirt I'm uploading now with the mitigation for the
debhelper issue to unblock others waiting on libvirt.
But the plan is to drop this mitigation before jammy release once
debhelper is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/414648
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts
@Dave - you can do things like:
https://codesearch.debian.net/search?q=dh_installsystemd.*--no-start=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services
One extra note: once this fix is landed we also need to figure out which
packages need a no-change re-build. Is it possible to "grep" the archive
for any package which mentions --no-restart-after-upgrade, --no-restart-
on-upgrade, or --no-stop-on-upgrade in its d/rules ?
--
You received this bug
I've now opened a merge request with debhelper upstream incorporating my
proposed fix [1] and I've added the fix to our proposed merge of
debhelper in LP: #1960248. Test packages are built in [2] -- anybody
affected by this is encouraged to test by build their packages with this
PPA as an "extra"
I've now got a branch on salsa [1] with a proposal for a fix which I've
tested against a few affected packages in a few different environments.
The debhelper test suite still passes, and overall I'm *reasonably*
happy with it, but I still need to write up a proper explanation of why
I've changed
** Changed in: debhelper (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debhelper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
docker.io is also affected:
https://git.launchpad.net/ubuntu/+source/docker.io/tree/debian/rules?h=ubuntu/jammy=18b9d33de2adcb7ec361e4789f1f96223e80d607#n109
** Also affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
I'm working on patching debhelper (brushing up on some *very* rusty perl
knowledge!) as some of the comments upstream indicate that as many as
40+ packages may be affected and I don't see it as viable to work around
every one of them. However, first I want to understand exactly what the
patch that
I'd like to know if there already is an Ubuntu position on this, will we revert
[1] to avoid a yet unknown amount of breakage in Jammy?
I'd like to know to adapt my packages accordingly ...
[1]: https://salsa.debian.org/debian/debhelper/-/commit/6067bc2
--
You received this bug notification
FYI: Keeping things up is even harder, while restarting sockets in the past
complained about services already being up they now restart the service.
So if anyone is looking at this for some package, be careful that you'd also
need to handle .socket files special now as they are affected by this
Hi,
recent tests with libvirt 8.0 (in PPA, but even rebuilding our current libvirt
in Jammy has the same result) shows that we are affected as expected. On
reinstall or upgrade guests are shut down due to this.
Trying to work around that until resolved in debhelper:
=>
** Tags added: fr-2008
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To manage
** Also affects: debhelper (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked
** Changed in: debhelper (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts services marked --no-restart-on-upgrade
To manage
** Description changed:
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-restart-on-upgrade (now deprecated in favour of --no-stop-on-
-
36 matches
Mail list logo
