update-manager disables third-party repositories with suite suffixes

[Evan Broder]

Binary package hint: update-manager-core

This is a sort of followup to bug #147080.

If I set Sources.AllowThirdParty=yes in an /etc/update-manager/release-upgrades.d/foo.cfg file, that works great for repositories where the pocket name matches the Ubuntu release I'm running exactly (i.e. "jaunty" or "lucid")

However, we also have a second pocket that we use for testing and development - we took inspiration from Ubuntu and called ours "jaunty-proposed" et al. Because the suite name in the sources.list entry doesn't exactly match the name of the Ubuntu release, update-manager forcibly disables that repository.

It would be excellent if update-manager could deal with sources.list entries that match /^suite/ instead of just /^suite$/

[Evan Broder (broder)]

Here is an example sources.list.d file for testing fixes to this bug.

With the current behavior, the first two "lucid" lines would get replaced with "maverick", but the second two "lucid-proposed" lines would be commented out.

[Robert Roth (evfool)]

Thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]