[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#942494: apt / apt-get break on broken mirrors



Hi,

On Thu, Oct 17, 2019 at 10:06:52AM +0200, root wrote:
>      Tried to switch to an other mirror, but was again redirected to the
>      broken mirror.

First rule of good bugreports: Tell us everything! In the best case the
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.


>      apt shall drop this mirror, accessing the next best one until it
>      finds a non broken one.

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.


>      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.

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.


>      if this is already configurable, it should be the default
>      behaviour for apt / apt-get.

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

Attachment: signature.asc
Description: PGP signature


Reply to: