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#19189 - add nodelete db archive option to pacman
Attached to Project:
Pacman
Opened by Caleb Cushing (xenoterracide) - Wednesday, 21 April 2010, 03:45 GMT
Last edited by Dan McGee (toofishes) - Thursday, 08 July 2010, 05:15 GMT
Opened by Caleb Cushing (xenoterracide) - Wednesday, 21 April 2010, 03:45 GMT
Last edited by Dan McGee (toofishes) - Thursday, 08 July 2010, 05:15 GMT
|
Detailswhen pacman downloads a db archive it extracts and removes (or extracts in a way that doesn't preserve). For clarity I'm talking like core.db.tar.gz. This is ok with default pacman setup because somehow pacman has another timestamp (or something) to check. This doesn't work if you change the download manager. I switched to wget because I need download throttling but now it will download all these files whether an update is available or not. Preserving the files would allow the timestamp to be checked on the remote.
|
This task depends upon
Closed by Dan McGee (toofishes)
Thursday, 08 July 2010, 05:15 GMT
Reason for closing: Implemented
Additional comments about closing: DB files are kept as of 3.4, see /var/lib/pacman/
Thursday, 08 July 2010, 05:15 GMT
Reason for closing: Implemented
Additional comments about closing: DB files are kept as of 3.4, see /var/lib/pacman/
Comment by Allan McRae (Allan) -
Wednesday, 21 April 2010, 04:57 GMT
- Field changed: Attached to Project (Community Packages → Pacman)
Moving to the correct section... Community packages is not even close!