Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#65366 - Using ALA for 2015-2017. Some packages keep coming up missing (HTTP error 404)

Attached to Project: Arch Linux
Opened by hidden (goodboy) - Tuesday, 04 February 2020, 11:26 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 07 May 2023, 09:14 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version 5.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Summary and Info:
I'm using ALA ( to recover an old arch installation (presumably from 2016)
(see also my original post here

But a 404 seems to happen regularly for two packages preventing the installation to complete successfully.

@WorMzy from the thread mentioned above suggested this
it seems the 'automatic redirection' that's meant to be in place isn't working. You might want to open a bug about that.

The 2 packages are:
P1 is missing in 2015
P2 is missing end of 2015, end plus mid 2016 and start of 2017

P1: failed retrieving file 'lib32-glibc-2.22-3.1-x86_64.pkg.tar.xz' from : The requested URL returned error: 404
P2: failed retrieving file 'r-3.3.2-2-x86_64.pkg.tar.xz' from : The requested URL returned error: 404

Steps to Reproduce:

Follow steps as in
Modify /etc/pacman.conf and /etc/pacman.d/mirrorlist accordingly.
However no guarantees made as the outcome may depend on the particular state of my machine.

This task depends upon

Closed by  Florian Pritz (bluewind)
Sunday, 07 May 2023, 09:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems like this was fixed long ago.
Comment by Florian Pritz (bluewind) - Friday, 07 February 2020, 13:13 GMT
The redirect regex didn't allow single-character pkgnames or pkgrels with dots in them. This should be fixed now. Can you try again?