One thing I caught in the most briefest of surface level reviews:
On Wed, Aug 03, 2022 at 07:05:15AM -0000, Alex Murray wrote:
> +# TODO - decide if we want to keep this - for now leave it out
> +
> +# also parse debian's embedded-code-copies and amalgate that into data
> +for f in ["../security-tracker/data/embedded-code-copies"]:
If you do keep this, please use the `secure_testing_path`
from the ~/.ubuntu-cve-tracker.conf config file (obtained via
cve_lib.read_config()) instead of hard-coding a relative path and
repo name when reading debian's embedded-code-copies data.
One thing I caught in the most briefest of surface level reviews:
On Wed, Aug 03, 2022 at 07:05:15AM -0000, Alex Murray wrote: code-copies and amalgate that into data tracker/ data/embedded- code-copies" ]:
> +# TODO - decide if we want to keep this - for now leave it out
> +
> +# also parse debian's embedded-
> +for f in ["../security-
If you do keep this, please use the `secure_ testing_ path` cve-tracker. conf config file (obtained via read_config( )) instead of hard-coding a relative path and code-copies data.
from the ~/.ubuntu-
cve_lib.
repo name when reading debian's embedded-
Thanks.
--
Steve Beattie
<email address hidden>