Package: debbugs Version: 2.4.2~exp0 Severity: normal Hi!
I think I found a bug in the BTS, hence I am reporting it against the experimental version of debbugs (which I believe is the closest version to what is used in the BTS, right?). The following example use of apt-listbugs shows the problem: $ apt-listbugs list gstreamer0.10-plugins-good Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of gstreamer0.10-plugins-good (-> ) <marked as done in some version> (Fixed: gstreamer0.10-plugins-good/0.10.8-4.1).1 unistallable due to .mo serious bugs of gstreamer0.10-plugins-good (-> ) <unfixed> #532352 - gstreamer0.10-plugins-good: CVE-2009-1932 integer overflows Summary: gstreamer0.10-plugins-good(2 bugs) This is wrongly displayed! You cannot even see the first bug number! The problem is that the first bug report includes a '\r' character in its subject and thus messes up with apt-listbugs description line building... I have already worked around this problem in apt-listbugs with a modification in the BTS SOAP reply parsing code. This modification will be included in the next release of apt-listbugs (version 0.1.1) and is visible on the public git repository: http://git.debian.org/?p=apt-listbugs/apt-listbugs.git;a=commitdiff;h=0ca67de284c11926221959a0ee0237dd0c3bd84d With this modification, the above command gives the following correct output: $ apt-listbugs list gstreamer0.10-plugins-good Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of gstreamer0.10-plugins-good (-> ) <marked as done in some version> #515836 - gstreamer0.10-plugins-good: 0.10.8-4.1 unistallable due to .mo (Fixed: gstreamer0.10-plugins-good/0.10.8-4.1) serious bugs of gstreamer0.10-plugins-good (-> ) <unfixed> #532352 - gstreamer0.10-plugins-good: CVE-2009-1932 integer overflows Summary: gstreamer0.10-plugins-good(2 bugs) However, the other apt-listbugs co-maintainer (Ryan Niebur) and I think that this is a bug in the BTS and should be fixed there. The BTS should drop '\r' characters from bug report subjects, so that any tool which queries the BTS via its SOAP interface won't get malformed subjects and won't mess up while trying to display them. I hope that you agree with this analysis and that this bug is not to difficult to fix. Thanks for your time. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
