Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.

Wine Fails to Launch under Debian Jessie, Just Days before the Freeze Deadline

posted by LaminatorX on Saturday October 25 2014, @02:41PM   Printer-friendly
from the whining-is-not-efficacious dept.

An Anonymous Coward writes:

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
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 Saturday October 25 2014, @05:04PM

    by Anonymous Coward on Saturday October 25 2014, @05:04PM (#109988)

    I don't think this submission is a "troll". Wine isn't just one application. It's a system that allows many thousands upon thousands of other apps to run. If you break Wine, you've broken a lot of other software. It would be like the Java VM not running any software, or the Python interpreter no longer starting up. It's a very, very serious bug.

    This bug comment [debian.org] is very ominous suonding, too:

    btw:
    Jessie/Testing still has 1.6.2-8.
    So if we want all changes since then to enter Jessie (including the
    non-release-critical changes) /someone/ should upload a fixed version
    until *October 26th which is in 3 days* (or even earlier since it has to
    be accepted, ...).
    See " rel="url2html-19988">https://release.debian.org/jessie/freeze_policy.html.

    That makes it sound like a fix needs to be integrated very soon otherwise this problem could be present for a long time. Maybe it's just worded poorly, but that's how I interpret it.

    As it stands, it's now October 25 and there's still no update to that bug's tread of discussion indicating that it has been fixed.