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: 5, Funny) by Anonymous Coward on Saturday October 25 2014, @02:48PM
(Score: 1, Interesting) by Anonymous Coward on Saturday October 25 2014, @02:53PM
Sorry, this may sound stupid, but I need to ask it: are you serious about this, or is this just a joke?
With systemd, I can never tell what's a feature that it seriously supports, and what's just hyperbole from opponents of systemd.
When a co-worker first told me that systemd uses binary log files, I laughed, because I thought he was just yanking my chain. Well, it turns out he wasn't joking!
(Score: 1) by forkazoo on Sunday October 26 2014, @01:50AM
For the record, it is a joke. Systemd is sometimes suggested to have a feature set similar to Windows services, but that's as far as it goes. OTOH, Graphics from init actually is a real thing... Because reasons. The plan is to move Linux vtty consoles to use the new systemd framebuffer stuff. Which is why as somebody who is mostly annoyed with systemd, I found the joke very funny.
(Score: 2) by Bot on Saturday October 25 2014, @03:23PM
WTF, systemd *emulates* windows executables? I thought Lennart was going to rewrite them, one by one, putting them all in systemd.
"So, get yourself a copy of The win64 API, ignore everything it says about DirectX compatibility and hack away your amazing Windows software. It's quite relieving!"
Maybe he's getting old.
Account abandoned.