Arch Linux User Repository

Thanks for pointing me in the right direction. Since I apply system updates when they become available, I'm not exactly sure why it was needed (possibly due to package caching) but yay -S ruby-hiera-eyaml --answerclean ALL solved the issue for me.

Arch released ruby 3.3.x to the main repos on 2024-10-01. This package was updated to 4.2.0 on 2024-11-03 (would have done it sooner, but I was away on vacation at the time). So anybody with version 4.2.0 of this package should have built it against ruby 3.3.x, unless it was installed without doing a full system update first (which is inadvisable for AUR packages).

In my case, I have had this package installed before Ruby was at version 3.3.x in Extra and I apply each system update within a few days of the release. Should something have caused the rebuild of this package as part of Arch's release of ruby 3.3.x last year?

If you just upgraded from ruby 3.2.x to 3.3.x then you will need to rebuild this package. That should have happened automatically as this package was updated to 4.2.0 following Arch's release of ruby 3.3.x last year.

Official ruby in Extra is now at 3.3.7-1 so running eyaml fails because it is looking for hiera-eyaml gem in /usr/lib/ruby/3.3.0 when it is in fact in /usr/lib/ruby/3.2.0:

/usr/lib/ruby/3.3.0/rubygems.rb:259:in `find_spec_for_exe': can't find gem hiera-eyaml 
(>= 0.a) with executable eyaml (Gem::GemNotFoundException)
    from /usr/lib/ruby/3.3.0/rubygems.rb:278:in `activate_bin_path'
    from /usr/bin/eyaml:25:in `<main>'

I did not realize the same ID could reference an updated key. The gpg --refresh command resolved it, thanks!

The key is not expired. The owner extended its validity back in January as you can see here. Hence, you need to update the copy in your keyring.

From what I can tell, the PKGBUILD references an expired key (see validpgpkeys below). I'm not an expert on building packages but it seems the PKGBUILD needs to be updated to fix this.

# Generated by gem2arch (https://github.com/anatol/gem2arch)
# Maintainer: Justin Dray <justin@dray.be>

_gemname=hiera-eyaml
pkgname=ruby-$_gemname
pkgver=4.1.0
pkgrel=1
pkgdesc='OpenSSL Encryption backend for Hiera'
arch=(any)
url='https://github.com/voxpupuli/hiera-eyaml'
license=(MIT)
depends=(ruby ruby-optimist ruby-highline)
makedepends=(git ruby-rdoc)
options=(!emptydirs)
source=(${_gemname}-${pkgver}::git+https://github.com/voxpupuli/hiera-eyaml?signed#tag=v${pkgver})
noextract=($_gemname-$pkgver.gem)
validpgpkeys=('C10B6298A584A5632E254DA304D659E6BF1C4CC0')

@krobe Looks like you need to update your keyring.

During update from previous version, the package was unable to be verified:

Parsing SRCINFO: ruby-hiera-eyaml
pub   rsa2048 2013-06-22 [SCA] [expired: 2024-01-17]
      C10B6298A584A5632E254DA304D659E6BF1C4CC0
uid           [ expired] Tim Meusel <tim@bastelfreak.de>
uid           [ expired] Tim Meusel <tim.meusel@online-mail.biz>