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?
(Score: 2) by HiThere on Saturday October 25 2014, @06:55PM
Is there a stable tree?
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 2) by arashi no garou on Sunday October 26 2014, @08:42PM
Yes, and you can configure slapt-get to work with stable package releases just as easily. Here are the changelogs for stable 32-bit and 64-bit respectively:
ftp://ftp.osuosl.org/pub/slackware/slackware-14.1/ChangeLog.txt [osuosl.org]
ftp://ftp.osuosl.org/pub/slackware/slackware64-14.1/ChangeLog.txt [osuosl.org]
(Score: 2) by HiThere on Monday October 27 2014, @05:45PM
Nice. This is going back on my list.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.