| 2013-07-08 21:29:17 |
Andrew Starr-Bochicchio |
bug |
|
|
added bug |
| 2013-07-08 22:13:29 |
Launchpad Janitor |
branch linked |
|
lp:~andrewsomething/ubuntu-release-upgrader/lp1199157 |
|
| 2013-07-08 22:14:12 |
Andrew Starr-Bochicchio |
ubuntu-release-upgrader (Ubuntu): assignee |
|
Andrew Starr-Bochicchio (andrewsomething) |
|
| 2013-07-08 22:14:15 |
Andrew Starr-Bochicchio |
ubuntu-release-upgrader (Ubuntu): status |
New |
In Progress |
|
| 2013-07-08 22:14:20 |
Andrew Starr-Bochicchio |
ubuntu-release-upgrader (Ubuntu): importance |
Undecided |
Medium |
|
| 2013-07-08 22:50:31 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2013-07-09 19:03:03 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/ubuntu-release-upgrader |
|
| 2013-07-10 03:32:47 |
Adolfo Jayme Barrientos |
ubuntu-release-upgrader (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2013-07-10 19:42:16 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2013-07-11 21:00:13 |
Brian Murray |
description |
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been rewritten, when you are presented with the final upgrade prompt, and observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed you'll notice that /etc/apt/sources.list has a comment indicating that saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
|
| 2013-07-11 21:19:37 |
Brian Murray |
nominated for series |
|
Ubuntu Raring |
|
| 2013-07-11 21:19:37 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Raring) |
|
| 2013-07-11 21:19:47 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Raring): status |
New |
In Progress |
|
| 2013-07-11 21:19:49 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Raring): assignee |
|
Brian Murray (brian-murray) |
|
| 2013-07-11 21:19:51 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Raring): importance |
Undecided |
Medium |
|
| 2013-07-12 15:42:30 |
Adam Conrad |
ubuntu-release-upgrader (Ubuntu Raring): status |
In Progress |
Fix Committed |
|
| 2013-07-12 15:42:32 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2013-07-12 15:42:33 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2013-07-12 15:42:42 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2013-07-12 15:52:44 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/raring-proposed/ubuntu-release-upgrader |
|
| 2013-07-12 16:03:00 |
Brian Murray |
description |
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been rewritten, when you are presented with the final upgrade prompt, and observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed you'll notice that /etc/apt/sources.list has a comment indicating that saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d -p
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been rewritten, when you are presented with the final upgrade prompt, and observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed you'll notice that /etc/apt/sources.list has a comment indicating that saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
|
| 2013-07-12 16:49:23 |
Brian Murray |
description |
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d -p
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been rewritten, when you are presented with the final upgrade prompt, and observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed you'll notice that /etc/apt/sources.list has a comment indicating that saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been rewritten, when you are presented with the final upgrade prompt, and observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed you'll notice that /etc/apt/sources.list has a comment indicating that saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release. |
|
| 2013-07-12 16:52:59 |
Brian Murray |
tags |
verification-needed |
verification-done |
|
| 2013-07-17 18:35:18 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-07-17 18:35:20 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Raring): status |
Fix Committed |
Fix Released |
|
