Pacman

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.
Tasklist

FS#9510 - pacman misses /var/lib/pacman directory

Attached to Project: Pacman
Opened by Tobias Powalowski (tpowa) - Sunday, 10 February 2008, 08:25 GMT
Last edited by Dan McGee (toofishes) - Thursday, 20 January 2011, 21:47 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.1.1
Due in Version 3.5.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:


Steps to Reproduce:
http://bugs.archlinux.org/task/9494

it seems pacman misses /var/lib/pacman creation.
it's now fixed in setup and quickinst to prevent this but fixing upstream would be a good idea too :)
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 20 January 2011, 21:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1ff8118212cf566607c61e2f340dc3064c67c2ac
Comment by Dan McGee (toofishes) - Tuesday, 12 February 2008, 02:24 GMT
I took a quick look at this tonight. Long and short is at this point, I'd rather not add the hackish way of doing this as was done before.

Path creation in pacman/libalpm is rather willy-nilly, and a lot of times it is done regardless of whether you are root, etc. At the moment, you could remove the check that ensures that the dbpath already exists, but I would rather keep it in there as removing it could expose other flaws of how pacman creates and manages databases, and tries to keep all permissions and ownership in check.
Comment by Xavier (shining) - Tuesday, 12 February 2008, 15:27 GMT
Why do we create other directories, but not that one? For example, we create the tmp dir and the cache dir when they don't exist.
Also, the code for creating the path to local db or sync db (so /var/lib/pacman/ is included) still exists, as I mentioned previously :
http://archlinux.org/pipermail/pacman-dev/2008-January/010834.html

It doesn't matter whether you are root or not. If we need the /var/lib/pacman path, we create it. If the user doesn't have enough privileges,
then the creation will fail, and pacman as well. I think that's fine, isn't it?

I have a feeling the real problem might be somewhere else (like pacman doing stuff when it doesn't really need to).

Loading...