Dear Maintainer,

   * What led up to the situation?
     Just tried to upgrade to latest available packages using
     "apt update".

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Tried to switch to an other mirror, but was again redirected to the
     broken mirror.

   * What was the outcome of this action?
     Unable to upgrade to latest packages.
     Unable to install newer packages.

   * What outcome did you expect instead?
     apt shall drop this mirror, accessing the next best one until it
     finds a non broken one.
     If this list is exausted apt / apt-get shall print a warning and
     just ignore this mirror, but go on working, installing what it
     available for upgrades.
     if this is already configurable, it should be the default
     behaviour for apt / apt-get.

Hi,
output you got.

I have no idea what you consider a broken mirror as "broken" is a word
applied to many many different states and only a small set can be worked
around by apt – and most of them are without you ever knowing.

You have an http source, so that defines a single mirror – aka the list
is quickly exhausted. Except that this single address might be backed by
multiple IPs and/or SRV records where apt is falling back if they are
broken in the more formal sense of not reachable and stuff.

Not sure what you mean here as apt reports an error about the failed
source, but continues with other sources just fine and will pull data
and packages from them just fine.

You can have a look at the apt-transport-mirror manpage and use that
feature to declare a list of multiple mirrors for a source in which apt
will "happily" fallback even in slightly less broken cases like missing
files on the mirror which should be there – but this case is not that
common if you aren't using a mirror who is by design not shipping all
files (called partial mirrors).

Also, too new for being used by default by everyone for now I would say.


Best regards

David Kalnischkies