| commit | fe659153d5971e41b7483bb40c31cd40f58f9d9c | |
| author | Dan McGee <dan@archlinux.org> | |
| Mon, 20 Feb 2012 05:24:26 +0000 (19 23:24 -0600) | ||
| committer | Dan McGee <dan@archlinux.org> | |
| Mon, 20 Feb 2012 05:24:26 +0000 (19 23:24 -0600) | ||
| tree | ac5adaff9ed0542e28acab67f9c95da9984dd889 | treesnapshot (tar.gz zip) |
| parent | 4899b5bd864919830fe4ce5786d37a00ab5a0da3 | commitdiff |
Give better error messages on database locking failures
This was noted when trying to perform an operation on a pacman database
on a read-only file system. Print the actual underlying errno string,
and only show the "you can remove" message if the lock file actually
exists.
Before:
$ pacman -Su
error: failed to init transaction (unable to lock database)
if you're sure a package manager is not already
running, you can remove /e/db.lck
After:
$ pacman -Su
error: failed to init transaction (unable to lock database)
error: could not lock database: Read-only file system
Signed-off-by: Dan McGee <dan@archlinux.org>
This was noted when trying to perform an operation on a pacman database
on a read-only file system. Print the actual underlying errno string,
and only show the "you can remove" message if the lock file actually
exists.
Before:
$ pacman -Su
error: failed to init transaction (unable to lock database)
if you're sure a package manager is not already
running, you can remove /e/db.lck
After:
$ pacman -Su
error: failed to init transaction (unable to lock database)
error: could not lock database: Read-only file system
Signed-off-by: Dan McGee <dan@archlinux.org>
| src/pacman/util.c | diffblobblamehistory |