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, @03:36PM
I know you're being facetious, but what you're saying is true anyway. We use Debian because it has always been the least-fucked-up of all of the major distros. Fedora, for example, has always been a dead distro, because its quality is generally so low. Now we're seeing Debian stoop to the level of these other, shittier distros. Bugs this obvious and severe never used to happen with Debian. But things have clearly changed with the project and its leadership. Sensibility and quality have been thrown out the window, and now we users are paying the price!
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:16PM
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:23PM
This kind of bug wouldn't have happened in the pre-systemd days of Debian. I know, because I've used Debian since almost the beginning of its existence, and I've used Wine since it started to become usable.
Debian's standards have sunk mighty low these days. A lot of crap that just never would have been allowed before is being tolerated now. And we're seeing the result in crap like systemd being included by default, GNOME 3 being the default desktop, and now totally unnecessary bugs like this breaking lots of software.