SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.
SoylentNews
posted by
LaminatorX
on Saturday October 25 2014, @02:41PM
from the whining-is-not-efficacious dept.
from the whining-is-not-efficacious dept.
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?
This discussion has been archived.
No new comments can be posted.
Wine Fails to Launch under Debian Jessie, Just Days before the Freeze Deadline
|
Log In/Create an Account
| Top
| 119 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
When angry, count four; when very angry, swear.
-- Mark Twain, "Pudd'nhead Wilson's Calendar"
(Score: 3, Interesting) by darkfeline on Saturday October 25 2014, @05:07PM
It sounds like the main wine executable wasn't installed in the right place with the right name. If so, it's not even a bug, just a packaging slip. Careless, sure, but completely harmless and trivial to fix. Grave bug my buttocks.
To the person complaining about lack of testing, packaging bugs are the most likely to slip through testing. After all, the program itself works fine!
For the Linux layman, this is like mistyping 'cp wine /usr/bin/wien' instead of 'cp wine /usr/bin/wine' and screaming that the sky is falling.
Join the SDF Public Access UNIX System today!