Newer identity cards need a new version of eid-mw Reproducible: Always
Created attachment 379932 [details] ebuild of eid-mw-4.0.6 I only changed SRC_URI line in this new ebuild. Known issue : do not change gtk use flag or eid-mw no longer compile (-> http://code.google.com/p/eid-mw/issues/detail?id=122) Sven, can you commit this ebuild ?
Comment on attachment 379932 [details] ebuild of eid-mw-4.0.6 --- eid-mw-4.0.4_p1253.ebuild 2014-03-07 16:24:12.000000000 +0100 +++ - 2014-06-30 06:38:29.258292254 +0200 @@ -12,7 +12,7 @@ SRC_URI="" else MY_P="${PN}-${PV/_p/-}" - SRC_URI="http://eid.belgium.be/en/binaries/${MY_P}_tcm406-178475.tgz" + SRC_URI="http://eid.belgium.be/en/binaries/${MY_P}.tar_tcm406-250016.gz -> ${MY_P}.tar.gz" KEYWORDS="~x86 ~amd64" S="${WORKDIR}/eid-mw-$(get_version_component_range 1-3)" fi
(In reply to Vincent Hardy from comment #1) > Known issue : do not change gtk use flag or eid-mw no longer compile > (-> http://code.google.com/p/eid-mw/issues/detail?id=122) > fixed in current svn : https://code.google.com/p/eid-mw/source/detail?r=1502
(In reply to Vincent Hardy from comment #3) > (In reply to Vincent Hardy from comment #1) > > Known issue : do not change gtk use flag or eid-mw no longer compile > > (-> http://code.google.com/p/eid-mw/issues/detail?id=122) > > > fixed in current svn : > https://code.google.com/p/eid-mw/source/detail?r=1502 patch to fix this bug in 4.0.6 sources : Index: cardlayer/src/pinpadlib.h =================================================================== --- cardlayer/src/pinpadlib.h (revision 1501) +++ cardlayer/src/pinpadlib.h (revision 1502) @@ -43,13 +43,14 @@ #endif #ifndef NO_DIALOGS #include "../dialogs/src/dialogs.h" +#endif #ifdef __APPLE__ typedef void* BEID_DIALOGHANDLE; #else typedef unsigned long BEID_DIALOGHANDLE; #endif -#endif + namespace eIDMW { #ifdef EIDMW_PF_EXPORT
@Vincent, I'm not sure what to do here. Wouldn't you first need to add the patch to the ebuild?
(In reply to Sven Vermeulen from comment #5) > @Vincent, I'm not sure what to do here. > > Wouldn't you first need to add the patch to the ebuild? I sent all (full ebuild + patch) to your gmail box (6 july)
Indeed. The files are committed. For future reference, it might be better to use the attachments in bugzilla and reassign the bug to proxy-maint@g.o so that anyone of the proxy maintainers know that some action is required on their/our part.