You are not logged in.
Pages: 1
Hello All!
I was following this German site to Yaourt and installed
spotify through it from the AUR. After that I wanted to update with pacman -Syu and that is where problems occured.
Even after restart it says that certain packages can't be locked and if I'm sure that there is no packagemanager running
I should delete db.lck in /var/lib/pacman (see below).
I use ps -ef | grep pacman to find the process id and kill it but it dynamically changes the process ID (can that be?)
and with that I'm unable to kill it ( e.g. XpYunkr 1700 1159 0 13:53 pts/0 00:00:00 grep pacman
and a second later XpYunkr 1703 1159 0 13:53 pts/0 00:00:00 grep pacman).
I'm not sure how safe it is or if Yaourt should even be used at all anymore because in the English wiki it
doesn't seem to rate very highly when looking at the comparison table in Table.
How should I proceed? Get rid of Yaourt again or delete db.lck? How would I directly delete the process
with a combined command of ps and kill a specific process before it can change its ID.
Here is is the error message:
:: 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 any databases
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
Hope I'm not too verbose.
Nice Sunday to you.
Greetings,
XpYunkr
Last edited by XpYunkr (2018-02-05 11:13:18)
Offline
The question is what happened that interrupted a pacman process so that the file remained, this has nothing to do with yaourt per se, did you abort a running process via some unclean method like shutting down?
You might want to share a pacman.log . Also what you mistake as a continuously elusive pacman process, is the grep process you invoke, which of course is a new process for each invocation, so nothing to worry there. (It might also help to know there's a pgrep command which is somewhat better suited for this task and will also specifically omit itself, to prevent this kind of confusion)
FWIW in this particular instance I'd just remove the lock file and run an update, maybe also a
pacman -Qkkto check if nothing is corrupted.
And use [ code ] tags for pasting output not quote tags.
Last edited by V1del (2018-02-04 13:47:01)
Offline
Thanks for the quick reply.
What should I look out for
running pacman -Qkk? After deleting db.lck and updating there are three warnings showing up multiple times
running pacman -Qkk:
warning: linux: /usr/lib/modules/4.14.15-1-ARCH/modules.alias (Modification time mismatch)warning: systemd: /usr/share/polkit-1/rules.d/systemd-networkd.rules (Permission denied)warning: vlc: /usr/lib/vlc/plugins/plugins.dat (Size mismatch)but no errors.
I really don't understand where the permission denied comes from.
And should I get rid of yaourt or is it ok to use?
Otherwise thanks for the help and I will mark it as solved.
Offline
Those warnings seem normal: the first 2 definitely are fine. The third I'm not familiar with as I don't use vlc, but it looks normal.
The permission denied message is just due to running that pacman command as a regular user (which I'd say is the right way to do it) and not having access to that file/path. If you run `pacman -Qkk` as root (which is safe, but mostly pointless) you will see that this permission denied error is gone.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Of course. Thanks a lot then!
Offline
Pages: 1