Hello,
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

So I expect to see 3 bugs with different versions, but instead:

$ mass-bug --subject="test"  mbf3.template mbf3.packages | grep -A1 "Package:
python-uno"
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.

Regards,
Sandro
--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBCHANGE_RELEASE_HEURISTIC=changelog
DEBCHANGE_MAINTTRAILER=no
USCAN_DESTDIR=/home/morph/deb/tarballs/
USCAN_SYMLINK=rename
DEBUILD_LINTIAN_OPTS=-I
DEBCHANGE_MULTIMAINT_MERGE=yes
DEBSIGN_KEYID=444DD950

[...]

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.

Regards,

Adam

Hi Adam,
thanks for the fast reply.

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,