[Bug 1306838] Re: do-release-upgrade fails to upgrade saucy to trusty

[Brian Murray]

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 changed:

- 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

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: New => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Medium => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1306838

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

Status in “ubuntu-release-upgrader” package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1306838/+subscriptions