Change Details

Current build fails because of naming discrepancy: - the repository is named swh-icinga-plugins - the debian package is named python3-swh.icingaplugin - the python module is named swh.icinga-plugins - the archive pushed for the python module is name swh.icinga_plugins a mixed feeling of T.T and ¯\_(ツ)_/¯ and (╯°□°）╯︵ ┻━┻ with a tendency to ;) nonetheless... I don't want to deal with the renaming of that module/package though. So this is trying to define an extra entry name python_module which if defined, allows to supersede the `repo_name.replace('-', '.')` stanza which is fine for all of our other swh modules. I have no clue on how to test that repository aside from modifying manually the jobs and check if my logic is sound. It has fixed the build. A git show on the pristine-tar branch helped in finding the discrepancy [2]. This fixes the build [1] Related to T2726 [1] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/3 https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/4/console [2] ``` 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 ```

Current build fails because of naming discrepancy: - the repository is named swh-icinga-plugins - the debian package is named python3-swh.icingaplugins - the python module is named swh.icinga-plugins - the archive pushed for the python module is name swh.icinga_plugins a mixed feeling of T.T and ¯\_(ツ)_/¯ and (╯°□°）╯︵ ┻━┻ with a tendency to ;) nonetheless... I don't want to deal with the renaming of that module/package though. So this is trying to define an extra entry name python_module which if defined, allows to supersede the `repo_name.replace('-', '.')` stanza which is fine for all of our other swh modules. I have no clue on how to test that repository aside from modifying manually the jobs and check if my logic is sound. It has fixed the build. A git show on the pristine-tar branch helped in finding the discrepancy [2]. This fixes the build [1] Related to T2726 [1] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/3 https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/4/console [2] ``` 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 ```

Current build fails because of naming discrepancy: - the repository is named swh-icinga-plugins - the debian package is named python3-swh.icingaplugins - the python module is named swh.icinga-plugins - the archive pushed for the python module is name swh.icinga_plugins a mixed feeling of T.T and ¯\_(ツ)_/¯ and (╯°□°）╯︵ ┻━┻ with a tendency to ;) nonetheless... I don't want to deal with the renaming of that module/package though. So this is trying to define an extra entry name python_module which if defined, allows to supersede the `repo_name.replace('-', '.')` stanza which is fine for all of our other swh modules. I have no clue on how to test that repository aside from modifying manually the jobs and check if my logic is sound. It has fixed the build. A git show on the pristine-tar branch helped in finding the discrepancy [2]. This fixes the build [1] Related to T2726 [1] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/3 https://jenkins.softwareheritage.org/job/debian/job/packages/job/DICP/job/update-for-release/4/console [2] ``` 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 ```