Bug#975289: Acknowledgement (systemd: always reporting unit file has "changed on disk" when override.conf is present)

Control: tags -1 + confirmed Control: forwarded -1 https://github.com/systemd/systemd/issues/17730 Am Mittwoch, den 25.11.2020, 12:56 +0100 schrieb Richard van den Berg: > On 25-11-2020 02:11, Michael Biebl wrote: > > Can you break this down to a more minimal test case which would > > make > >

Bug#975289: Acknowledgement (systemd: always reporting unit file has "changed on disk" when override.conf is present)

On 25-11-2020 02:11, Michael Biebl wrote: Can you break this down to a more minimal test case which would make this easily reproducible with systemd from unstable? This reproduces the issue with 246.6-2~bpo10+1: 1) Create a normal unit file /etc/systemd/system/test-start.service with

Bug#975289: Acknowledgement (systemd: always reporting unit file has "changed on disk" when override.conf is present)

Am Mittwoch, den 25.11.2020, 02:10 +0100 schrieb Michael Biebl: > On Sun, 22 Nov 2020 15:54:12 +0100 Richard van den Berg > wrote: > > This looks a lot like > > https://github.com/systemd/systemd/issues/17312  > > which apparently was fixed by > > https://github.com/systemd/systemd/pull/16885 > >

Bug#975289: Acknowledgement (systemd: always reporting unit file has "changed on disk" when override.conf is present)

On Sun, 22 Nov 2020 15:54:12 +0100 Richard van den Berg wrote: > This looks a lot like https://github.com/systemd/systemd/issues/17312  > which apparently was fixed by https://github.com/systemd/systemd/pull/16885 > > Can this PR be applied to the debian systemd package in unstable? Or do > I

Bug#975289: Acknowledgement (systemd: always reporting unit file has "changed on disk" when override.conf is present)

This looks a lot like https://github.com/systemd/systemd/issues/17312 which apparently was fixed by https://github.com/systemd/systemd/pull/16885 Can this PR be applied to the debian systemd package in unstable? Or do I need to wait until 247 is officially released?