Current build fails because of naming discrepancy, the:
- repository is named swh-icinga-plugins
- debian package is named python3-swh.icingaplugins
- python module is named swh.icinga-plugins
- archive pushed for the python module is named swh.icinga_plugins [2]
a mixed feeling of T.T and ¯\_(ツ)_/¯ and (╯°□°）╯︵ ┻━┻
with a tendency to ;) nonetheless (especially now that i fixed it).
This allows to define an extra entry name python_module which supersedes the
`repo_name.replace('-', '.')` instruction. That original instruction is fine
for all of our other swh modules. Note that it could be better on the long run
to explicitely define that python_module for all our swh packages (but if we
agree, for another diff).
I have no clue on how to test that repository aside from modifying manually the
jobs and check if my logic is sound. So I did and the failed build [2] has been
fixed [3]
Related to T2726
[1]
```
commit df174ce493d155929c70c657809d548ffc27557b (origin/pristine-tar, pristine-tar)
Author: Antoine R. Dumont (@ardumont) <antoine.romain.dumont@gmail.com>
Date: Mon Jan 20 18:41:24 2020 +0100
pristine-tar data for swh.icingaplugins_0.0.2.orig.tar.gz
```
[2] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/3/console
[3] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/6/console