Bug#761859: prototype ready

2015-02-22 Thread Paul Wise
On Sun, 22 Feb 2015 00:37:49 +0100 Holger Levsen wrote: I have a prototype ready, see attached... I noticed that fixed issues are not listed, we need that so people can look up the security history of any package by clicking a 'security' link in the links section. Just an item link: True|False

debsecan now on Gitorious

2015-02-22 Thread Florian Weimer
I've moved the debsecan Git repository to Gitorious. Please speak up if you want to be added to the push ACL. -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#761859: yaml...

2015-02-22 Thread Florian Weimer
* Holger Levsen: the patch currently creates yaml, not json. Which do you prefer? JSON has less risk of unwanted data execution when deserializing. It is also supported by Python out of the box, so it's more natural for the successor of the custom debsecan format (which I created when Python

Bug#761859: yaml...

2015-02-22 Thread Holger Levsen
Hi, the patch currently creates yaml, not json. Which do you prefer? Also, is the bug description useful in the data? Do you want no data/remote/local or (null|None)/true/false? Anything else? cheers, Holger From 4237fa854c9dc4f1d8ac8de5c8e2030f68bf847b Mon Sep 17 00:00:00 2001

Bug#761859: prototype ready

2015-02-22 Thread Paul Wise
On Sun, 2015-02-22 at 19:00 +0100, Holger Levsen wrote: On Sonntag, 22. Februar 2015, Paul Wise wrote: I see a bunch of urgency set to high** and medium**, should it be high and medium instead? this comes directly from the database, so I don't think it should be modified. Hmm, it appears