[pacman-dev] [PATCH] libalpm: Log URLs when retrying

[Vladimir Panteleev]

On Sun, 3 Oct 2021 at 23:22, Morgan Adamiec <morganamilo at archlinux.org> wrote:
> Still I seems to work with 404's too
>
> :: Retrieving packages...
>  filesystem-2018.1-2-x86_64 downloading...
> ---
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: url is
> http://mirror.bytemark.co.uk/archlinux/core/os/x86_64/filesystem-2018.1-2-x86_64.pkg.tar.xz
> ---
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: maxsize 7972
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: opened tempfile for
> download:
> /var/cache/pacman/pkg/filesystem-2018.1-2-x86_64.pkg.tar.xz.part (wb)
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: curl returned result 0
> from transfer
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: response code 404
> error: failed retrieving file 'filesystem-2018.1-2-x86_64.pkg.tar.xz'
> from mirror.bytemark.co.uk : The requested URL returned error: 404
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: tempfile found, attempting
> continuation from 0 bytes
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: curl returned result 0
> from transfer
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz: response code 200
> ---
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz.sig: url is
> https://ia601006.us.archive.org/6/items/archlinux_pkg_filesystem/filesystem-2018.1-2-x86_64.pkg.tar.xz.sig
> ---
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz.sig: maxsize 16384
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz.sig: opened tempfile for
> download:
> /var/cache/pacman/pkg/filesystem-2018.1-2-x86_64.pkg.tar.xz.sig.part (wb)
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz.sig: curl returned result 0
> from transfer
> debug: filesystem-2018.1-2-x86_64.pkg.tar.xz.sig: response code 200
> debug: curl_download_internal return code is 0
> checking keyring...


So, in your log, what URL did pacman download
filesystem-2018.1-2-x86_64.pkg.tar.xz from?

We could make an educated guess that it is from
https://ia601006.us.archive.org/6/items/archlinux_pkg_filesystem/filesystem-2018.1-2-x86_64.pkg.tar.xz
, because that's where it downloaded the signature from. This assumes
that pacman resumes downloading the signature from the mirror which
last successfully served a package file. However, that is never
explicitly stated in the log, and is what this patch aims to address.
Hope this helps. :)