The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

XFree86 3.3 update



Previously, I reported general success with XFree86 except with
Xemacs.  (A brief review: replacing XFree86 3.2 with XFree86 3.3
caused Xemacs to core dump at *every* startup, regardless of whether
or not it was using X mode.  This rendered xemacs totally useless.)

I reported that as a bug the very first day that XFree86 3.3 was
available as a Debian package (a week or two ago, I believe).  I have
still not heard back from the maintainer of xemacs (I reported the bug
against xemacs19).

I subsequently updated my system to the 3.3-2 version of the XFree86
packages, but that did not solve the xemacs problem.

Finally, I decided to go ahead and recompile xemacs against the
XFree86 3.3 libraries.  This solved the problem.

Now, a question: I have named the compiled version xemacs19_19.15-3.1
(the latest xemacs in hamm was xemacs19_19.15-3).  Should I upload
this to unstable as a non-maintainer upload?  (Again, the xemacs in
unstable is totally useless with the X in unstable!)

(On another note, it would be really nice if we get dependencies for
source packages.)

-- 
John Goerzen          | Running Debian GNU/Linux (www.debian.org)
Custom Programming    | 
jgoerzen@complete.org | 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .