Bug#761859: prototype ready

2015-02-23 Thread Holger Levsen
Hi, On Montag, 23. Februar 2015, Raphael Hertzog wrote: The only missing data I see is the Debian bug report assigned to each CVE. I'll add that. And you call the file json but it contains YAML :-) yeah, fixed in the last attached patch, but I will rewrite it to actually output json...

Bug#761859: prototype ready

2015-02-23 Thread Holger Levsen
Hi, On Montag, 23. Februar 2015, Paul Wise wrote: Hmm, it appears that these are the default urgency from NVD and the ones without asterisks are ones set by SVN committers. That doesn't appear to be a distinction worth preserving but it is fine to do so. I kept it under the premise of

Bug#761859: prototype ready

2015-02-23 Thread Raphael Hertzog
On Sun, 22 Feb 2015, Holger Levsen wrote: new output is attached in compressed form. The only missing data I see is the Debian bug report assigned to each CVE. And you call the file json but it contains YAML :-) Otherwise, I see that you have the raw data per real suite (aka squeeze is never

DSA candidates

2015-02-23 Thread Raphael Geissert
cabextract -- commons-httpclient -- file -- fuseiso -- jruby -- kgb-bot -- libcsoap -- libidn -- mini-httpd -- oss4 -- patch -- procmail -- redmine -- wss4j -- novnc/stable -- tiff3/stable -- -- The above is a list of DSA candidates based on the tracker's information. One should evaluate the

Bug#761859: prototype ready

2015-02-23 Thread Paul Wise
On Mon, 2015-02-23 at 14:59 +0100, Holger Levsen wrote: surely. I just wasn't sure whether this should be done on the security-tracker side or by it's users... or I could provide two versions: json-full and json(- aggregated) - do you think that would be useful? I think it would be useful