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: 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.