Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Saturday October 25 2014, @02:41PM   Printer-friendly
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.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by CRCulver on Saturday October 25 2014, @04:24PM

    by CRCulver (4390) on Saturday October 25 2014, @04:24PM (#109973) Homepage

    It's a wonderful system and virtually anything you used on another OS that is not included in the base install is available as a slackbuild.

    So I have to stare at compiler output for hours before I can run lots of popular Linux software on my computer, as opposed to just installing a conveniently packaged deb/rpm like on any other system? No thanks. I do like Slackware for certain niches, but the Slackbuild system makes it a pain for conventional desktop installations.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Saturday October 25 2014, @05:13PM

    by Anonymous Coward on Saturday October 25 2014, @05:13PM (#109999)

    Building from source isn't a problem for C code, since C code compiles really fast. But it's fucking unbearable for anything written in C++. Like if you want Firefox and KDE installed on Gentoo, be prepared to wait a week, even on expensive, fast modern workstations.

  • (Score: 2) by arashi no garou on Saturday October 25 2014, @06:09PM

    by arashi no garou (2796) on Saturday October 25 2014, @06:09PM (#110021)

    If you don't want to wait for the source to compile to use a slackbuild, you can always use the pre-built packages available from some of the core Slackware team, like AlienBOB's packages at http://www.slackware.com/~alien/slackbuilds/ [slackware.com] or Robby Workman's at http://rlworkman.net/pkgs/ [rlworkman.net] . If you don't trust those sources (and for the record, I do but I've been using Slackware more or less since 1999, so I feel safe with them), you can always build your packages from source when you sleep. Recently I built Chromium from the slackbuild and the latest source to test a bug in the notification area (specifically, to see if it really had been fixed in the latest source release); I started it around 6pm, watched some TV and ate dinner, went to bed, and the next day it was ready.

    Generally, when using slackbuilds via sbopkg, I've noticed that most simple packages compile in a matter of seconds or minutes, with some GUI apps taking about half an hour to an hour, and very few complicated packages (the aforementioned Chromium, Firefox, GIMP, etc.) taking several hours. This is on an old Core 2 Duo machine, which is my Slackware workhorse and not my main workstation, so I can afford to have it churning away at slackbuilds while I get things done on my main rig.

  • (Score: 2) by Arik on Saturday October 25 2014, @11:29PM

    by Arik (4543) on Saturday October 25 2014, @11:29PM (#110104) Journal
    "So I have to stare at compiler output for hours"

    What kind of idiot stares at compiler output? Seriously, wtf?

    First off, just about anything you could possibly want is already available as a binary, so if you're the type that would rather have a whopper than a filet mignon, go for it.

    But if you do want to (or, much less likely, need to) compile something, you act like that's some sort of chore, so clearly you've never done it. It's no chore at all. On modern hardware it's usually something that can be done in seconds, after all. Sure, compiling something huge (like say you decide to recompile your entire KDE installation just for fun) can take some time, but it's not like you would be forced to do that (binaries for big compiles like KDE and GNOME are easily obtained) and even if you want to do it, you dont sit and stare at compiler output. You press enter and then go to sleep/lunch/the park whatever while it works. When you come back it's done.

    The computer is supposed to be your servant, not your taskmaster.

    --
    If laughter is the best medicine, who are the best doctors?
    • (Score: 0) by Anonymous Coward on Sunday October 26 2014, @01:08AM

      by Anonymous Coward on Sunday October 26 2014, @01:08AM (#110123)

      What else is he supposed to do, use Chrome during the 8 hours it takes to compile it? Or should he use KDE during the week it takes to compile it instead, maybe? Oh, wait, none of that is possible. You can't use the software until it's done compiling!

      • (Score: 1) by Pino P on Monday November 24 2014, @12:48AM

        by Pino P (4721) on Monday November 24 2014, @12:48AM (#119267) Journal

        Then download the binary for the generic architecture and use that in a chroot while compiling a fully optimized build.