Processing of fusionsound_1.0.0-3_i386.changes

fusionsound_1.0.0-3_i386.changes uploaded successfully to localhost along with the files: fusionsound_1.0.0-3.dsc fusionsound_1.0.0-3.diff.gz libfusionsound-doc_1.0.0-3_all.deb libfusionsound-1.0-0_1.0.0-3_i386.deb libfusionsound-dev_1.0.0-3_i386.deb Greetings, Your Debian queue

Processing of dfb++_1.0.0-4_i386.changes

dfb++_1.0.0-4_i386.changes uploaded successfully to localhost along with the files: dfb++_1.0.0-4.dsc dfb++_1.0.0-4.diff.gz libdfb++-1.0-0_1.0.0-4_i386.deb libdfb++-dev_1.0.0-4_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a sub

Bug#434457: Fixed it.

tags 434457 +patch thanks I fixed this bug. The problem was an uncaught exception when reading in sm files that contained letters. I don't know what the letters are supposed to mean, but pydance should convert unrecognized input to a sane default, ignore, or give an error, rather than crashing. Th

Processed: Fixed it.

Processing commands for [EMAIL PROTECTED]: > tags 434457 +patch Bug#434457: Pydance crashes. There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) --

Bug#465376: varkon: bashism in /bin/sh script

Package: varkon Severity: important Version: 1.18A-3 User: [EMAIL PROTECTED] Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' ou

Bug#432932: #432932: adding security tag

tag 432932 security thanks Anyone feel free to correct me if I'm wrong but this looks like a security bug. Regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EM

Processed: #432932: adding security tag

Processing commands for [EMAIL PROTECTED]: > tag 432932 security Bug#432932: metasend: Slightly exploitable MIME type setting There were no tags set. Tags added: security > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (admin

Bug#465349: metamail: bashism in /bin/sh script

Package: metamail Severity: important Version: 2.7-53 User: [EMAIL PROTECTED] Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' o

Rastplatzsex - Hier geht was ab !

18137 - dloaswod - 048 - badmx --- Parkplatzsex auch in deiner Nähe http://www.rastplatzsex.tk

Bug#449843: marked as done (libgringotts: debian/watch fails to report upstream's version)

Your message dated Mon, 11 Feb 2008 21:02:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449843: fixed in libgringotts 1.2.1-12 has caused the Debian Bug report #449843, regarding libgringotts: debian/watch fails to report upstream's version to be marked as done. This means tha

Bug#449838: marked as done (gringotts: debian/watch fails to report upstream's version)

Your message dated Mon, 11 Feb 2008 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449838: fixed in gringotts 1.2.10~pre1-2 has caused the Debian Bug report #449838, regarding gringotts: debian/watch fails to report upstream's version to be marked as done. This means that

Bug#374358: marked as done (gringotts: Gringotts crashes when running to a remote X server)

Your message dated Mon, 11 Feb 2008 18:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#374358: fixed in gringotts 1.2.10~pre1-1 has caused the Debian Bug report #374358, regarding gringotts: Gringotts crashes when running to a remote X server to be marked as done. This means

Bug#459892: marked as done (New upstream version 1.2.9pre4)

Your message dated Mon, 11 Feb 2008 18:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#459892: fixed in gringotts 1.2.10~pre1-1 has caused the Debian Bug report #459892, regarding New upstream version 1.2.9pre4 to be marked as done. This means that you claim that the problem

Bug#459892: marked as done (New upstream version 1.2.9pre4)

Your message dated Mon, 11 Feb 2008 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#459892: fixed in gringotts 1.2.10~pre1-2 has caused the Debian Bug report #459892, regarding New upstream version 1.2.9pre4 to be marked as done. This means that you claim that the problem

Bug#443900: marked as done (Gringotts actually does not start under Debian Sid 32 Bit)

Your message dated Mon, 11 Feb 2008 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443900: fixed in gringotts 1.2.10~pre1-2 has caused the Debian Bug report #443900, regarding Gringotts actually does not start under Debian Sid 32 Bit to be marked as done. This means that

Bug#443900: marked as done (Gringotts actually does not start under Debian Sid 32 Bit)

Your message dated Mon, 11 Feb 2008 18:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#443900: fixed in gringotts 1.2.10~pre1-1 has caused the Debian Bug report #443900, regarding Gringotts actually does not start under Debian Sid 32 Bit to be marked as done. This means that

Bug#449838: marked as done (gringotts: debian/watch fails to report upstream's version)

Your message dated Mon, 11 Feb 2008 18:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#449838: fixed in gringotts 1.2.10~pre1-1 has caused the Debian Bug report #449838, regarding gringotts: debian/watch fails to report upstream's version to be marked as done. This means that

Bug#374358: marked as done (gringotts: Gringotts crashes when running to a remote X server)

Your message dated Mon, 11 Feb 2008 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#374358: fixed in gringotts 1.2.10~pre1-2 has caused the Debian Bug report #374358, regarding gringotts: Gringotts crashes when running to a remote X server to be marked as done. This means

Bug#440789: Probably fixed in 1.2.10~pre1-1

Hi, I believe this bug may be fixed in 1.2.10~pre1-1, which I just uploaded. It would be nice if someone can try this on amd64 and post the results. -- Wesley J. Landaker <[EMAIL PROTECTED]> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 signature.asc Description: This is a d

mma_0.12-2_i386.changes ACCEPTED

Accepted: mma_0.12-2.diff.gz to pool/main/m/mma/mma_0.12-2.diff.gz mma_0.12-2.dsc to pool/main/m/mma/mma_0.12-2.dsc mma_0.12-2_all.deb to pool/main/m/mma/mma_0.12-2_all.deb Override entries for your package: mma_0.12-2.dsc - source sound mma_0.12-2_all.deb - optional sound Announcing to [

Processing of mma_0.12-2_i386.changes

mma_0.12-2_i386.changes uploaded successfully to localhost along with the files: mma_0.12-2.dsc mma_0.12-2.diff.gz mma_0.12-2_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT

Bug#454212: megahal: Confirmed in etch

Hello, * Giuliani Vito, Ivan [Sun, Feb 10, 2008 at 11:36:34PM +0100]: > The backtrace is attached. > > The megahal.brn file that it tries to open doesn't exists. Maybe it is > trying to make some read/write operation on it without checking if it > has been correctly opened? Thanks for the backtr

Bug#454212: megahal segfaults as soon as it's launched

Niko Tyni wrote: Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. The attached patch fixes a stack corruption issue on 64-bit architectures (reading 8 bytes into a 4-byte buffer) and an off-by-one sprintf overflow in the error and status file name in