| Git Clone URL: | https://aur.archlinux.org/eid-mw.git (read-only, click to copy) |
|---|---|
| Package Base: | eid-mw |
| Description: | The Belgian e-ID (electronic identity card) viewer and Firefox extension |
| Upstream URL: | https://eid.belgium.be/ |
| Licenses: | LGPL-3.0-only |
| Submitter: | gromit |
| Maintainer: | lquidfire |
| Last Packager: | lquidfire |
| Votes: | 3 |
| Popularity: | 0.94 |
| First Submitted: | 2024-03-20 15:19 (UTC) |
| Last Updated: | 2024-10-26 12:18 (UTC) |
Thanks @lquidfire.
Those procedures didn't work for me initially; but based on the error messages I found this info regarding firewalls. I'm on a mobile connection abroad and had no idea, but there may indeed be some firewall, because gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D95426E309C0492990D8E8E2824A5E0010A04D46 (note the :80) did the trick to import the key.
By now, eid-mw is up and running :-) Many thanks for AURing it!
Hi, trying to install this from Pamac on Manjaro. I get the below errors about PGP key errors, which I know little about. Can someone help me address this? Thanks!
Cloning eid-mw build files...
Generating eid-mw information...
Checking eid-mw dependencies...
Resolving dependencies...
Checking inter-conflicts...
key D95426E309C0492990D8E8E2824A5E0010A04D46 could not be imported
Building eid-mw...
==> Making package: eid-mw 5.1.19-1 (Fri 16 Aug 2024 10:30:10 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found eid-mw-5.1.19-v5.1.19.tar.gz
-> Found eid-mw-5.1.19-v5.1.19.tar.gz.asc
==> Validating source files with sha256sums...
eid-mw-5.1.19-v5.1.19.tar.gz ... Passed
eid-mw-5.1.19-v5.1.19.tar.gz.asc ... Skipped
==> Verifying source file signatures with gpg...
eid-mw-5.1.19-v5.1.19.tar.gz ... FAILED (unknown public key 824A5E0010A04D46)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build eid-mw
A tool that can help with this is the package extra/rebuild-detector. It has a Pacman hook that will notify you when a library update breaks any of your local repo software. You then know that that software has to be rebuilt.
@desaparecido thanks, rebuilding did the trick. And yes, libassuan changed name from so.0 to so.9 with the update.
@libertepourmoi did you try to rebuild the package ? if you have new shared library name (like seems in this case), is needed to build again to link with new library name.
with the same libassuan package version I have this :
/usr/lib/libassuan.so /usr/lib/libassuan.so.9 /usr/lib/libassuan.so.9.0.0
After updating libassuan to version 3.0.0-1 I can't use this anymore. E.g. when running eid-viewer, I get "eid-viewer: error while loading shared libraries: libassuan.so.0: cannot open shared object file: No such file or directory"
thks to explain it simply and accurate.
it should be pinned
@cherkaba: See the link in the PKGBUILD.
The 'release' packages are signed by the key you mention (and found here: https://eid.belgium.be/en/linux-eid-software-installation).
However, sources are not signed with that key, but with the one mentioned here: https://files.eid.belgium.be/info.html (as explained in the PKGBUILD).
I hope this helps!
please why on the website the official gpg key => B37D 9040 098C 3DEE E00F 6D08 A357 43EA 6773 D225
but this pkg download another one => D95426E309C0492990D8E8E2824A5E0010A04D46
???
Pinned Comments
lquidfire commented on 2024-06-04 20:16 (UTC)
@cherkaba: See the link in the PKGBUILD.
The 'release' packages are signed by the key you mention (and found here: https://eid.belgium.be/en/linux-eid-software-installation).
However, sources are not signed with that key, but with the one mentioned here: https://files.eid.belgium.be/info.html (as explained in the PKGBUILD).
I hope this helps!