SoylentNews is people
SoylentNews
Longtime Debian contributor Tollef Fog Heen has announced his resignation from the Debian systemd maintainer team. His announcement states that "the load of the continued attacks is just becoming too much."
He has since written a detailed blog article surrounding the circumstances of his resignation. As he puts it,
I've been a DD for almost 14 years, I should be able to weather any storm, shouldn't I? It turns out that no, the mountain does get worn down by the rain. It's not a single hurtful comment here and there. There's a constant drum about this all being some sort of conspiracy and there are sometimes flares where people wish people involved in systemd would be run over by a bus or just accusations of incompetence.
This is yet another dramatic event affecting the Debian project in recent months. The adoption of systemd has been extremely controversial, even going so far as to result in calls for Debian to be forked. There have been other problems as of late, too, ranging from a serious bug breaking Wine just days before the Jessie freeze deadline, to the possibility of Debian GNU/kFreeBSD being dropped from Debian 8. And it was only just over a week ago that Joey Hess — another longtime Debian contributor — left the project, citing the "very unhealthy directions" that Debian has been led in lately.
Is the internal tension and strife caused by systemd about to tear the Debian project apart? Recent events such as the aforementioned have suggested that this is becoming more and more of a possibility. The repercussions of this drama will no doubt be felt wide and far, given Debian's own popularity, as well it forming the basis of other major Linux distros such as Ubuntu and Linux Mint.
(Score: 0) by Anonymous Coward on Monday November 17 2014, @01:13PM
The cause of the bug is irrelevant. Maybe it was just a few characters that needed to change.
The problem is that the bug happened in the first place. That's what makes it so serious.
It was a totally obvious problem. The most basic level of testing, which obviously involves just running the broken "wine" script, would have shown that there was a serious problem.
It's the kind of bug that's totally inexcusable. The fact that it did happen shows that something is seriously wrong with Debian. This bug is indicative of a complete and total quality control failure on Debian's part.
Debian's quality has taken a nosedive since systemd was integrated. It was one reliable and trustworthy; now it's riddled with totally unnecessary and unjustifiable problems.
(Score: 2) by HiThere on Monday November 17 2014, @07:36PM
Idiot. That is should have happened that close to release *is* bad, but it was easily fixed without reversion, and anyone can make a typo.
Perfection does not exist in this world, and to expect it is to beg for disappointment. One should, however, strive to approach it.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 0) by Anonymous Coward on Monday November 17 2014, @11:20PM
I'd expect a sloppy bug like that when I'm using Fedora.
I do not expect a sloppy bug like that when I'm using Debian testing or Debian unstable.
This bug cannot be justified. The evidence suggests that the package maintainer didn't even bother to try running the script before making the update publicly available. Even if he or she did, the fact that the bug got through suggests that the testing process is extraordinarily flawed.
Regardless of what happened, it's not acceptable in any way.