Hi, I've just reviewed this bug report.

I think the real issue here, is the one described in the README.Debian
(section _Current Design Limitation_).

When source-version differs from binary-version, version tracking fails
to work properly.


For example, consider bug #552764 of libgcj-bc/4.3.3-9+nmu1, which has
been fixed in libgcj-bc/4.3.4-1 .
This bug has severity serious and should be listed by the following
command:

  $ apt-listbugs list libgcj-bc/4.3.3-9+nmu1
  Reading package fields... Done
  Reading package status... Done
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done

but, as can be seen, fails to be listed.
The same bug should *not* be listed by the following command:

  $ apt-listbugs list libgcj-bc/4.3.4-1
  Reading package fields... Done
  Reading package status... Done
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done

and, indeed, it is *not* listed, but for the wrong reason
(because 4.3.4-1 >= 1.88).

If we manually use source-versions, version tracking works:

  $ apt-listbugs list libgcj-bc/1.87+nmu1
  Reading package fields... Done
  Reading package status... Done
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done
  serious bugs of libgcj-bc (4.3.3-9+nmu1 -> 1.87+nmu1) <marked as done in some 
version>
   #552764 - no-copyright-file (Fixed: gcc-defaults/1.88)
  Summary:
   libgcj-bc(1 bug)
  $ apt-listbugs list libgcj-bc/1.88
  Reading package fields... Done
  Reading package status... Done
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done


I think apt-listbugs should try to internally and transparently convert
the binary-version into the corresponding source-version before
querying the BTS via SOAP, and the convert back source-version into
binary-version before presenting data to the user (or performing any
other binary-version based operation).

This is important for both the 'list' and the 'apt' commands.

I don't know whether this conversion is actually feasible and
how easy it could be.  For instance, how could you tell that
libgcj-bc/4.3.2-1 belongs to src:gcc-defaults/1.76 ?
Remember that you do not necessarily have the corresponding .deb
package available, and that this version is not necessarily
available from any configured apt repositories...



-- 
 New location for my website! Update your bookmarks!
 http://www.inventati.org/frx
..................................................... Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4

Attachment: pgpcvLPbMYJIW.pgp
Description: PGP signature

Reply via email to