Processed: severity of 431780 is serious, severity of 432195 is serious, severity of 431781 is serious ... ... ... ...

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.13 > severity 431780 serious Bug#431780: w3cam: freetype1 deprecation Severity set to `serious' from `important' > severity 432195 serious Bug#432195: vgrabbj: freetype1 deprecation Seve

Bug#461532: mc: filenames starting with space breaks the ssh (Shell) connection

Package: mc Version: 1:4.6.1-8 Severity: important If there is a filename starting with space the the ssh (Shell) connection to that directory does not show the first space character. If the file is accessed with copy (F5), move (F6) or view (F3), the ssh connection will be completely broken. [E

Bug#426387: smarteiffel2: FTBFS: usr/lib/smarteiffel2/bin/eiffeltest': No such file or directory

It FTBFSs for me in an unstable pbuilder. I don't know if it makes a difference but I do have /bin/sh using /bin/dash to test the bashism bugs. Do the buildds use dash? I was hoping to work on this but it's a damn tarball in source package and I HATE those. :-) Thanks, Barry deFreese --

Bug#460906: fixed

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: doc-html-w3 | 2003.03-2 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s)

Bug#460318: marked as done (New upstream version 2.4)

Your message dated Sun, 20 Jan 2008 05:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#460318: fixed in mxml 2.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#442416: marked as done (libmxml1: Cannot load zynaddsubfx's XML files)

Your message dated Sun, 20 Jan 2008 05:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#442416: fixed in mxml 2.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#461382: x11vnc -forever segfault

| 1) start on 10.0.0.1: x11vnc -forever | 2) connect and disconnect a couple of times (just close the vncviewer window): | #! /bin/sh | | while true; | do | vncviewer -passwd VNCpasswdfile 10.0.0.1 | done I tried this on a lenny install and could not reproduce the problem, even "X-ing out" the vn