debbugs_2.4.2~exp0_amd64.changes ACCEPTED

2009-08-16 Thread Archive Administrator
Accepted: debbugs-local_2.4.2~exp0_all.deb to pool/main/d/debbugs/debbugs-local_2.4.2~exp0_all.deb debbugs-web_2.4.2~exp0_all.deb to pool/main/d/debbugs/debbugs-web_2.4.2~exp0_all.deb debbugs_2.4.2~exp0.dsc to pool/main/d/debbugs/debbugs_2.4.2~exp0.dsc debbugs_2.4.2~exp0.tar.gz to pool/mai

Bug#454248: marked as done (bugs.debian.org: please add viewable message number to web listing)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#454248: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #454248, regarding bugs.debian.org: please add viewable message number to web listing to be marked as done. This means that you claim that t

Bug#137970: marked as done (bugs.debian.org: Anyone can close bug, message is misleading)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#132274: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #132274, regarding bugs.debian.org: Anyone can close bug, message is misleading to be marked as done. This means that you claim that the pro

Bug#234362: marked as done (debbugs: $gPackagePages should be optionnal)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#234362: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #234362, regarding debbugs: $gPackagePages should be optionnal to be marked as done. This means that you claim that the problem has been dea

Bug#132274: marked as done (debbugs: "acknowledged by developer" inaccuracy)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#132274: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #132274, regarding debbugs: "acknowledged by developer" inaccuracy to be marked as done. This means that you claim that the problem has been

Bug#448861: marked as done (bugs.debian.org: Links with email addresses in uppercase don't work)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#448861: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #448861, regarding bugs.debian.org: Links with email addresses in uppercase don't work to be marked as done. This means that you claim that

Bug#228597: marked as done (debbugs: Please update Dependencies to exim4)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#228597: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #228597, regarding debbugs: Please update Dependencies to exim4 to be marked as done. This means that you claim that the problem has been de

Bug#229067: marked as done ([bugreport.cgi] Add link to the package.debian.org package page as is done in pkgreport.cgi)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#229067: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #229067, regarding [bugreport.cgi] Add link to the package.debian.org package page as is done in pkgreport.cgi to be marked as done. This m

Bug#484789: marked as done (BTS server sends 2007-14 as Year-Month.)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#484789: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #484789, regarding BTS server sends 2007-14 as Year-Month. to be marked as done. This means that you claim that the problem has been dealt w

Bug#499682: marked as done (Hardcoded spool path in scripts/age-1)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#499682: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #499682, regarding Hardcoded spool path in scripts/age-1 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#419553: marked as done (reasign: please make both packages clickable)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#419553: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #419553, regarding reasign: please make both packages clickable to be marked as done. This means that you claim that the problem has been de

Bug#452905: marked as done ([pkgreport.cgi] revise explanation of no maintainer packages (and therefore, likely non-existant))

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#452905: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #452905, regarding [pkgreport.cgi] revise explanation of no maintainer packages (and therefore, likely non-existant) to be marked as done.

Bug#127354: marked as done ([bugreport.cgi,process.in,service.in] Add date/time in the html record types and show the retitle for retitling)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#127354: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #127354, regarding [bugreport.cgi,process.in,service.in] Add date/time in the html record types and show the retitle for retitling to be mar

Bug#196947: marked as done (bugs.debian.org: control bot should report old severity when processing severity change)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#196947: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #196947, regarding bugs.debian.org: control bot should report old severity when processing severity change to be marked as done. This means

Bug#207992: marked as done (bugs.debian.org: can't view bug: An error occurred. Dammit. Error was: 205075 state kill-init at end.)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding bugs.debian.org: can't view bug: An error occurred. Dammit. Error was: 205075 state kill-init at end. to be marked as don

Bug#191306: marked as done (if sendmessage dies, process exits, making the log "strange")

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding if sendmessage dies, process exits, making the log "strange" to be marked as done. This means that you claim that the pro

Bug#415933: marked as done (debbugs: display usertags for srcpkg user when passing pkg= to pkgreport.cgi)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#415933: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #415933, regarding debbugs: display usertags for srcpkg user when passing pkg= to pkgreport.cgi to be marked as done. This means that you c

