Package Details: eid-mw 4.4.13-1

Git Clone URL: https://aur.archlinux.org/eid-mw.git (read-only)
Package Base: eid-mw
Description: The middleware, viewer and Firefox extension for the Belgian electronic identity card (Belgian eID)
Upstream URL: http://eid.belgium.be/
Licenses: LGPL3
Conflicts: eid-viewer
Replaces: eid-viewer
Submitter: xdevla
Maintainer: wget
Last Packager: wget
Votes: 40
Popularity: 0.653444
First Submitted: 2012-02-14 10:56
Last Updated: 2018-12-23 18:43

Pinned Comments

wget commented on 2017-02-07 19:42

Since eid-mw now contains the middleware, the viewer and the Firefox extension, the eid-viewer package is now deprecated. eid-viewer has been merged into this package.

This package is making use of PGP signatures. Please make sure you understand that principle before filling a request: https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key. A GPG public key needs to be imported first, typically with a command like:

gpg --recv-key 824A5E0010A04D46

Receiving GPG keys might fail with the following error message: gpg: keyserver receive failed: Connection refused. If this happens, just check your DNS or use another one.

Update: 2017-03-29 We are now using the build server. As explained in the PKGBUILD file, only the binary files hosted on the dist server are signed, the source files are not in order to avoid confusion with less tech-savvy sysadmins. For security-conscious users like us, we need to use the build server instead. This is why it has been decided, this PKGBUILD won't use the dist server anymore, as long the build server remains publicly available. Using the build server also fixes issues with curl user-agent in the process.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

christofvanhove commented on 2017-01-16 21:49

Thanks for the fast reply. No I did not import the public Key. I managed to get things working by following the instructions on: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

wget commented on 2017-01-15 22:00

@christofvanhove do you have imported the public key as described on the Arch Linux wiki ? https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

In particular "If a needed public key is missing, or if you want to add public keys by other developers, you can import it manually,"

christofvanhove commented on 2017-01-15 21:58

There seems to be a problem with an key:

eid-mw-4.1.21-v4.1.21.tar.gz ... FAILED (unknown public key 824A5E0010A04D46)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build eid-mw.

wget commented on 2017-01-11 11:36

Switching to the release server will be sooner than anticipated. https://twitter.com/wouter_verhelst/status/819143456647970816

wget commented on 2017-01-11 11:36

Switching to the release server will be sooner than anticipated. https://twitter.com/wouter_verhelst/status/819143456647970816

wget commented on 2017-01-10 21:06

Hello there. I'm the new maintainer. I know this package has sources which are not from the release server, but rather the continuous integration server. I'll continue with that branch as the release server has no https for now. I'll switch to the release branch as soon we have https on the server.

wget commented on 2017-01-10 21:06

Hello there. I'm the new maintainer. I know this package has sources which are not from the release server, but rather the continuous integration server. I'll continue with that branch as the release server has no https for now. I'll switch to the release branch as soon we have https on the server.

wget commented on 2017-01-10 21:04

@olive As precised on eid-mw, we will still use the dist branch for now, as the official branch has still no https. As soon the official branch switches to https, I'll change the URL and GPG signatures accordingly.

wget commented on 2017-01-10 21:02

@BlackIkeEagle yes because this isn't the same branch we are using. :)

wget commented on 2017-01-10 21:01

@visibilityspots I cannot reproduce on my side. Make sure all the package from the base-devel group are properly installed. What is the version you are upgrading from?