Re: Bug#1031695: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
>>>>> "Michael" == Michael Biebl <biebl@debian.org> writes:
Michael> Excluding packages that only ship overrides/drop-ins, this
Michael> makes 37 affected packages in bookworm.
If I'm understanding this issue correctly, the concern would be a
package that moved from /lib/systemd/system to /usr/lib/systemd/system.
Under the TC resolution, that should not be happening for bookworm.
At least some of those packages are new services that have never been in
/lib/systemd/system. I believe for example pam is in that set.
That's presumably not going to break something in the way that a file
moving between /lib and /usr/lib is.
But we don't want to encourage that movement.
It seems like knowing how many incorrect moves we've had would also be
valuable--how many things that used to be in /lib/systemd but are now
appearing in /usr/lib.
Reply to: