distro upgrade under crouton chroot session

Bug #1537576 reported by Luke Brumfield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

Running Ubuntu 14.04 (Trusty) under crouton on a Chromebook Pixel(2015)

Edited the file /etc/update-manager/release-upgrades

replaced Prompt=lts by Prompt=normal

sudo do-release-upgrade
This was the output:

Checking for a new Ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1214 kB]
Fetched 1214 kB in 0s (0 B/s)
authenticate 'vivid.tar.gz' against 'vivid.tar.gz.gpg'
extracting 'vivid.tar.gz'
...
...
...
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Building data structures... Done

Calculating the changes

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version of Ubuntu
* Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.

Expected an upgrade to "Vivid", changes were rolled back. Only packages not installed from repos are Google Chrome and Dropbox.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.8
Uname: Linux 3.14.0 x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashDB: ubuntu
Date: Sun Jan 24 19:15:03 2016
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to trusty on 2016-01-25 (0 days ago)
mtime.conffile..etc.update.manager.release.upgrades: 2016-01-24T19:13:30.431739

Revision history for this message
Luke Brumfield (lukebrumfield) wrote :
Revision history for this message
Luke Brumfield (lukebrumfield) wrote :

It seems like this isn't the only bug reported upgrading Trusty to Vivid. My unique difference is the chroot session and being on the chromebook. Is there anyone having an issue going from Trusty to WIly? I didn't have lts as the option, and it did not suggest Utopic. I would imagine in that case it would go for WIly (the latest release).

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1534374, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.