SoylentNews is people
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.
TOO BAD YOU CAN'T BUY a voodoo globe so that you could make the earth spin
real fast and freak everybody out.
-- Jack Handey, The New Mexican, 1988.
(Score: 2) by Bot on Saturday October 25 2014, @03:26PM
If a testing bug before freeze decrees the death of debian, I guess all other operating systems are already zombies.
Account abandoned.
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @03:36PM
I know you're being facetious, but what you're saying is true anyway. We use Debian because it has always been the least-fucked-up of all of the major distros. Fedora, for example, has always been a dead distro, because its quality is generally so low. Now we're seeing Debian stoop to the level of these other, shittier distros. Bugs this obvious and severe never used to happen with Debian. But things have clearly changed with the project and its leadership. Sensibility and quality have been thrown out the window, and now we users are paying the price!
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:16PM
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:23PM
This kind of bug wouldn't have happened in the pre-systemd days of Debian. I know, because I've used Debian since almost the beginning of its existence, and I've used Wine since it started to become usable.
Debian's standards have sunk mighty low these days. A lot of crap that just never would have been allowed before is being tolerated now. And we're seeing the result in crap like systemd being included by default, GNOME 3 being the default desktop, and now totally unnecessary bugs like this breaking lots of software.
(Score: 2) by HiThere on Saturday October 25 2014, @06:49PM
While you're right that that's a hyperbolic overstatement, it is a significant problem that should not have been allowed to occur at this stage of the release process. I've reverted from testing to stable, and it's not clear that I'll stay with debian. If I weren't temporarily locked into ext4 partitions, I'd strongly consider switching to one of the BSDs. As it is I'll hope that if I stick with Wheezy for awhile things will straighten out. Or maybe I'll switch to Slackware. I really don't want to go to Gentoo. (The last time that I seriously looked at it I spent so much time resolving problems that I eventually gave it up. It's been awhile, but some people are saying that it hasn't gotten any better.)
The other possibility is CentOS. It's not a choice I like, as the security system isn't to my taste (or needs) and it's incompatible with non-RedHat installs in other partitions. (Well, it was a few years ago, when I was still flipping between distros to figure out which is best.) OTOH, if I'm going to be stuck with systemd, I might as well use a distro that supports it decently. Possibly I could have one partition for CentOS and one for Fedora and still get them to work together. But that might take more investment of time and effort than would switching to a BSD.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 0) by Anonymous Coward on Saturday October 25 2014, @07:43PM
You should consider FreeBSD. It's as close as you're going to get to what Debian used to offer, before Debian collectively went stupid and started doing stuff like systemd and bugs like this.
(Score: 3, Informative) by VLM on Sunday October 26 2014, @11:19AM
" If I weren't temporarily locked into ext4 partitions, I'd strongly consider switching to one of the BSDs."
"supports" as in you can install your *BSD root partition to ext4, naw. "supports" as in you can read the partition and copy the contents to a new ZFS partition or whatever, sure, thats generally fine. Kind of like linux "supports" msdos partition, as in you can access it, but not necessarily install your system on it. There was a system to do that in the early 90s but it was really weird.
Historically people have run into weird bugs where ext4 FS get accidentally mounted as ext2. Really, ext3 is just 2 with a journal, so if you don't mount RW its difficult to tell them apart, and I guess 4 doesn't add much either.
(Score: 2) by HiThere on Sunday October 26 2014, @07:26PM
I don't need it as a root partition, but I do need to be able to both read and write to it. AFTER I've successfully migrated, THEN I'll consider going totally to a non-Linux partition. Too many times what some people praise isn't what I need, so the conversion needs to be in stages.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.