debmirror doesn't work with Canonical ESM

[Danielle Zephyr Malament]

debmirror tries to put Canonical Ubuntu Extended Support repos in the wrong dist (e.g. 'trusty' instead of 'trusty-security', which breaks the paths it looks for on the remote server. This is because there is a check for origin='Ubuntu' but not origin='UbuntuESM'. This diff fixes it:

} elsif ($origin eq "Ubuntu" or $origin eq "Canonical") {

to

} elsif ($origin eq "Ubuntu" or $origin eq "UbuntuESM" or $origin eq "Canonical") {

I was able to reproduce with the latest versions on both Trusty and Bionic.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Fleish (lasnchpad)]

This impacts debmirror in Debian stretch & buster as well. IMO, this should be fixed by Canoncial in the ESM repositories vs. trying to update debmirror for this new naming convention they've introduced.

[Thayne (thayne-u)]

Is there any workaround for this? I'm running into this while trying to mirror the fips-updates repo on ubuntu 20.04.

[Thayne (thayne-u)]

Of note, the fips updates have an origin of `UbuntuFIPSUpdates` probably that check should be if the origin _starts_ with `Ubuntu` not if it is exactly equal to ubuntu

[Thayne (thayne-u)]

Here's a patch that I think would fix it.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "debmirror.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]