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, @01:08AM

    by Anonymous Coward on Sunday October 26 2014, @01:08AM (#110123)

    What else is he supposed to do, use Chrome during the 8 hours it takes to compile it? Or should he use KDE during the week it takes to compile it instead, maybe? Oh, wait, none of that is possible. You can't use the software until it's done compiling!

  • (Score: 1) by Pino P on Monday November 24 2014, @12:48AM

    by Pino P (4721) on Monday November 24 2014, @12:48AM (#119267) Journal

    Then download the binary for the generic architecture and use that in a chroot while compiling a fully optimized build.