Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

[Michael Biebl]

Control: reassign -1 e2fsprogs

Am 14.05.23 um 11:30 schrieb Andreas Beckmann:
> On 09/05/2023 17.48, Michael Biebl wrote:
>> Andreas, you filed this with RC severity with the justification that 
>> systemd units are not enabled. I don't see that, so could you please 
>> clarify.
>>
>> What I could find out so far is the change of WantedBy target not 
>> being properly cleaned up on upgrades, but that doesn't strike me as 
>> RC (and would need to be done in e2fsprogs)
> 
> Yes, looks like this is in the e2fsprogs realm.
> 
> Please reassign it there together with instructions how to fix it, i.e. 
> what should be done in the maintainer scripts.
> 
> IMO the expected outcome from e2fsprogs perspective should be identical 
> system configuration (w.r.t. enabled systemd units) after both fresh 
> install and upgrade from bullseye, regardless of the installation status 
> of systemd.
> If e2fsprogs doesn't care about this, it can downgrade the severity.
> 
> 
> Andreas
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230514/cab63d77/attachment.sig>