Fail more gracefully when pip --dry-run doesn't work

[terriko]

If pip --dry-run (used for testing requirements.txt files) fails, the whole process halts. This is kind of a pain when I'm using cve-bin-tool to scan arbitrary github directories. We should probably do something similar to what we do with extraction, where it logs an error message and tells you what file it couldn't scan but does not raise an exception (which stops the scan entirely leaving you with only partial results)

[metabiswadeep]

Could you please elaborate on what has to be done?

[terriko]

Try downgrading pip and running cve-bin-tool (might also work if you turn off network access?)

Basically, if your version of pip is too old it throws an exception when you run pip. We need it to throw an error instead.

[metabiswadeep]

Try downgrading pip and running cve-bin-tool (might also work if you turn off network access?)

Basically, if your version of pip is too old it throws an exception when you run pip. We need it to throw an error instead.

On downgrading pip and running cve-bin-tool it is showing "no such option: --dry-run" for pip. I guess older versions of pip do not support dry-run?