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 Sunday October 26 2014, @09:30AM
If you want to use Debian unstable or testing, then consider using apt-listbugs [debian.org] which notifies you of known critical bugs in packages you are attempting to install/update. Maintaining a system that's running a non-stable distro requires some sysadmining effort. If you don't want to expend that effort, run a stable distro. (Personally, I've switched to running Ubuntu on all but my primary desktop which runs Debian unstable.)