Description of problem:

I ran rpmdeplint against a package using the --repos-from-system option. The command ran for awhile until it ended in a Traceback:

bin/rpmdeplint check-upgrade /tmp/ghc-cassava-0.4.5.1-1.fc24.x86_64.rpm --repos-fr
om-system
Traceback (most recent call last):
  File "bin/rpmdeplint", line 15, in <module>
    sys.exit(rpmdeplint.cli.main())
  File "/home/rjoost/works/rpmdeplint/rpmdeplint/cli.py", line 224, in main
    return args.func(args)
  File "/home/rjoost/works/rpmdeplint/rpmdeplint/cli.py", line 95, in cmd_check_upgrad
e
    with dependency_analyzer_from_args(args) as analyzer:
  File "/home/rjoost/works/rpmdeplint/rpmdeplint/cli.py", line 153, in dependency_anal
yzer_from_args
    return DependencyAnalyzer(repos, rpms, arch=arch)
  File "/home/rjoost/works/rpmdeplint/rpmdeplint/__init__.py", line 127, in __init__
    repo.download_repodata()
  File "/home/rjoost/works/rpmdeplint/rpmdeplint/repodata.py", line 138, in download_r
epodata
    h.perform(r)
  File "/usr/lib64/python2.7/site-packages/librepo/__init__.py", line 1506, in perform
    _librepo.Handle.perform(self, result)
librepo.LibrepoException: (19, u'Cannot download repomd.xml: Cannot download repodata/
repomd.xml: All mirrors were tried', u'Usable URL not found')

After debugging I realised that one of my repositories was pointing to a URL which was returning a 404. It seems DNF handles the exception in a more user friendly way:

Failed to synchronize cache for repo 'Dropbox', disabling.


Version-Release number of selected component (if applicable):

develop

How reproducible:

100%

Steps to Reproduce:
1. Create a (system) repo with a URL returning a 404
2. Run rpmdeplint against the repo
3. profit

Actual results:

Traceback (example see above)

Expected results:

Either ignore, log and continue or at least tell me which repo is b0rked.

Additional info:

none