Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#14390 - More helpful error message when no mirrors set in Pacman
Attached to Project:
Pacman
Opened by Luca Spiller (thelucster) - Sunday, 19 April 2009, 22:38 GMT
Last edited by Dan McGee (toofishes) - Saturday, 11 July 2009, 23:26 GMT
Opened by Luca Spiller (thelucster) - Sunday, 19 April 2009, 22:38 GMT
Last edited by Dan McGee (toofishes) - Saturday, 11 July 2009, 23:26 GMT
|
DetailsDescription:
If trying to perform a system upgrade when no mirrors are set, it fails without giving a useful error message (Unexpected Error). In Arch default mirrors are not set, where as in most other distros they are, as such setting mirrors is an easy step to miss. I would suggest a check is made to ensure that mirrors are set, and if not a more helpful error message given. Steps to reproduce: 1. Comment out entries in /etc/pacman.d/mirrorlist 2. $ pacman -Syu :: Synchronising package databases... error: failed to update core (unexpected error) error: failed to update extra (unexpected error) error: failed to update community (unexpected error) :: Starting full system upgrade... local database is up to date |
This task depends upon
Closed by Dan McGee (toofishes)
Saturday, 11 July 2009, 23:26 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in git by commit aa579b843899ccba093f83faa942599ce1110c24
Saturday, 11 July 2009, 23:26 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in git by commit aa579b843899ccba093f83faa942599ce1110c24
Comment by Artiom Molchanov (artiom) -
Thursday, 21 May 2009, 10:52 GMT
I confirm the problem. Without this bug report I will be not able to detect the problem.