Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.

FS#71352 - Make server_error_limit configurable

Attached to Project: Pacman
Opened by Peter (paulypeter) - Thursday, 24 June 2021, 12:30 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 24 June 2021, 17:32 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


As of pacman 6.0.0, a mirror server is skipped after 3 failed download attempts. I would like to change this setting.

I think this would have to be changed in lib/libalpm/dload.c, l. 63.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 24 June 2021, 17:32 GMT
Reason for closing:  Won't implement
Additional comments about closing:  FS#23407 is the right way to go here
Comment by Eli Schwartz (eschwartz) - Thursday, 24 June 2021, 12:34 GMT
  • Field changed: Attached to Project (Arch Linux → Pacman)
  • Field changed: Summary ([pacman] Make server_error_limit configurable → Make server_error_limit configurable)
Moved to the pacman bugtracker.
Comment by Eli Schwartz (eschwartz) - Thursday, 24 June 2021, 12:36 GMT

What use case is enabled by letting this be changed? When is 3 failed downloads not a sign that the server is out of order and shouldn't be used?
Comment by Peter (paulypeter) - Thursday, 24 June 2021, 12:55 GMT
My use case is using multiple PCs on a limited bandwidth. Before v6.0.0, I downloaded new packages once on one machine and then started an http server on that machine, sharing /var/cache/pacman/pkg. The *.db files are not included in this directory, so when running "pacman -Syu" on another machine where the first one is listed as a host, it obviously fails on the db files. The rest of the files is still there though.
Comment by Christian Hesse (eworm) - Thursday, 24 June 2021, 13:12 GMT
This could as well be fixed with implementing CacheServer as described in FS#23407...
Comment by Eli Schwartz (eschwartz) - Thursday, 24 June 2021, 14:07 GMT
See, understanding the use case is important. :)

You do *not* want remote mirrors to keep being tried after 3 failures. But your local mirror should be tried infinite times so you want to disable the error limit entirely.

You don't want this configurable after all.
Comment by Peter (paulypeter) - Thursday, 24 June 2021, 16:27 GMT
I guess you're right, I want it disable-able. :D

Although the other mentioned implementation would be a great idea, as well.