[Reportbug-maint] Processing of reportbug_4.1_amd64.changes

reportbug_4.1_amd64.changes uploaded successfully to localhost along with the files: reportbug_4.1.dsc reportbug_4.1.tar.gz reportbug_4.1_all.deb python-reportbug_4.1_all.deb Greetings, Your Debian queue daemon ___ Reportbug-maint

[Reportbug-maint] reportbug_4.1_amd64.changes ACCEPTED

Accepted: python-reportbug_4.1_all.deb to pool/main/r/reportbug/python-reportbug_4.1_all.deb reportbug_4.1.dsc to pool/main/r/reportbug/reportbug_4.1.dsc reportbug_4.1.tar.gz to pool/main/r/reportbug/reportbug_4.1.tar.gz reportbug_4.1_all.deb to pool/main/r/reportbug/reportbug_4.1_all.deb

[Reportbug-maint] Bug#512675: marked as done (reportbug: Reportbug detects wrong cpu count on multiprocessor alpha systems)

Your message dated Sun, 12 Apr 2009 13:02:03 + with message-id e1lszjz-00086f...@ries.debian.org and subject line Bug#512675: fixed in reportbug 4.1 has caused the Debian Bug report #512675, regarding reportbug: Reportbug detects wrong cpu count on multiprocessor alpha systems to be marked

[Reportbug-maint] Bug#522499: marked as done (reportbug: defaults to severity critical in ui-urwid)

Your message dated Sun, 12 Apr 2009 13:02:03 + with message-id e1lszjz-00086b...@ries.debian.org and subject line Bug#496969: fixed in reportbug 4.1 has caused the Debian Bug report #496969, regarding reportbug: defaults to severity critical in ui-urwid to be marked as done. This means that