unable to upgrade from lucid to precise

Bug #1602332 reported by GSR kashyap
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

have done upgrade in 10.04(lucid) by issuing command do-release-upgrade with prompt=LTS
after some time got the error with option to type x to terminate and r to resurrect window
===========
An unresolvable problem occurred while calculating the upgrade:
E:Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.

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.

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Building data structures... Done
=== Command detached from window (Tue Jul 12 21:31:26 2016) ===
=== Command terminated with exit status 1 (Tue Jul 12 21:31:26 2016) ===
========================

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.134.7
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Tue Jul 12 21:27:17 2016
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: update-manager

Revision history for this message
GSR kashyap (gsr-kashyap) wrote :
tags: added: dist-upgrade
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin (martin-meier) wrote :

Why would you deliberately punish administrators that take over a rotten infrastructure and not allow them to update?
Can't you at least maintain an extra Repository containing the old stuff so one could patch his sources.list and migrate machines rather than completely setting up new ones?

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.