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: 2) by frojack on Saturday October 25 2014, @07:19PM
But rather than just patching it, they have actually started what should have been done all along.
They forked openssl, went in with a meat cleaver and cut all the usless detritus that has been added over the years but never uses. They call it LibreOSS [libressl.org] and it will become the the standard for OpenBSD going forward. (probably with 5.6).
Opensuse says its not quite possible to adopt it as the standard just yet, because something in their distro has to find all dependencies and adjust all packages to allow either ssl suite and also to account for glibc differences.
Wiki: http://en.wikipedia.org/wiki/LibreSSL [wikipedia.org]
No, you are mistaken. I've always had this sig.