[Piuparts-devel] piuparts-analyze needs to ignore BinNMU suffix in version numbers (\+b\d+$)

Andreas Beckmann debian at abeckmann.de
Sun Nov 20 01:30:39 UTC 2011


On 2011-11-19 12:54, Mika Pflüger wrote:
> When piuparts-analyze finds a log for a package in fail/ (say, version
> 2) and in bugged/ (say, version 1), and additionally finds the bug
> (say, bug number 12345) against version 1 in the bts and the equivalent

Ah, I never had enough old logs around to trigger this behaviour.

But right now I have seen this:

Moving fail/check-mk-multisite_1.1.12-1.log to bugged
Moving fail/omniidl_4.1.5-2.log to bugged
Moving fail/ganglia-monitor_3.1.7-2+b1.log to bugged
frontaccounting/2.2.10-3: Maybe the bug was filed earlier: 595591 against frontaccounting/2.2.10-2
Moving fail/debian-edu-artwork_0.0.33-1.log to bugged
Traceback (most recent call last):
  File "/org/piuparts.debian.org/share/piuparts/piuparts-analyze", line 231, in <module>
    main()
  File "/org/piuparts.debian.org/share/piuparts/piuparts-analyze", line 226, in main
    mark_logs_with_reported_bugs()
  File "/org/piuparts.debian.org/share/piuparts/piuparts-analyze", line 161, in mark_logs_with_reported_bugs
    for bug_version in get_bug_versions(bug):
  File "/org/piuparts.debian.org/share/piuparts/piuparts-analyze", line 130, in get_bug_versions
    return reversed(sorted([x.split('/', 1)[1] for x in debianbts.get_status((bug,))[0].found_versions], cmp=apt_pkg.version_compare))
IndexError: list index out of range


Andreas



More information about the Piuparts-devel mailing list