Arch Linux User Repository

yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay

pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.

nerd-fonts-fantasque-sans-mono package and other packages in the nerd family including fira etc, are no longer verifying correctly.

❯ yay -S nerd-fonts-fantasque-sans-mono
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  nerd-fonts-fantasque-sans-mono-2.1.0-1

  1 nerd-fonts-fantasque-sans-mono           (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: PKGBUILD up to date, Skipping (1/1): nerd-fonts-fantasque-sans-mono
  1 nerd-fonts-fantasque-sans-mono           (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: Parsing SRCINFO (1/1): nerd-fonts-fantasque-sans-mono

==> Making package: nerd-fonts-fantasque-sans-mono 2.1.0-1 (Sun 23 Feb 2020 08:27:56 PM IST)
==> Retrieving sources...
  -> Found FantasqueSansMono.zip
  -> Found LICENSE
==> Validating source files with sha1sums...
    FantasqueSansMono.zip ... FAILED
    LICENSE ... Passed
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: nerd-fonts-fantasque-sans-mono

The same package is installed without problems using the aura package manager

❯ sudo aura -A nerd-fonts-fantasque-sans-mono
[sudo] password for aniketd:
aura >>= Determining dependencies...
aura >>= AUR Packages:
nerd-fonts-fantasque-sans-mono
aura >>= Continue? [Y/n]
loading packages...
warning: nerd-fonts-fantasque-sans-mono-2.1.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) nerd-fonts-fantasque-sans-mono-2.1.0-1

Total Installed Size:  7.55 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                                                                                  [########################################################################################] 100%
(1/1) checking package integrity                                                                                                                [########################################################################################] 100%
(1/1) loading package files                                                                                                                     [########################################################################################] 100%
(1/1) checking for file conflicts                                                                                                               [########################################################################################] 100%
(1/1) checking available disk space                                                                                                             [########################################################################################] 100%
:: Processing package changes...
(1/1) reinstalling nerd-fonts-fantasque-sans-mono                                                                                               [########################################################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating fontconfig cache...
(3/4) Updating 32-bit fontconfig cache...
(4/4) Updating X fontdir indices...

I am not able to upgrade development packages, shows cannot rm permission denied when trying to remove cache of it

@hugo you need to install base-devel. This is assumed hence make is not a dependency.

"make" is missing on makedepends, got an error on a fresh install.

On-topic: I've noticed with other packages yay is importing a single GPG key just fine. Could the problem be multiple GPG keys?

Off-topic: @fightcookie; maybe walk the talk? How is you bulky comment not off-topic and without new information? The way I see it is this comment section is the place where end users help each other out to get a particular software working. I can't always tell the difference between a packaging or a software bug.

@MindfulConsumer I am subscribed to comments to this aur package, so off-topic comments are kind of distracting and wasting my time (I'm surely not the only one subscribed). Also, these kinds of comments led @jguer to disable comments to this package (according to their pinned message), which is unfortunate I think for support of the package since they are the maintainer currently! It is totally ok of you to boycott GitHub, but please consider only posting packaging related bugs here, to keep the comments readable by everyone interested without being overwhelmed by off topic things :)

@swm and @jguer: sadly I had to conclude github should be on my boycott list, I refuse to create an account there. I can manually import the gpg keys without problems with "gpg --recv-keys <key>" and continue installing.

@iTanguy and @MindfulConsumer: Seeing jguer's pinned comment from 2019-04-16, you should probably go to the upstream issue tracker, see if the problem has already been reported there and do so if not.

@MindfulConsumer: yay uses sudo which may ask for your user password to execute actions as root (if not already done so in the last x minutes, depending on your sudo configuration). Otherwise it should not ask for passwords. The "permission denied" error you see is from gpg trying to get the keys from a server, which has nothing to do with your local user accounts. (I think yay's usage of gpg will also import the keys to your own gpg keyring, which does not belong to root and does not need sudo usage.) An issue with the same gpg error message has been reported upstream, which might help you solve your problem: https://github.com/Jguer/yay/issues/656

I'm pretty sure yay is supposed to ask me for a password here:

 :: Parsing SRCINFO (1/1): palemoon-bin

 ==> PGP keys need importing:
 -> 439F46F42C6AE3D23CF52E70865E6C87C65285EC, required by: palemoon-bin
-> 3DAD8CD107197488D2A2A0BD40481E7B8FCF9CEC, required by: palemoon-bin
==> Import? [Y/n] y
:: Importing keys with gpg......
gpg: keyserver receive failed: Permission denied
==> Error: Problem importing keys

License information should be more accurate. I am no packaging expert nor lawyer, just a user who cares about FOSS.

1. GPL license version used is GLP v3.0, for License should be set to GPL3
2. The "go-alpm" module is under MIT license, so it should be added to the "License" field (becoming "GPL3 MIT")
3. the MIT license file should be added to /usr/share/licenses/yay/