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 Bot on Saturday October 25 2014, @04:21PM
Given that the executable works and it is a case of borked launcher script because some paths have changed, it is very likely that the packager built the new version and ran it directly. IIRC Debian has helper scripts that prepare chroots for packaging purposes.
I think we are throwing out the baby and his older brother and the dog with the bathwater.
Account abandoned.
(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