Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?
On 14/12/2020 21:56, Philip Hands wrote:
Could I just check if there's a point of common acceptability which both
sides of this discussion could live with?
My suggestion for a mutually bearable solution would be that the
network-manager package could have its dependency on libpam-systemd
changed to instead be something like:
libpam-systemd | network-manager-nonsystemd
Is this instead of the logind virtual package? I'm not quite sure what
problem you're trying to solve here, but I'm don't think it generalises
well (you'd end up with potentially lots of package that just Depend on
logind and maybe contain an init script); and without any input from the
network-manager maintainer about why they were unwilling to take the
patch to use the existing virtual package, I'm not sure why this should
be more acceptable.
If you think this approach is impractical for some reason, please say
so, because what I have in mind as a better option does rather rely on
this being available as a plausible fall-back position.
I'm confused as to why you don't just tell us what your better option is.