[Bug 1291262] Re: do-release-upgrade gives up too easily on 404 error

[Rolf Leggewie]

I reran the command today in X instead of from the VT and I saw some
error about "no known mirror".  I thought of "proxy" but what is meant
is "official Ubuntu repository", I guess.  My deb lines look like this

deb http://u.cname.leggewie.org/ubuntu precise main restricted universe
multiverse

u.cname.leggewie.org is a CNAME for jp.archive.ubuntu.com.  I do this so
that I can have u.cname.leggewie.org be that CNAME "out in the wild" but
have it point to my local apt-cacher-ng repository automatically by the
local DNS in my home LAN.

Suggested fixes:
1) Try to resolve to an IP level or otherwise determine if the host is an official Ubuntu Mirror
2) at least improve the wording from "No known mirror" to something along the lines of "None of your repositories in sources.list were recognized as official Ubuntu mirrors"

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

Title:
  do-release-upgrade gives up too easily on 404 error

Status in “update-manager” package in Ubuntu:
  New

Bug description:
  The do-release-upgrade command in precise gives up too easily when
  some files fail to download.

  $ sudo do-release-upgrade -d
  [...]
  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/r0lf/stable/ubuntu/dists/trusty/main/binary-i386/Packages 
  404 Not Found 
  , W:Failed to fetch http://$some-private-mirror/debs/./Packages 
  403 Forbidden 
  , E:Some index files failed to download. They have been ignored, or 
  old ones used instead. 

  The program then aborts when it should simply keep going.  For your
  better understanding the 403 error results from the fact that I allow
  access to that mirror only from certain trusted IP numbers.  The 404
  from the PPA stems from the fact that I haven't yet published any
  trusty packages in that PPA.  Neither of the two should be a problem
  for an upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1291262/+subscriptions