Hi,

I just tried to install dgit and got the following:

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  hevea libdb-dev libdb5.3-dev libfuzzylite5.0 libpopt-dev librpm-dev libselinux1-dev libsepol1-dev libxm
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libjson-perl
Recommended packages:
  libjson-xs-perl
The following NEW packages will be installed:
  dgit libjson-perl
0 upgraded, 2 newly installed, 0 to remove and 115 not upgraded.
Need to get 134 kB of archives.
After this operation, 361 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://http.debian.net/debian/ testing/main libjson-perl all 2.90-1 [86.0 kB]
Get:2 http://http.debian.net/debian/ testing/main dgit all 0.30 [48.0 kB]
Fetched 134 kB in 0s (264 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of dgit (→ 0.30) <Resolved in some Version>
 b1 - #774628 - dgit must support intended dgit repo move (Fixed: 0.3)
Summary:
 dgit(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]



Bug #774628 was fixed in version 0.30, yet somehow apt-listbugs seems to
think that it was only fixed in version 0.3. Since version 0.3 is lower
than version 0.30 it does not see the bug being fixed in the current
version I suppose.

I do not know why above it stripped off the trailing zero.

cheers, josch

On Sun, 19 Jul 2015 14:23:24 +0200 Johannes Schauer wrote:

[...]

Hello Johannes,
thanks for your bug report!
[...]

I've just managed to reproduce the issue.
What happens is that bug #774628 is found in version "dgit/0.22.1" and
fixed in version "0.30".
Hence, apt-listbugs should consider dgit/0.30 as not buggy.

However, the BTS SOAP interface apparently sends this fixed version
("0.30") as a number (0.3), rather than as a string.
As a consequence, apt-listbugs considers #774628 as fixed in version
0.3 and *then* found again in the later version 0.22.1 : the final
result is that it considers dgit/0.30 as buggy.

The BTS SOAP interface sends this fixed version as the 0.3 number,
rather than as the "0.30" string.
The --debug option of apt-listbugs shows:

[...]
#<SOAP::Mapping::Object:0x1011d90 {}forwarded="" {}unarchived="" {}outlook="" {}location="db-h" {}subject="dgit must support intended dgit repo move" {}fixed_versions=[0.3] {}owner="" {}severity="serious" {}affects="" {}found={"dgit/0.22.1"=>nil} {}originator="Ian Jackson <ijackson@chiark.greenend.org.uk>" {}date=1420469821 {}blocks="" {}fixed_date=[] {}log_modified=1436360961 {}found_date=[] {}blockedby="" {}summary="" {}keywords="" {}archived=0 {}source="dgit" {}done="Ian Jackson <ijackson@chiark.greenend.org.uk>" {}id=774628 {}tags="" {}package="dgit" {}msgid="<21674.42326.891976.60160@chiark.greenend.org.uk>" {}mergedwith="" {}last_modified=1436360961 {}fixed={0.3=>nil} {}pending="done" {}bug_num=774628 {}found_versions=["dgit/0.22.1"]>
[...]



I am reassigning your bug report to package debbugs.

Dear debbugs maintainers, could you please look into this issue?
I think the BTS SOAP interface should always treat fixed/found versions
as strings, and never as numbers (even when they look like numbers!).

Please fix this issue, by forcing the SOAP interface to always send
fixed/found versions as strings.

Thanks for your time!
Bye.

Heh. Yeah, this definitely seems to be the bug. YA example of why me
being lazy in the soap interface description has resulted in some issues
like this.

I'll see what i can do to fix this up.

Hello Don, thanks for confirming!

Good, thanks a lot for your helpfulness.

Bye.