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 meisterister on Sunday October 26 2014, @02:33AM
+1 to FreeBSD, just because I've also been considering it as an alternative (I've installed it on one of my systems and enjoy all of it except for LLVM). For the modern Linux user, the most striking thing is how customizable it is. It won't do anything until you tell it to, then do it well.
(May or may not have been) Posted from my K6-2, Athlon XP, or Pentium I/II/III.