Le 11/04/23 à 19:53, Sam Hartman a écrit :
control: tags -1 wontfix
"bigon" == bigon <bi...@debian.org> writes:
bigon> It seems that your package libpam-modules-bin is shipping
bigon> files (.service, .socket or .timer) in
bigon> /usr/lib/systemd/system.
I think we're talking about pam_namespace.service.
I don't think dh_installsystemd has anything to do for that file because
it has no Install section.
What harm is caused by pam_namespace.service being in /usr/lib/systemd?
dh_installsystemd also takes care of calling systemctl daemon-reload
when a new .service file is installed/removed, it also takes care that
the service is stopped before removing the package (in this case it's a
short living/oneshot service, but still)
bigon> debhelper? As soon as debhelper is supporting (not until
bigon> bookworm+1 aka Trixie) you will be able to move them back to
bigon> the newer location.
Um, no doing that before dpkg is fixed to deal with aliasing could
potentially be a really bad idea.
I'm not sure I understand, if all the files are at package level moved
to /usr instead of / then aliasing in dpkg is not needed, isn't it?
Again, what harm is caused by pam_namespace.service being in
/usr/lib/systemd/system?
How is this a bug?
