Hi Adam, thanks for the fast reply. On Sun, Nov 28, 2010 at 13:09, Adam D. Barratt <[email protected]> wrote: > On Sun, 2010-11-28 at 12:46 +0100, Sandro Tosi wrote: >> I prepared a list of pkg_ver to report bugs against them; it contains: >> >> $ grep python-uno mbf3.packages >> python-uno_1:2.4.1+dfsg-1+lenny8 >> python-uno_1:3.2.1-7 >> python-uno_1:3.3.0~beta2-2 > [...] >> Package: python-uno >> Version: 1:3.3.0~beta2-2 >> -- >> Package: python-uno >> Version: 1:3.3.0~beta2-2 >> -- >> Package: python-uno >> Version: 1:3.3.0~beta2-2 >> >> 3 reports, all with the (highest?) same version. > > They will all have the version which occurs latest in the package file. > mass-bug builds a hash of versions, indexed by package name, so repeated > entries for a given package will simply overwrite the earlier versions.
Now I see where it's coming. wouldn't it be better to "trust" the user running mass-bug instead? it tends to be a quite dangerous tool, so extra attentions from who's using is anyhow required, so maybe you can "relax" that check. I think the optimum would be to have a way to use mass-bug to report bugs on a package with more than one effected version in a single report (so the above 3 examples simply collapse in a single report with "several" versions in it) - I dunno if that's even supported on the debbugs side, but it might be worth asking owner@ if he considers an interesting option (CC him). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To unsubscribe, send mail to [email protected].