Bug#321888: marked as done (merge is overly picky)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#286792: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #286792, regarding merge is overly picky to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#103803: marked as done ([service.in] Allow reopen to unarchive archived bugs)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#153536: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #153536, regarding [service.in] Allow reopen to unarchive archived bugs to be marked as done. This means that you claim that the problem has

Bug#168213: marked as done (bugs.debian.org: merging should be allowed in different "forwarded to" states)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#286792: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #286792, regarding bugs.debian.org: merging should be allowed in different "forwarded to" states to be marked as done. This means that you

Bug#153536: marked as done (BTS can't find my bug when issuing command merge)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#153536: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #153536, regarding BTS can't find my bug when issuing command merge to be marked as done. This means that you claim that the problem has bee

Bug#172635: marked as done (X-Debbugs-CC to maintainer causes message to be sent twice)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#172635: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #172635, regarding X-Debbugs-CC to maintainer causes message to be sent twice to be marked as done. This means that you claim that the probl

Bug#475622: marked as done (removed packages are not handled properly for archiving [see #447502])

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#475622: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #475622, regarding removed packages are not handled properly for archiving [see #447502] to be marked as done. This means that you claim tha

Bug#295282: marked as done (bugs.debian.org: Can't view bug #281919)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding bugs.debian.org: Can't view bug #281919 to be marked as done. This means that you claim that the problem has been dealt w

Bug#320686: marked as done (bugs.debian.org: Internal server error when viewing #270464)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding bugs.debian.org: Internal server error when viewing #270464 to be marked as done. This means that you claim that the prob

Bug#441022: marked as done (Mixed case version string confuses version tracking)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#441022: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #441022, regarding Mixed case version string confuses version tracking to be marked as done. This means that you claim that the problem has

Bug#222264: marked as done ([debbugs packaging] should ship example apache config/.htaccess)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#64: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #64, regarding [debbugs packaging] should ship example apache config/.htaccess to be marked as done. This means that you claim that the

Bug#458822: marked as done (debbugs: Please provide a way of relating bugs with source package when doing SOAP queries)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#458822: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #458822, regarding debbugs: Please provide a way of relating bugs with source package when doing SOAP queries to be marked as done. This me

Bug#248335: marked as done (debbugs: [patch] README.mail for exim4)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#248335: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #248335, regarding debbugs: [patch] README.mail for exim4 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#288384: marked as done ([process.in] process.in lc()'s the owner of a bug; service.in does not.)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#288384: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #288384, regarding [process.in] process.in lc()'s the owner of a bug; service.in does not. to be marked as done. This means that you claim

Bug#478039: marked as done (Debian bugs mailing list software sends incorrect date header information.)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#458757: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #458757, regarding Debian bugs mailing list software sends incorrect date header information. to be marked as done. This means that you cla

Bug#458757: marked as done (Add date headers to outgoing messages before storage in log)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#458757: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #458757, regarding Add date headers to outgoing messages before storage in log to be marked as done. This means that you claim that the prob

Bug#470146: marked as done (consider bugs with no found version absent if not present in target release and not pseudopackage)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#470146: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #470146, regarding consider bugs with no found version absent if not present in target release and not pseudopackage to be marked as done.

Bug#272274: marked as done (debbugs: RFC 2047 subject lines should be decoded in web interface)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#238984: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #238984, regarding debbugs: RFC 2047 subject lines should be decoded in web interface to be marked as done. This means that you claim that t

Bug#139936: marked as done (BTS bug 'owner' code)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#133453: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #133453, regarding BTS bug 'owner' code to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#168962: marked as done (does not create links from URLs)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#168962: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #168962, regarding does not create links from URLs to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#245096: marked as done (bugs.debian.org should be utf-8ized)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#238984: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #238984, regarding bugs.debian.org should be utf-8ized to be marked as done. This means that you claim that the problem has been dealt with.

Bug#306068: marked as done (outgoing headers not properly reencoded using encode_rfc1522)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#306068: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #306068, regarding outgoing headers not properly reencoded using encode_rfc1522 to be marked as done. This means that you claim that the pro

Bug#292151: marked as done (bugs.debian.org: privacy concerns with full email header exposure)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#188561: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #188561, regarding bugs.debian.org: privacy concerns with full email header exposure to be marked as done. This means that you claim that th

