Re: Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread lorenzo
On Wed, 16 Dec 2020 11:48:52 +0100 Philip Hands wrote: > Are Simon's suggested dependencies are better in this regard? As far as I know > default-logind | logind works fine, but something like > systemd-sysv | network-manager-nonsystemd, won't for the same reason mentioned in my previous

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Philip Hands
Matthew Vernon writes: > 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

Additional TC meeting before next one

2020-12-16 Thread Margarita Manterola
Hey all, TL;DR: next meeting poll at: https://xoyondo.com/op/XH9BddY6TL6BBin Today we had an interesting discussion during our TC meeting [1], but we didn't manage to come to a conclusion regarding #975075 - Should maintainers be able to block init compatibility changes? Given that taking a

Next Meeting - December 16th at 18:00 UTC (in 1.5 hours)

2020-12-16 Thread Margarita Manterola
Dear Technical Committee members, Our monthly meeting is scheduled to take place today, December 16th at 18:00 UTC. We currently have a few ongoing bugs, we should try to make progress on them. Topics for our agenda are: * Review of previous meeting AIs * #971515 - kubernetes: excessive

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Ansgar
On Wed, 2020-12-16 at 14:46 +, Matthew Vernon wrote: Not is it straightforwardly clear that "alternative init systems" should in fact be interpreted to mean "alternative init systems (but not sysvinit)". The GR text mostly seems to talk about *exploring* alternatives; continuing to maintain

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Sam Hartman
> "Matthew" == Matthew Vernon writes: Matthew> On 15/12/2020 22:07, Sam Hartman wrote: >>> However, Debian remains an environment where developers and >>> users can explore and develop alternate init systems and >>> alternatives to systemd features. Those interested in

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Matthew Vernon
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

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Matthew Vernon
On 15/12/2020 22:07, Sam Hartman wrote: However, Debian remains an environment where developers and users can explore and develop alternate init systems and alternatives to systemd features. Those interested in exploring such alternatives need to provide the necessary development and packaging

Re: Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread Philip Hands
lorenzo writes: > Hi all, > >> 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 > > Please consider that apt has

Re: Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-16 Thread lorenzo
Hi all, > 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 Please consider that apt has issues with or group