Package Details: eid-mw 5.1.21-1

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.67
First Submitted: 2024-03-20 15:19 (UTC)
Last Updated: 2024-11-03 14:46 (UTC)

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!

Latest Comments

« First ‹ Previous 1 2

lquidfire commented on 2024-05-31 15:17 (UTC)

Thank you, @arielzn. I have added the link and changed the explanation - I hope that it is more easy to understand now. Also upgraded to the next version.

arielzn commented on 2024-05-29 16:24 (UTC) (edited on 2024-05-29 16:29 (UTC) by arielzn)

Would you mind adding on the PKGBUILD comments about gpg signatures a reference to this link https://files.eid.belgium.be/info.html ?

On that link is "officially" mentioned on the eid website the key we actually need to import to validate the sources.

Even if the text talks about candidate deb/rpm builds, it can be clarified is the one also used for sources.

I think the whole text on the comments right now is a bit confusing, and unclear from where the key defined on validpgpkeys= actually comes from.

lquidfire commented on 2024-05-13 09:44 (UTC) (edited on 2024-05-14 18:18 (UTC) by lquidfire)

Package updated.

@NeedaVirus: Could you please check and confirm if the SSL issue has been resolved?

@glitsj16: Thank you for your suggestions. I am willing to add autoreconf as per your suggestion (I don't think it could harm anything), but I don't understand what the xz-issue could be in this software, nor how a reconfigure could improve this. Could you please enlighten me? Thank you in advance!

I had originally implemented the autoreconf suggestion, but now disabled it as I do not understand it, and that seems enough reason for now not to enable it.

glitsj16 commented on 2024-05-08 08:49 (UTC)

@NeedaVirus
Cleaner fix for the configure error: use SSL_PREFIX=/usr ./configure .... Editing openssl's pc file can potentially break building other packages.

@elod / @gromit
After the xz-backdoor debacle it might be wise to re-generate the configure script with auto(re)conf before running it.

prepare() { cd "${pkgname}-${pkgver}-v${pkgver}" NOCONFIGURE=1 autoreconf -vfi }

Upstream released 5.1.18, so that needs attention too.

NeedaVirus commented on 2024-05-08 07:44 (UTC) (edited on 2024-05-08 07:46 (UTC) by NeedaVirus)

Can't install on Arch by May 2024.

configure: error: Could not find exec_prefix for openssl ==> ERREUR : Une erreur s’est produite dans build(). Abandon… -> erreur lors de la construction : eid-mw-exit status 4 -> Impossible d’installer les paquets suivants. Une intervention manuelle est requise : eid-mw - exit status 4

Workaround found by jake99 : 1.) Edit the file /usr/lib/pkgconfig/openssl.pc 2.) Add this two lines at the top of the file :

prefix=/usr exec_prefix=${prefix}

Worked for me, Can the maintainer update his PKGBUILD please ? :-)

« First ‹ Previous 1 2