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#58960 - reboot /var/lib/pacman/db.lck removal

Attached to Project: Pacman
Opened by Ceriel Jacobs (cj1) - Sunday, 10 June 2018, 22:27 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 10 June 2018, 22:53 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I was expecting the 'reboot' command to delete /var/lib/pacman/db.lck

It doesn't.

Steps to reproduce:
# 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
# reboot
# 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
# rm -f /var/lib/pacman/db.lck
# pacman -Syu
:: Synchronizing package databases...
core is up to date
...

4.16.13-2-ARCH

Note: an improvement can already be to suggest the user to run the command: "rm -f /var/lib/pacman/db.lck"
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 10 June 2018, 22:53 GMT
Reason for closing:  Not a bug
Additional comments about closing:   FS#10946   FS#47188   FS#55975  and for more balanced approaches FS#9424 FS#23501

Loading...