Incomplete UDD import of CPE info from upstream/metadata?

2016-12-15 Thread Petter Reinholdtsen
Hi. I was looking at the automatic CVE tracking a bit today, and hoped to figure out which packages had the CPE field already in their debian/upstream/metadata file. But according to UDD there are none: udd=> select * from upstream_metadata where key = 'CPE'; source | key | value +--

Bug#824912: tracker.d.o: add an API for action items

2016-12-15 Thread Raphael Hertzog
Hi, On Wed, 14 Dec 2016, efkin wrote: > I decided to keep DRF 2.4.3. But i'm happy to change it if you prefer. > I have no big reasons to prefer one or the other one, so i fallback on > the fact that if it's on stable i go for it. stretch is coming in a few months and we are not using Django from

Re: Incomplete UDD import of CPE info from upstream/metadata?

2016-12-15 Thread Paul Wise
On Thu, Dec 15, 2016 at 8:17 PM, Petter Reinholdtsen wrote: > I was looking at the automatic CVE tracking a bit today, and hoped to > figure out which packages had the CPE field already in their > debian/upstream/metadata file. But according to UDD there are none: I expect that is because UMEGAY

Re: Incomplete UDD import of CPE info from upstream/metadata?

2016-12-15 Thread Charles Plessy
Le Fri, Dec 16, 2016 at 07:59:53AM +0800, Paul Wise a écrit : > On Thu, Dec 15, 2016 at 8:17 PM, Petter Reinholdtsen wrote: > > > I was looking at the automatic CVE tracking a bit today, and hoped to > > figure out which packages had the CPE field already in their > > debian/upstream/metadata file