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#8226 - Pacman doesn't like it when multiple processes modify the cache

Attached to Project: Pacman
Opened by Jason Chu (jason) - Friday, 05 October 2007, 21:43 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 12:07 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.6
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:
If you mount bind pacman's cache inside a chroot and try to run multiple pacman updates at once, there could be cache collisions.

Steps to Reproduce:
1) Create chroot
2) mount -o bind /var/cache/pacman <path to chroot's pacman cache>
3) pacman -Syu on host system
4) pacman -Syu in chroot
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 12:07 GMT
Reason for closing:  Duplicate
Additional comments about closing:  FS#23501
Comment by Xavier (shining) - Thursday, 24 July 2008, 12:29 GMT
Allan : How can you even detect that is happening?
Dan : Not sure. Maybe worth leaving open.
me : maybe we need to lock the cache as well
Comment by Taylan Ulrich B. (taylanub) - Sunday, 06 February 2011, 16:05 GMT
I'd say not just "lock the cache as well", but do and only do lock what really should be locked at that moment.
One should be able to download files in one pacman (say with -w) and install packages with another (say with -U).
In fact one could have two pacmans download different files at the same time; we would need per-file locks (foo.pkg.tar.xz.lock in the cache dir).
I don't know if per-file locks would work in the db as well; would be awesome.
Comment by Allan McRae (Allan) - Sunday, 22 April 2012, 12:07 GMT
Closing this as a duplicate of a later bug report because the new one is more general.

Loading...