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 SGT CAPSLOCK on Saturday October 25 2014, @07:07PM
How is it even possible to incorrectly pack a package like that?! This one is boggling, man. I've been scouring the mailing lists, reading all the forums, staring at the bug trackers and even perusing the "discussions" on the wikis, but I still can't find an answer that satisfies me. None of this makes any sense.
...Unless the Government is involved...
BTW, does anyone know where I can get some relevant oldschool animated GIF images for my Debian conspiracy blog? Non-GPL plz. I don't trust anything Big Brother uses. And BB uses the GPL, man. GPL GIF images.
Forgot what I was writing about at this point. Think I'll make some nachos!
(Score: 2) by Appalbarry on Saturday October 25 2014, @11:31PM
Mod parent fucking UP! Just about peed myself.
(Score: 0) by Anonymous Coward on Sunday October 26 2014, @01:17AM
Go home lennart