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#13487 - unprivileged ops fail when new repos are added
Attached to Project:
Pacman
Opened by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 17:54 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 18:03 GMT
Opened by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 17:54 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 18:03 GMT
|
DetailsIf an invalid or missing repo is added to pacman.conf, user-based operations fail at the "registering the database" step.
Steps to Reproduce: * Add a bunk section to pacman.conf, like: [foobarbaz] Server = file:///zomg/whatever This does not need to be local, nor does it need to be invalid. * Run an unprivileged operation *WITHOUT* sudo $ pacman -Si bash error: could not register 'foobarbaz' database (unexpected system error) This was noticed because makepkg's deptest fails if you add a new repo. Suggestion: If not running as root, consider DB registration errors harmless. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Wednesday, 25 February 2009, 18:03 GMT
Reason for closing: Fixed
Additional comments about closing: In git
Wednesday, 25 February 2009, 18:03 GMT
Reason for closing: Fixed
Additional comments about closing: In git
If we don't need a transaction, these errors could just be warnings... not sure if this introduces other unforseen issues though
Hooray, I'll just close this then :)