Re: Dealing with renamed source packages during CVE triaging
On Fri, Jun 15, 2018 at 05:21:55PM +1000, Brian May wrote:
> Brian May <email@example.com> writes:
> > So we could write a script, lets say:
> > bin/list-potential-packages-affected-by-code-copies
> In investigating the possibility of this, I noticed the scripts in
> lib/python/sectracker use legacy python coding standards.
> I have updated these files on my local box to work with Python 3, but
> refraining from pushing for now, because of the possibilty I might break
> something important.
When the Debian Security Tracker was created, Python 3 didn't even exist
Feel free to make a pull request, I don't think we have a specific dependency
on Python 2 modules anywhere. But it might take a bit to get reviewed/deployed
as it's not a high priority issue.