Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Saturday October 25 2014, @02:41PM   Printer-friendly
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.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Sunday October 26 2014, @06:18PM

    by Anonymous Coward on Sunday October 26 2014, @06:18PM (#110287)

    Your attitude is what I'd expect from a Microsoft Windows user.

    You're saying, "Yeah, it's a bug. So what. It's totally fine."

    That's not how the Linux community sees things. We have these things called standards. When it comes to software, one of these standards involves doing basic testing. It appears that wasn't done in this case, because if it had been, then this bug would have been discovered immediately, well before the updated package ever went live.

    Your shitty standards have no place in the world of software development. They have no place within the Debian project.

    The Debian project's standards are slipping, and this should definitely be news. This is the most important news I've seen here at SN in days.