Add missing repositories to the download page

[voegelas]

Repositories without a package whose name matches the OBS package name are currently not added to the download page. Debian package names sometimes differ from RPM package names. For example, perl-URI is named liburi-perl on Debian-based systems.

This pull request makes the following modifications:

1. The API request fetches all binaries as mentioned in Add option to query OBS repo by package rather than binary name. #1036.
2. As before repositories with a package whose name matches the OBS package name are added to the download page. Nothing changes for these repositories. As before only the matching package is added.
3. Additionally, the repositories that weren't added in the previous step are added to the download page.
4. The Debian section in the ERB template outputs the Debian package name instead of the OBS package name.

Screenshots

Source: https://software.opensuse.org//download.html?project=home%3Avoegelas&package=perl-CPANPLUS-Dist-Debora

Current download page without Debian repositories

New download page with Debian repositories

---

• I've included before / after screenshots or did not change the UI

[hellcp]

So this was partly intentional, and I don't know if this is the best solution to the problem. As you implemented it, we will have quite a lot of packages listed when the source package in obs creates a lot of subpackages. My preference would probably be to list subpackages from the source package as links to different package pages, so that it's still simple to just link to a specific subpackage if the packager would rather do that.

[voegelas]

Both RPM and Debian repositories with a package that matches the OBS package name are handled as before: Only the matching package is added. I doubt that there are many repositories without a matching package and lots of subpackages.

Debian package names that differ from RPM package names are an exception. Mostly modules for Python, Perl etc. that rarely have got subpackages.

[hellcp]

This is not all that uncommon in case of RPMs though, there are plenty of packages that don't build the root package, but only exist as a bunch of subpackages. Granted, we do have the publishing sources enabled, so in most cases the root package will still be displayed as src.rpm file, which is not ideal in its own right.

[voegelas]

I will update the code to ignore repositories with subpackages.

[voegelas]

The code does now only add additional repositories with exactly one package. The failed unit test is probably caused by missing API credentials. But I do not have the time to look into that code complexity message from codeclimate, which in my opinion is nonsense. I give up.