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
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To Xavier (shining)
Architecture All
Severity Low
Priority Normal
Reported Version 3.2.2
Due in Version 3.3.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If 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
Comment by Xavier (shining) - Wednesday, 25 February 2009, 17:59 GMT
Fixed in git : http://projects.archlinux.org/?p=pacman.git;a=commitdiff;h=34e1413d756269dcd71a32dd5d2dbb263a943051
Comment by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 18:01 GMT
Quick patch so you get the idea: http://phraktured.net/unprivileged-ops-skip-db-registration-error.patch

If we don't need a transaction, these errors could just be warnings... not sure if this introduces other unforseen issues though
Comment by Aaron Griffin (phrakture) - Wednesday, 25 February 2009, 18:03 GMT
Much better - dir isn't created on the initialization of the DB, but only when we need it.

Hooray, I'll just close this then :)

Loading...