Your message dated Sat, 21 Mar 2026 15:52:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#757446: libssl1.0.0: services are not restarted when
upgrading
has caused the Debian Bug report #757446,
regarding libssl1.0.0: services are not restarted when upgrading
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
757446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757446
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libssl1.0.0
Version: 1.0.1e-2+deb7u12
Severity: normal
When upgrading from 1.0.1e-2+deb7u11 to 1.0.1e-2+deb7u12 (current wheezy
to wheezy-security) the postinst script did not restart any services.
AFAICS this is due to the version checks present in the postinst scripts
around the code blocks that search for services to be restarted. I don't
quite understand what these checks are useful for. But as the $check
variable is empty because of this, no services will be restarted even if
the restart-services debconf entry contains some services to be
restarted.
Wouldn't it be better to remove the version checks altogether (or to
restrict them to updates that only contain packageing changes) and to
scan for relevant services on every upgrade?
Gaudenz
--- End Message ---
--- Begin Message ---
On 2014-08-08 11:37:19 [+0200], Gaudenz Steinlin wrote:
> When upgrading from 1.0.1e-2+deb7u11 to 1.0.1e-2+deb7u12 (current wheezy
> to wheezy-security) the postinst script did not restart any services.
The postinst script has been removed in the meantime. Please use
`needrestart' or something similar.
> Gaudenz
Sebastian
--- End Message ---
