update-manager disables third-party repositories with suite suffixes
Bug #594206 reported by
Evan Broder
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
| update-manager-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: update-manager-core
This is a sort of followup to bug #147080.
If I set Sources.
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$/
| Changed in update-manager-core (Ubuntu): | |
| status: | New → Invalid |
Revision history for this message
| Evan Broder (broder) wrote | #1 |
Revision history for this message
| Robert Roth (evfool) wrote | #2 |
| Changed in update-manager (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in update-manager (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
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.