Stories
Slash Boxes
Comments

SoylentNews is people

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: 2) by arashi no garou on Saturday October 25 2014, @04:39PM

    by arashi no garou (2796) on Saturday October 25 2014, @04:39PM (#109980)

    Install slackware-current, install slapt-get and configure it for slackware-current, and you have a rolling-release OS with up to date, bleeding edge packages. It's like Arch without the sado-masochistic, user hating project leaders (and no systemd! ).

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

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

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

    I like the no systemd part, but how much effort does the rest of it actually take? Like "configure it for slackware-current", is that as simple as editing /etc/apt/sources.list is under Debian?

    How frequently are the packages updated? Let's say a new version of bash or Firefox is released today. How long will it be until I can install it using the Slackware package management tools?

    • (Score: 2) by arashi no garou on Saturday October 25 2014, @05:12PM

      by arashi no garou (2796) on Saturday October 25 2014, @05:12PM (#109997)

      Like "configure it for slackware-current", is that as simple as editing /etc/apt/sources.list is under Debian?

      Pretty much, yeah. See http://software.jaos.org/git/slapt-get/plain/README [jaos.org] for details.

      How frequently are the packages updated? Let's say a new version of bash or Firefox is released today. How long will it be until I can install it using the Slackware package management tools?

      Even though it's fairly bleeding edge, Pat and the Slackware team still test each package before releasing it to the -current tree. So, there is some delay from source release to an official Slackware package release, even on -current. For example, take gimp-2.8.14. It was released in source format by the GIMP authors on August 26th, and the slackware-current package was released on October 25th (today), two months later. Of course, you're always free to build your own package using a Slackbuild and the most recent source, but any testing is your own responsibility in that scenario.

      In my mind, that kind of thing is what makes Slackware the most versatile OS out there. Stick with the stable branch for optimum stability at the cost of current features, use the -current branch for fairly up to date packages that have been vetted by the Slackware team, or roll your own packages as the source is released for the absolute bleeding edge, warts and all.