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: 0) by Anonymous Coward on Sunday October 26 2014, @01:11AM
In the past, I would have. I've contributed a number of fixes to Debian packages in the past. I used to maintain several packages, too. But after the whole systemd incident, and the tyranny that it involved, I refuse to contribute to the Debian project any longer. When FreeBSD 10.1 is out in a couple of weeks, I'm switching to it, and I'm not looking back. I'm done with Debian as a contributor, and I'll soon be done with it as a user.
(Score: 0) by Anonymous Coward on Sunday October 26 2014, @02:15AM
But you'll continue on as a whiner . . .
(Score: 0) by Anonymous Coward on Sunday October 26 2014, @01:00PM
Pointing out Debian's idiocy is much more productive than trying to contribute to Debian. It's not worth contributing until the idiocy has been cleared away.