SoylentNews is people
SoylentNews
posted by
LaminatorX
on Saturday October 25 2014, @02:41PM
from the whining-is-not-efficacious dept.
from the whining-is-not-efficacious dept.
A grave bug has been introduced into the "wine" package of Debian Jessie, just days before the November 5th freeze deadline. The /usr/bin/wine launch script fails with an "error: unable to find wine executable. this shouldn't happen." message.
Debian has already suffered much unrest lately over the inclusion of systemd, with threats of a fork being issued, along with the possible cancellation of the GNU/kFreeBSD port and the possible dropping of support for the SPARC architecture. After so much strife and disruption, can Debian afford to have such a serious bug affect such a critical package so soon before such a major freeze?
This discussion has been archived.
No new comments can be posted.
Wine Fails to Launch under Debian Jessie, Just Days before the Freeze Deadline
|
Log In/Create an Account
| Top
| 119 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
You humans are all alike.
(Score: 2) by neagix on Sunday October 26 2014, @02:48PM
Actually why did this even get through the moderation queue? Where is the news?
Shall we publish news about each and every bug of Debian before the release? And why not doing giving the same service to other distros? Hopefully they will get some manpower to do more testing and development.
(Score: 0) by Anonymous Coward on Sunday October 26 2014, @06:10PM
Are you intentionally trying to be stupid?
This is obviously more than just about a single bug.
This is about the sort of bug: an unjustifiable one. Even the most basic testing would have caught this problem right away. You know, like installing wine and trying to run a program with it. You know, the kind of testing that should have been done before this update was ever made public.
The real news here is about how the Debian project is falling apart before our very eyes. Read the other stories that are linked to later on in the submission. This isn't an isolated incident. There's been the systemd disaster. There's been the talk of killing GNU/kFreeBSD. All of this is turning the Debian project and its community upside down. There's been talk of forking Debian, even!
Debian's standards are slipping, and they're slipping badly. This is massive news, with far-reaching consequences for thousands upon thousands of people. Millions of people could be affected, if you want to consider everybody who uses a Debian system directly or indirectly.
This news is perhaps the most important I've seen in days. This is news that will have a real impact.
(Score: 2) by neagix on Sunday October 26 2014, @08:20PM
No, I am really this stupid.
Aside from your sarcasm, I perfectly agree that the most basic test toolsuite should have caught such a bug, but I do not agree on why it is of such big impact, nor why this would be a further proof of Debian bad shape.
What is the expectation of quality of testing/jessie?
Personally I would be AOK with the criticism if it were *already* marked stable and this happened, but it's not what has happened.
I think this story should be discussed with a very critic tone on the Debian development mailing list, and topic could be about enforcing stricter testing rules and/or fix some tools, but not as in here, like: "Look kidz! Debian is rotting!"
Maybe Debian is in bad shape, I am not here to discuss that, and probably I agree with some of the other reasons why one could and should (constructively) complain. But specifically this one, e.g. a bug close to freeze time, is not valid IMO: Jessie is still in development, it has not been released.
I was in particular being critic of the mass of comments that were talking like if this had happened on an officially released and distributed stable version, like Wheezy. It ain't happened. No news here, move along.