On Sun, 30 Oct 2022 12:47:33 +0200 Adrian Bunk wrote:

> On Sun, Oct 30, 2022 at 11:30:58AM +0100, Axel Beckert wrote:
> >...
> > To do that it seems only marginally necessary how other releases a named
> > as it only needs to know the release name of the release its running
> > on. For that it should suffice to know a list of all tags which are
> > _not_ release names.
> 
> I don't know much about interfaces to the BTS, but there might be
> some usable existing interface/implementation for such information.

I am not aware of any existing SOAP interface for this in debbugs.
At least, I cannot find it among the [documented] interfaces.

[documented]: <https://www.donarmstrong.com/debbugs_documentation/SOAP.html>

Maybe it would be worth requesting this feature to debbugs upstream?
Are you willing to do so?

Actually, this is related to another pending feature request: [#694979].
A possible enhanced version of 'get_bugs' could also allow the client
to specify the release it is interested in, and the BTS would only
return bugs that affect the specified binary versions of the specified
binary packages on the specified release (taking release-related tags
into account).

[#694979]: <https://bugs.debian.org/694979>

> 
> If available, this would be preferrable to an own implementation
> interpreting the sometimes weird and archaic ways how the BTS works.

I agree that a server-side implementation would be better than a
client-side one, since it would not need to closely chase any
server-side change.

> 
> > Then again, if new not-release-name tags are added to the BTS in the
> > future, having a positive list of all known release names (which are
> > usually known two releases in advance) might be helpful nevertheless.
> >...
> 
> The distro-info-data package can be used if such information is required.

Yes, I agree, but with the limitations I expressed in my reply to Axel
("which release am I running?" does not always have a clear-cut answer
and relying on distro-info-data would be Debian-specific anyway, or
would require porting that package to any other distribution we want
apt-listbugs to run on).


Anyway, thanks for your comments, Adrian!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgphv5iVyO0Pg.pgp
Description: PGP signature

Reply via email to