Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 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, @04:53PM

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

    Have you looked at the patch? This is a pretty inexcusable bug, even for an unstable or testing version. This isn't an obscure problem that only happens on certain systems. This is a shell script with completely fucked up paths to binaries!

  • (Score: 2) by Konomi on Saturday October 25 2014, @05:05PM

    by Konomi (189) on Saturday October 25 2014, @05:05PM (#109989)

    Yes, I read the patch before I replied to you and my previous reply still stands.

    • (Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:25PM

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

      No, it doesn't stand. This is the kind of bug that even minimal testing by the package maintainer should have detected right away. If this did slip through, then Debian needs to do a massive and thorough review of their entire testing procedure.

      • (Score: 0) by Anonymous Coward on Saturday October 25 2014, @06:57PM

        by Anonymous Coward on Saturday October 25 2014, @06:57PM (#110040)

        join the wine team and help fix it, you entitled kid...

        in free software you receive a gift from developers and you are allowed to participate on the creative process

        you are not a costumer and they are not trying to sell you anything... grab this into your forehead

        • (Score: 0) by Anonymous Coward on Saturday October 25 2014, @07:41PM

          by Anonymous Coward on Saturday October 25 2014, @07:41PM (#110057)

          Joining the Wine team won't help. This isn't a problem with Wine. This is a problem with Debian. Debian needs to fix their shit.

          • (Score: 1, Informative) by Anonymous Coward on Saturday October 25 2014, @08:12PM

            by Anonymous Coward on Saturday October 25 2014, @08:12PM (#110064)

            Join the debian WINE team. Derp.

            • (Score: 0) by Anonymous Coward on Saturday October 25 2014, @08:52PM

              by Anonymous Coward on Saturday October 25 2014, @08:52PM (#110071)

              Why would I waste my time and effort volunteering for a failed organization like Debian? The whole systemd debacle should never have happened. And this bug never should have happened. I have better things to do with my time than work with inept groups of people.