[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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


On Mon, Nov 30, 2020 at 04:24:28PM -0800, Josh Triplett wrote:
> If (hypothetically) network-manager upstream
> decided to remove those legacy fallbacks, the maintainer would then be
> in a position of either:

But that is not what this particular discussion is about. Personally, I have no
interest in rehearsing the GR discussions again. Maybe there are cases where
removal of a broken initscript could be justified. However, this is about the
removal of a functioning initscript. It is the removal itself that causes the
breakage to some people's systems.

If the NM maintainer could point to an upstream change that necessitated the
removal of the initscript then I would not have opened #964139 in the first
place. However, such evidence has not been forthcoming.

If the NM maintainer could point to a breakage caused by adding support for
libpam-elogind as mandated by the winning GR resolution, I am pretty sure that
we would not be seeking resolution via the tech-ctte now. Again, I am unaware of
any such breakage.

Best wishes.


Reply to: