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: 0) by Anonymous Coward on Saturday October 25 2014, @05:30PM
The patch has been there for several days now. So why hasn't it been fixed? It leaves me feeling uncomfortable when a bug like this in a major piece of software (wine is used to run a lot of other apps!) isn't fixed right away. This isn't just wine not working in some small number of obscure cases. It doesn't even start up! That's a big deal!