Bug#761859: security-tracker json deployed
Hi,
On Mon, 16 Mar 2015, Holger Levsen wrote:
> Hi Raphael,
>
> On Montag, 16. März 2015, Raphael Hertzog wrote:
> > I'm currently trying to use the generated json but the data below the
> > releases field doesn't correspond to what we discussed. It contains
> > entries like wheezy-security or squeeze-security when it was supposed
> > to have only the underlying release names "squeeze" or "wheezy".
>
> The repository dictionary has what you are looking for. The releases
> dictionary indeed lists all versions in all existing releases.
The repository dictionary doesn't have the data that I'm interested in.
> Maybe you would prefer the releases dict to only have keys squeeze, wheezy,
> jessie and sid and an additional sub-release key?
Yes, the entries in "releases" must be predictable. I must be able to
lookup issue_data['releases']['squeeze']['status'] and have the status in
squeeze no matter what sub-release has the latest version.
I also noticed that we have nowhere data that says that an
issue is <undetermined>... maybe those issues should be entirely dropped?
I don't understand why we have that status in the first place.
But my first try at identifying issues open in squeeze (i.e. an improved
https://security-tracker.debian.org/tracker/status/release/oldstable) led
me to showing many such issues... and I want to filter them out.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Reply to: