Re: Proposed refactoring of the per-release tracker pages
On Sun, 10 Jan 2010 00:31:24 +0100 Francesco Poli wrote:
> > You could use debsecan
>
> I tried, but I wasn't able to use debsecan to list all the
> vulnerabilities that affect a given release (stable, testing, or
> unstable). It keeps showing only the vulnerabilities that affect
> packages installed on *my* system.
>
> Is there some option I failed to find in the man page?
I'm not really sure about this, but you could download the debsecan
source and try to modify it for your needs.
> I can try to use the SVN web interface, but... wouldn't it boil down
> to scrape web pages, *again*?
Those files contain the underlying data that the tracker derives its
information from. The formats of those files are very unlikely to
change in the future; whereas the tracker web interface is more of a
moving target. I'm not too familiar with wsvn, but there may be a way
to get to the data files directly, rather than scraping the fancy
display.
On the other hand, it may be easy enough to fix your code to work with
the upcoming modifications.
Mike
Reply to: