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#65234 - pacman should show pacman lock file location when locked

Attached to Project: Pacman
Opened by Daniel YC Lin (dlin) - Tuesday, 21 January 2020, 23:55 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 22 January 2020, 00:08 GMT
Task Type Bug Report
Category Output
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 5
Private No

Details

Description:
pacman should show pacman lock file location when locked.

$ sudo pacman -Syu :(
:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to synchronize all databases

I don't know what's to do, if I can NOT access the internet.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Comment by Eli Schwartz (eschwartz) - Wednesday, 22 January 2020, 00:07 GMT
  • Field changed: Attached to Project (Arch Linux → Pacman)
Moving to the dedicated pacman project, as it's about pacman expected behavior, not the way it is packaged in arch.
Comment by gcb (gcb) - Monday, 07 September 2020, 20:40 GMT
had just filled a duplicate[1] (sorry for my low search skills) and after downloading sources to try to just update the manpage, a quick grep showed the information. I (and the reporter here) just happened to trigger a code path that does not.

Downloading fresh package database (-y, --refresh) will not show the information, as show on the original report above. However not updating the package database will:

$ sudo pacman -Su
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck

(and again, still think this file should live in `/run/lock`)


[1] https://bugs.archlinux.org/task/67847
Comment by janek (xeruf) - Tuesday, 30 August 2022, 21:13 GMT
Agree, had to go to https://wiki.archlinux.org/title/Pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error just now to find it

Loading...