Closed felikcat closed 2 years ago
Well, a year and a half ago when I created the refind-btrfs package on the AUR this issue wasn't present. It actually appeared fairly recently when the maintainer (Luis Martinez) added the "validpgpkeys" to the PKGBUILD which obviously defines and invalid (expired?) key. Why did this person make that change? I honestly have no idea.
As far as a potential refind-btrfs-bin package goes I don't think it's that easy to accomplish with Python packages but then again I'm not really that experienced with the PKGBUILD file format.
There is a prebuilt refind-btrfs package found in Chaotic-AUR repository (created by the Garuda Linux team, AFAIK) and also the python-pid package. Maybe that would solve the issues with the GPG key? It's a bit overkill to include a whole repo for just this one package but it might work.
Alternatively, I could migrate this dependency to another one which performs the same required checks but I'm currently unable to find it.
EDIT: Feel free to create a "bin" version of the default package, if you want to. I don't mind, of course. :+1:
When I installed refind-btrfs I didn't face this issue, so I assume this can be closed?
When I installed refind-btrfs I didn't face this issue, so I assume this can be closed?
Sure, it seems that the PGP fingerprint issues have been resolved upstream.
AUR helper: Paru Workaround: Run
gpg --recv-keys 13FFEEE3DF809D320053C587D6E95F20305701A1
before installingrefind-btrfs
.refind-btrfs
pulls in python-pid as a dependency, which the maintainer of is using an expired PGP key.If there were
refind-btrfs-bin
, this issue would have been prevented.