release upgrade from 18.04 to 18.10 cannot calculate upgrade, no reason given
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
do-release-upgrade cannot calculate the upgrade, offers no useful insight as to why, and provides no way to see the actual underlying error.
====
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://
Hit http://
Hit http://
Hit http://
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Updating repository information
Hit http://
Hit http://
Hit http://
Hit http://
Fetched 0 B in 0s (0 B/s)
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... 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-
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command terminated with exit status 1 (Thu Oct 18 21:53:52 2018) ===
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Thu Oct 18 21:49:00 2018
InstallationDate: Installed on 2015-12-17 (1036 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitec
SourcePackage: ubuntu-
UpgradeStatus: Upgraded to bionic on 2018-10-19 (0 days ago)
mtime.conffile.
tags: | added: bionic2cosmic |
Status changed to 'Confirmed' because the bug affects multiple users.