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 DECbot on Sunday October 26 2014, @07:54PM
With systemd, they're all integrated tightly into the bathwater, so how could you tell what you're throwing out? I guess the binary logs might help. Of course those depend on the bathwater too.
cats~$ sudo chown -R us /home/base