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#58965 - error: "(unable to lock database)" for each repo; path missing in output = usability bug

Attached to Project: Pacman
Opened by Ceriel Jacobs (cj1) - Monday, 11 June 2018, 09:26 GMT
Task Type Bug Report
Category Backend/Core
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Summary and Info:
# 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 update archlinuxfr (unable to lock database)
error: failed to synchronize all databases
#

Steps to Reproduce:
1. Make btrfs crash.
2. Run `pacman -Syu`

I understand from  FS#55975  that the lock file should not be automatically deleted (f.e. on reboot).

I also know that this system crashed due to some btrfs error. Usually the best approach for those kind of issues is to stay (kernel) updated.

In  FS#55975  pacman outputs:
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck

Such a handy message is missing in the above error case where all locks fail.
For usability at least tell once which path the "(unable to lock database)" is referring to.

In other words, the issue is that pacman does not tell me the path (/var/lib/pacman/db.lck), in contrary to error messages as shown in  FS#47188  and  FS#10946 .
This task depends upon

Loading...