Bug#188561: marked as done (Allow for removing unimportant headers)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#188561: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #188561, regarding Allow for removing unimportant headers to be marked as done. This means that you claim that the problem has been dealt wi

Bug#329457: marked as done ("bad bug log" crash in /usr/local/lib/site_perl/Debbugs/Log.pm)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding "bad bug log" crash in /usr/local/lib/site_perl/Debbugs/Log.pm to be marked as done. This means that you claim that the p

Bug#222077: marked as done ([debbugs packaging] Need to create the hash dirs db_h/00..99)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#222077: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #222077, regarding [debbugs packaging] Need to create the hash dirs db_h/00..99 to be marked as done. This means that you claim that the pro

Bug#428056: marked as done ([bugreport.cgi] Delete double leading spaces when displaying format=flowed mails)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#428056: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #428056, regarding [bugreport.cgi] Delete double leading spaces when displaying format=flowed mails to be marked as done. This means that y

Bug#485804: marked as done (Track messages replied and allow selection of bugs by them)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#485804: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #485804, regarding Track messages replied and allow selection of bugs by them to be marked as done. This means that you claim that the probl

Bug#420274: marked as done (debbugs: please take care of exim 3 going away)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#248335: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #248335, regarding debbugs: please take care of exim 3 going away to be marked as done. This means that you claim that the problem has been

Bug#463008: marked as done (bugs.debian.org: uppercase characters in versions are not properly handled)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#441022: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #441022, regarding bugs.debian.org: uppercase characters in versions are not properly handled to be marked as done. This means that you cla

Bug#293498: marked as done (Messages to ##-done for closed bug get forwarded nowhere)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#136654: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #136654, regarding Messages to ##-done for closed bug get forwarded nowhere to be marked as done. This means that you claim that the problem

Bug#136654: marked as done (encode done/forwarded acks consistently)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#136654: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #136654, regarding encode done/forwarded acks consistently to be marked as done. This means that you claim that the problem has been dealt w

Bug#296683: marked as done (Missing caracter set for bugs.debian.org?)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#238984: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #238984, regarding Missing caracter set for bugs.debian.org? to be marked as done. This means that you claim that the problem has been dealt

Bug#425614: marked as done (version regex is too strict)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#425614: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #425614, regarding version regex is too strict to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#459709: marked as done (debbugs: Last-Modified header shows up with HEAD but not with GET)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#459709: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #459709, regarding debbugs: Last-Modified header shows up with HEAD but not with GET to be marked as done. This means that you claim that th

Bug#499997: marked as done (bugs.debian.org: Ugly display when trying to display a non existing bug)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#47: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #47, regarding bugs.debian.org: Ugly display when trying to display a non existing bug to be marked as done. This means that you claim

Bug#217960: marked as done (debbugs: use hyperlinks with "cloned" messages on web pages)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#217960: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #217960, regarding debbugs: use hyperlinks with "cloned" messages on web pages to be marked as done. This means that you claim that the prob

Bug#290501: marked as done (spamscan in debbugs does not work any more after upgrading to spamassassin 3.0.2-1)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#290501: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #290501, regarding spamscan in debbugs does not work any more after upgrading to spamassassin 3.0.2-1 to be marked as done. This means that

Bug#46848: marked as done (The bug system does not understand MIME From lines.)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#238984: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #238984, regarding The bug system does not understand MIME From lines. to be marked as done. This means that you claim that the problem has

Bug#459866: marked as done (Please distinguish between new and followup messages in X-Debian-PR-Message)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#459866: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #459866, regarding Please distinguish between new and followup messages in X-Debian-PR-Message to be marked as done. This means that you cl

Bug#265267: marked as done ([pkgreport.cgi,bugreport.cgi] rearrange to have the variable information first, and the constant stuff later)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#265267: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #265267, regarding [pkgreport.cgi,bugreport.cgi] rearrange to have the variable information first, and the constant stuff later to be marke

Bug#420137: marked as done (bugs.debian.org: Confusing response when closing a bug report)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#132274: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #132274, regarding bugs.debian.org: Confusing response when closing a bug report to be marked as done. This means that you claim that the pr

Bug#238984: marked as done (Names etc. in UTF-8 are displayed incorrectly)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#238984: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #238984, regarding Names etc. in UTF-8 are displayed incorrectly to be marked as done. This means that you claim that the problem has been d

