|
|
Subscribe / Log in / New account

Some unlikely 2021 predictions

Some unlikely 2021 predictions

Posted Jan 7, 2021 9:37 UTC (Thu) by smurf (subscriber, #17840)
In reply to: Some unlikely 2021 predictions by pebolle
Parent article: Some unlikely 2021 predictions

WRT Debian and systemd: probably. But these are just the dying embers which won't have an impact on the project at large.
The discussion in https://bugs.debian.org/975075 seems to confirm this.


to post comments

Some unlikely 2021 predictions

Posted Jan 7, 2021 20:15 UTC (Thu) by pebolle (guest, #35204) [Link] (3 responses)

> The discussion in https://bugs.debian.org/975075 seems to confirm this.

I can't read threads like that anymore. Way too many messages, most of them way too long. Some of the names involved are all too familiar from watching their systemd train wreck from the sidelines.

Debian is clearly filled with people with a lot of experience and energy. It's their project and they can run it as they like. But some of them really seem to love playing mock United-Nations-sponsored organization: a "Constitution", "General Resolutions", and whatever more they excel at. It's all looks a bit silly...

Some unlikely 2021 predictions

Posted Jan 8, 2021 0:30 UTC (Fri) by NYKevin (subscriber, #129325) [Link] (2 responses)

I read the whole thing. Here's the TL;DR:

1. The NetworkManager maintainer removed its (working) sysvinit script and documented the change in the changelog. Someone filed a bug to add it back.
2. In a separate bug, it was requested to modify NM's dependencies so it could be installed with elogind instead of systemd.
3. The maintainer set the bugs to wishlist priority and otherwise ignored them.
4. Someone uploaded an NMU (and later went on to file the bug linked upthread). The maintainer asked that it be rejected, and stated that the sysvinit script had been removed intentionally.
5. Much ado over what the GR means, how it applies to cases like this, whether the TC is empowered to interpret the GR, etc.
6. My read of that thread is that the sysvinit script is probably going to end up living in a separate package. The offending Depends has already been downgraded to a Recommends (but I'm not sure if they are going to do anything else with that problem).

Frankly, I think the Debian people brought this on themselves by voting for the most ambiguous and wishy-washy option available (except perhaps for proposal G). Several of the other options had clearly-spelled-out policies for what to do with bugs like this (or at least implicated existing policies in standardized ways), but proposal B was pretty vague on what a maintainer is expected to do in this situation (it literally just says to "use their normal procedures").

Some unlikely 2021 predictions

Posted Jan 8, 2021 1:59 UTC (Fri) by pebolle (guest, #35204) [Link] (1 responses)

> I think the Debian people brought this on themselves

So true! Debian's systemd saga borders on the the bizarre. Their refusal to make a choice is what fuelled this soap opera. Honestly, I think it's impossible to explain all this to people outside our Free Software bubble.

Thank you Debian, for making us look fringe!

Some unlikely 2021 predictions

Posted Jan 21, 2021 16:38 UTC (Thu) by mstone_ (subscriber, #66309) [Link]

Yeah, free software's decision making progress is completely incomprehensible, compared to the corporate world where, say, google can decide on a simple messaging app and stay on message with no drama at all.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds