That sould usually be in the error message. Something like "could not lock database" so in the future it might be helpfull to post the error message that way you can get better help from this list. Regards Schtiehve Am 2020-08-11 23:22, schrieb Jude DaShiell: > The hang up turned out to be /var/lib/pacman/db.lck. An upgrade got > disrupted so that file needed to be removed and that removal solved this > issue. If that happens again, I'll now know to look for and remove that > lock file in the future. > > On Tue, 11 Aug 2020, mar77i via arch-general wrote: > >> Date: Tue, 11 Aug 2020 15:13:56 >> From: mar77i via arch-general <arch-general@xxxxxxxxxxxxx> >> Reply-To: mar77i@xxxxxxxxxxxxx, >> General Discussion about Arch Linux <arch-general@xxxxxxxxxxxxx> >> To: General Discussion about Arch Linux <arch-general@xxxxxxxxxxxxx> >> Cc: mar77i@xxxxxxxxxxxxx >> Subject: Re: old archlinux instance repositories progress >> >> ??????? Original Message ??????? >> On Tuesday, August 11, 2020 8:21 PM, Jude DaShiell <jdashiel@xxxxxxxxx> wrote: >> >> > pacman -Sy archlinux-keyring returns error cannot update core among >> > other repositories and pacman -Ss archlinux-keyring shows the keyring to >> > be installed with date of 20200622-1 on it. >> > >> >> ...is this the same issue as on the other discussion thread? >> >> pacman -Ss shows the package as it's available in the repository. >> If you want to see the installed package, you have to type `pacman -Qs [packagename]`. >> >> cheers! >> mar77i >> >> >> Sent with ProtonMail Secure Email. >>
