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