Ubuntu
ubuntu-release-upgrader package

choosing to use own mirror also updates PPAs to new release and these may not exist

Bug #1306838 reported by Seth Arnold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Triaged
Low
Unassigned

Bug Description

This report is similar to 1244050 -- but that appeared to be specific to extras.ubuntu.com. My upgrade failed due to ppa.launchpad.net:

Error during update$

A problem occurred during the update. This is usually some sort of$
network problem, please check your network connection and retry.$

W:Failed to fetch$
http://ppa.launchpad.net/pitti/sru-test/ubuntu/dists/trusty/main/binary-amd64/Packages$
404 Not Found$
, W:Failed to fetch$
http://ppa.launchpad.net/pitti/sru-test/ubuntu/dists/trusty/main/binary-i386/Packages$
404 Not Found$
, E:Some index files failed to download. They have been ignored, or$
old ones used instead.$

Restoring original system state

While this looks simple enough to fix by hand, I was surprised the tool didn't fix it for me.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.5
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashDB: ubuntu
Date: Fri Apr 11 16:31:12 2014
InstallationDate: Installed on 2012-10-18 (540 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to saucy on 2014-04-11 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2014-04-11 16:18:10.509996
 Log time: 2014-04-11 16:18:42.192534
 Log time: 2014-04-11 16:19:43.913596

Revision history for this message
Seth Arnold (seth-arnold) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Heh, this is wrong by a lot:
 UpgradeStatus: Upgraded to saucy on 2014-04-11 (0 days ago)

Apparently do-release-upgrade destroys the actual upgrade time when it fails.

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

It's actually the UpgradeStatus check that is a poor guess.

    log = '/var/log/dist-upgrade/main.log'
    if os.path.exists(log):
        mtime = os.stat(log).st_mtime
        human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
        delta = time.time() - mtime

        # Would be nice if this also showed which release was originally installed
        report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % (release_codename, human_mtime, delta / 86400)

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

Generally, the release upgrader disables things like PPAs but because you said Yes to the no valid mirror found questions it just auto-updated everything to trusty.

"No valid mirror found

While scanning your repository information no mirror entry for the
upgrade was found. This can happen if you run an internal mirror or
if the mirror information is out of date.

Do you want to rewrite your 'sources.list' file anyway? If you choose
'Yes' here it will update all 'saucy' to 'trusty' entries.
If you select 'No' the upgrade will cancel.

Continue [yN] y"

summary: - do-release-upgrade fails to upgrade saucy to trusty
+ choosing to use own mirror also updates PPAs to new release and these
+ may not exist
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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