deal with landscape repositories during upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Fix Released
|
Medium
|
Unassigned | ||
update-manager-core (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Dapper |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: update-manager-core
The official Landscape repositories are considered third party ones and are disabled during a distribution upgrade.
TEST CASE:
0. install gutsy
1. add "deb http://
2. run update-manager and click on "upgrade"
3. verify that update-manager tells you that third party repository have been disabled, check /etc/apt/
4. cancel the upgrade
5. run "update-manager --proposed" and click on "upgrade"
6. verify that no message about third party sources is displayed and check that /etc/apt/
7. ignore the error about the authentication failure, that is because this test here has not added the required repository key
Their format is:
deb http://
We currently support all distros from dapper to hardy, so the possibilities for sources.list entries are:
deb http://
deb http://
deb http://
deb http://
deb http://
So, after a gutsy -> hardy upgrade, this line:
deb http://
should be changed to:
deb http://
and the packages from that repo upgraded too as usual so we end up with landscape related packages built for hardy.
description: | updated |
Changed in landscape: | |
importance: | Undecided → Medium |
milestone: | none → mthood |
Changed in landscape: | |
status: | New → Fix Released |
Changed in update-manager-core: | |
status: | Fix Committed → Fix Released |
This is fixed in my local bzr tree and will be part of the next upload.