Bug#456786: marked as done (debbugs: Last-Modified header when retrieving mboxes)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#456786: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #456786, regarding debbugs: Last-Modified header when retrieving mboxes to be marked as done. This means that you claim that the problem has

Bug#260791: marked as done (debbugs on other systems)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#260791: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #260791, regarding debbugs on other systems to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#140061: marked as done (maintainer confusion?)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#140061: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #140061, regarding maintainer confusion? to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#422062: marked as done (get_status(419306) always returns an error)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#422062: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #422062, regarding get_status(419306) always returns an error to be marked as done. This means that you claim that the problem has been deal

Bug#499941: marked as done (debbugs: received a help message from request@ on error in control@)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#499941: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #499941, regarding debbugs: received a help message from request@ on error in control@ to be marked as done. This means that you claim that

Bug#293277: marked as done (debbugs: misc. fixes to scripts/service.in and debian/control)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#293277: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #293277, regarding debbugs: misc. fixes to scripts/service.in and debian/control to be marked as done. This means that you claim that the pr

Bug#179340: marked as done ([process.in] Allow X-Debbugs-*: headers to be set in Pseudo headers)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#179340: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #179340, regarding [process.in] Allow X-Debbugs-*: headers to be set in Pseudo headers to be marked as done. This means that you claim that

Bug#222118: marked as done ([debbugs packaging] The configuration files shipped with menu are outdated)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#222118: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #222118, regarding [debbugs packaging] The configuration files shipped with menu are outdated to be marked as done. This means that you cla

Bug#435926: marked as done (debbugs gets confused when a name is both a source and an unrelated binary package)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#435926: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #435926, regarding debbugs gets confused when a name is both a source and an unrelated binary package to be marked as done. This means that

Bug#447544: marked as done (Version put in lower case but version.cgi is case sensitive)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#441022: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #441022, regarding Version put in lower case but version.cgi is case sensitive to be marked as done. This means that you claim that the prob

Bug#501757: marked as done (debbugs: invalid URL generated in summary when bug contains ‘merged-upstream’ information)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#501757: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #501757, regarding debbugs: invalid URL generated in summary when bug contains ‘merged-upstream’ information to be marked as done. This mea

Bug#462322: marked as done (debbugs: pkgreport.cgi generates broken HTML)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#462322: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #462322, regarding debbugs: pkgreport.cgi generates broken HTML to be marked as done. This means that you claim that the problem has been de

Bug#219230: marked as done (debbugs: want X-Debian-PR-Source-Package, a la X-D-P-P)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#219230: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #219230, regarding debbugs: want X-Debian-PR-Source-Package, a la X-D-P-P to be marked as done. This means that you claim that the problem h

Bug#276747: marked as done (clone command documentation is wrong)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#276747: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #276747, regarding clone command documentation is wrong to be marked as done. This means that you claim that the problem has been dealt with

Bug#201825: marked as done (bugs.debian.org: control@b.d.o. ignores X-Debbugs-No-Ack: yes)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#201825: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #201825, regarding bugs.debian.org: cont...@b.d.o. ignores X-Debbugs-No-Ack: yes to be marked as done. This means that you claim that the pr

Bug#153535: marked as done (BTS can't find my bug when issuing command merge)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#153536: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #153536, regarding BTS can't find my bug when issuing command merge to be marked as done. This means that you claim that the problem has bee

Bug#97264: marked as done ([service.in] Add X-Debbugs-No-Ack: support to service.in)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#201825: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #201825, regarding [service.in] Add X-Debbugs-No-Ack: support to service.in to be marked as done. This means that you claim that the problem

Bug#432466: marked as done (bugs.debian.org: missing newline in usertags control response)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#432466: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #432466, regarding bugs.debian.org: missing newline in usertags control response to be marked as done. This means that you claim that the pr

Bug#376303: marked as done (debbugs does not create db-h/ directory)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#222077: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #222077, regarding debbugs does not create db-h/ directory to be marked as done. This means that you claim that the problem has been dealt w

Bug#188670: marked as done (debbugs: Refcard page doesn't list submission addresses)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#188670: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #188670, regarding debbugs: Refcard page doesn't list submission addresses to be marked as done. This means that you claim that the problem

