considers dapper-commercial a third party repository and disables it
Bug #66783 reported by
James Troup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Bug Description
I just upgraded Avril's laptop from dapper to edgy and the upgrade process warned me that it had detected a 3rd party repository and disabled it for my own safety. But in fact the "3rd party repository" was dapper-commercial. Obviously, that shouldn't be considered 3rd party or disabled on upgrade, but rather changed to edgy like all the other sources.list entries.
| Changed in update-manager: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Paul Sladen (sladen) wrote | #1 |
Revision history for this message
| Tollef Fog Heen (tfheen) wrote | #2 |
| Changed in update-manager: | |
| assignee: | nobody → mvo |
Revision history for this message
| Tollef Fog Heen (tfheen) wrote | #3 |
Revision history for this message
| Michael Vogt (mvo) wrote | #4 |
| Changed in update-manager: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Michael Vogt (mvo) wrote | #5 |
| Changed in update-manager: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Technically it probably is a 3rd party repository; as the software available in 'dapper-commerical' may not actually be available in 'edgy-commerical'.
Perhaps a generic method for rewriting all the "closely supported" archives could be added so that backports/