lucid upgrade to precise universe failed: Could not calculate the upgrade, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
ARCH: amd64
Error:
2012-09-19 00:09:13,411 DEBUG updateSourcesList()
2012-09-19 00:09:13,428 DEBUG rewriteSourcesL
2012-09-19 00:09:13,430 DEBUG examining: 'deb http://
2012-09-19 00:09:13,430 DEBUG entry 'deb http://
2012-09-19 00:09:13,430 DEBUG examining: 'deb http://
2012-09-19 00:09:13,430 DEBUG entry 'deb http://
2012-09-19 00:09:13,430 DEBUG examining: 'deb http://
2012-09-19 00:09:13,430 DEBUG entry 'deb http://
2012-09-19 00:09:13,433 DEBUG running doUpdate() (showErrors=True)
2012-09-19 00:09:17,616 DEBUG openCache()
2012-09-19 00:09:17,616 DEBUG failed to SystemUnLock() (E:Not locked)
2012-09-19 00:09:19,386 DEBUG /openCache(), new cache size 38602
2012-09-19 00:09:19,386 DEBUG needServerMode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2012-09-19 00:09:20,583 ERROR Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade:
E:Error, pkgProblemResol
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 update-manager' in a terminal. (None)
2012-09-19 00:09:20,583 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResol
2012-09-19 00:09:20,583 DEBUG abort called
2012-09-19 00:09:20,584 ERROR view.abort called
2012-09-19 00:09:20,584 DEBUG openCache()
2012-09-19 00:09:20,584 DEBUG failed to SystemUnLock() (E:Not locked)
2012-09-19 00:09:22,039 DEBUG /openCache(), new cache size 30590
2012-09-19 00:09:22,041 DEBUG enabling apt cron job
Changed in update-manager (Ubuntu): | |
status: | New → Incomplete |
importance: | Undecided → High |
Interesting! I can not find this bug today. Let's watch more days on the test.