Bug#288564: marked as done (Broken bug report page for bug #286414)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding Broken bug report page for bug #286414 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#318898: marked as done ([pkgreport.cgi] sort bugs acording to last activity instead of date of submission)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#318898: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #318898, regarding [pkgreport.cgi] sort bugs acording to last activity instead of date of submission to be marked as done. This means that

Bug#488245: marked as done (soap.cgi improperly serializes things that look like dates but aren't)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#484789: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #484789, regarding soap.cgi improperly serializes things that look like dates but aren't to be marked as done. This means that you claim tha

Bug#182419: marked as done ([service.in] check originator using Mail::RFC822::Address when reopen is issued)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#182419: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #182419, regarding [service.in] check originator using Mail::RFC822::Address when reopen is issued to be marked as done. This means that yo

Bug#223636: marked as done (pkgreport.cgi/archival: links to attachments broken)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#301606: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #301606, regarding pkgreport.cgi/archival: links to attachments broken to be marked as done. This means that you claim that the problem has

Bug#416321: marked as done (UTF-8 decoding in subjects eats leading spaces)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#416321: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #416321, regarding UTF-8 decoding in subjects eats leading spaces to be marked as done. This means that you claim that the problem has been

Bug#256075: marked as done (List the age of the last bug activity in the summary)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#207065: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #207065, regarding List the age of the last bug activity in the summary to be marked as done. This means that you claim that the problem has

Bug#207065: marked as done ([pkgreport.cgi] display date at which bugs were closed/opened)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#207065: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #207065, regarding [pkgreport.cgi] display date at which bugs were closed/opened to be marked as done. This means that you claim that the pr

Bug#499681: marked as done (Needless use of CGI::Alert)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#499681: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #499681, regarding Needless use of CGI::Alert to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#322719: marked as done (Bad bug log for Bug 297579)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding Bad bug log for Bug 297579 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#324146: marked as done (bugs.debian.org: broken bug #307492)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#191306: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #191306, regarding bugs.debian.org: broken bug #307492 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#419202: marked as done ([service.in] add quotes around titles in retitle action)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#419202: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #419202, regarding [service.in] add quotes around titles in retitle action to be marked as done. This means that you claim that the problem

Bug#422934: marked as done (debbugs: control results for usertags processing should contain user in results)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#422934: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #422934, regarding debbugs: control results for usertags processing should contain user in results to be marked as done. This means that yo

Bug#431459: marked as done (Please provide a visible link to the #msgno anchors)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#431459: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #431459, regarding Please provide a visible link to the #msgno anchors to be marked as done. This means that you claim that the problem has

Bug#301606: marked as done (MIME attachment broken for RFC1522 attachment names (#273993 FE))

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#301606: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #301606, regarding MIME attachment broken for RFC1522 attachment names (#273993 FE) to be marked as done. This means that you claim that the

Bug#23018: marked as done ([pkgindex.cgi] should be indexed by first letter of the package (even though we don't use this any more))

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#23018: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #23018, regarding [pkgindex.cgi] should be indexed by first letter of the package (even though we don't use this any more) to be marked as do

Bug#59355: marked as done (List of packages is too long)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#23018: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #23018, regarding List of packages is too long to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#470392: marked as done (bugs.debian.org: No error given on unexisting package)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#452905: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #452905, regarding bugs.debian.org: No error given on unexisting package to be marked as done. This means that you claim that the problem ha

Bug#467190: marked as done (does not deal properly with \r line endings in encoded messages)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:14 + with message-id and subject line Bug#467190: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #467190, regarding does not deal properly with \r line endings in encoded messages to be marked as done. This means that you claim that the

Bug#34689: marked as done (improved package listing -- bug tracking system)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#23018: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #23018, regarding improved package listing -- bug tracking system to be marked as done. This means that you claim that the problem has been d

Bug#128320: marked as done ([process.in] Allow Forwarded: to be set at submit@ time)

2009-08-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Aug 2009 14:38:12 + with message-id and subject line Bug#128320: fixed in debbugs 2.4.2~exp0 has caused the Debian Bug report #128320, regarding [process.in] Allow Forwarded: to be set at submit@ time to be marked as done. This means that you claim that the problem

  1   2   3   >