open-eid / gentoo Goto Github PK

View Code? Open in Web Editor NEW

10.0 10.0 14.0 714 KB

Gentoo ebuild (community provided)

Shell 100.00%

gentoo's People

Contributors

Stargazers

Watchers

Forkers

sainsaar urmet ecognize articice ykshatroff monoidic vozhyk- cesura jaakristioja ceamac mattiasmerilai metsma klondi markovendelin

gentoo's Issues

dev-qt/qtsvg required

Thanks for these ebuilds!
Minor issue, dev-qt/qtsvg is required for qdigidoc4 but is not pulled in as a dependency.

Chrome-tokens-signing packages

https://github.com/open-eid/chrome-token-signing/releases/tag/v1.0.4

Firefox 52 ends support NPAPI plugins

Test link:
https://hwcrypto.github.io/hwcrypto.js/sign.html

app-crypt/qdigidoc4-4.2.1: * Applying sandbox-compat.patch ... 1 out of 1 hunk FAILED -- saving rejects to file common/CMakeLists.txt.rej

sandbox-compat.patch needs some review action.

>>> Unpacking source...
>>> Unpacking qdigidoc4-4.2.1.tar.gz to /mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/work
>>> Source unpacked in /mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/work
>>> Preparing source in /mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/work/qdigidoc4-4.2.1 ...
 * Applying sandbox-compat.patch ...
1 out of 1 hunk FAILED -- saving rejects to file common/CMakeLists.txt.rej                                                                                                                                                             [ !! ]
 * ERROR: app-crypt/qdigidoc4-4.2.1::esteid failed (prepare phase):
 *   patch -p1  failed with /mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/files/sandbox-compat.patch
 *
 * Call stack:
 *               ebuild.sh, line  124:  Called src_prepare
 *             environment, line 3236:  Called cmake-utils_src_prepare
 *             environment, line 2030:  Called default_src_prepare
 *      phase-functions.sh, line  937:  Called __eapi6_src_prepare
 *             environment, line 1362:  Called eapply '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/files/sandbox-compat.patch'                                                                                                       
 *             environment, line 2215:  Called _eapply_patch '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/files/sandbox-compat.patch'                                                                                                
 *             environment, line 2153:  Called __helpers_die 'patch -p1  failed with /mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/files/sandbox-compat.patch'                                                                         
 *   isolated-functions.sh, line  119:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=app-crypt/qdigidoc4-4.2.1::esteid'`,
 * the complete build log and the output of `emerge -pqv '=app-crypt/qdigidoc4-4.2.1::esteid'`.
 * The complete build log is located at '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/temp/build.log'.
 * The ebuild environment file is located at '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/temp/environment'.
 * Working directory: '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/work/qdigidoc4-4.2.1'
 * S: '/mnt/datapool/tmp/portage/app-crypt/qdigidoc4-4.2.1/work/qdigidoc4-4.2.1'

>>> Failed to emerge app-crypt/qdigidoc4-4.2.1, Log file:

qdigidoc4 crashes when ID card is inserted

qdigidoc4 crashes when the ID card is inserted, see open-eid/DigiDoc4-Client#1144.

Please revbump the 4.2.14 ebuild with the patch open-eid/DigiDoc4-Client@a523867 which applies cleanly as a user patch and fixes the issue. Alternatively, please bump the version to 4.3.0 which also contains this fix.

Thanks! :-)

libdigidoc-3.10.5.ebuild depends on deprecated eapi 7 and cmake-utils eclass

libdigidoc-3.10.5.ebuild uses deprecated eapi 6 and cmake-utils eclass, leading portage to complain upon seeing the file and failing to build.
Bumping eapi to 7 and replacing cmake-utils with cmake eclass leads to a successful build, albeit with qa warnings. My limited testing seems to indicate that I did not break anything, but I have no idea what to look for, nor the skills to do so either, so I guess someone who knows what they are doing should take a look:)

libdigidoc-3.10.5.patch.txt
.

www-plugins/firefox-pkcs11-loader-3.13.6::esteid mozextension: EAPI 7 not supported

What's the appropriate move here, who knows?

dev-libs/libdigidocpp-3.13.1 fails to compile

build.log:

/var/tmp/portage/dev-libs/libdigidocpp-3.13.1/work/libdigidocpp-3.13.1/src/xml/ObjectType.h:31:20: error: 'QualifyingPropertiesType' in namespace 'digidoc::xades' does not name a type
     typedef xades::QualifyingPropertiesType QualifyingPropertiesType;
                    ^~~~~~~~~~~~~~~~~~~~~~~~

didn't work until I installed native ccid and pcsc-lite pcscd daemon

Hi!

I have connected the repository and emerged both www-plugins, but they refused to work.
Then, I started poking the opensc-explorer and other commands, all of them said that no card readers were found (card reader was visible under lsusb).

Then, I installed native ccid and pcsc-lite and started the pcscd daemon with

sudo pcscd -a -d -f

after re-inserting the card it worked.

Is this a dependency problem in www-plugins?

I think it needs the daemon from pcsc-lite to work, so

pcsc-lite USE flag for opensc should be required by these packages

dev-libs/libdigidocpp-3.12.1 fails to build

There is missing dependency in dev-libs/libdigidocpp-3.12.1.build on vim, which includes xxd.
build.zip

dev-libs/xml-security-c-2.0.2-r1 fails to fetch

Since it was removed from the Gentoo official portage tree (see #36), fetching dev-libs/xml-security-c-2.0.2-r1::esteid fails because xml-security-c-2.0.2.tar.gz is no longer available from the Gentoo distfiles mirrors, and it seems that on the apache.org side, the respective compressed tarball has been moved to the archive, as a newer version (2.0.4) is already available.

dev-cpp/xsd, dev-libs/xml-security-c, dev-cpp/libxsd-frontend, dev-cpp/libcutl, dev-util/build are dropped from ::gentoo

From package.mask:

# Unmaintained.  Tests fail to build.  Last release in 2014.  No reverse
# dependencies.  Removal in 30 days.  Bug #640860.

(bug 640860)
I really doubt this is going to get upstream to use some other library, so should this package be added to this overlay?

app-crypt/qdigidoc4: missing DEPEND net-nds/openldap?

My binpkg host has openldap, and qdigidoc4 seems to build against it.

https://github.com/open-eid/DigiDoc4-Client/blob/v4.2.4/CMakeLists.txt#L20 does say find_package( LDAP REQUIRED )

But our ebuild doesn't say anything about LDAP. Should it?

This is creating a problem on client hosts without openldap installed. Wondering if I can avoid it, ideally it'd be a USE flag. I'm not even sure what qdigidoc4 uses LDAP for?

dev-libs/libdigidocpp-3.15.0 fails 8 tests

[ebuild U ~] dev-libs/libdigidocpp-3.14.11::esteid [3.14.8::esteid] USE="doc -java (-pdf)" 0 KiB

>>> Test phase: dev-libs/libdigidocpp-3.14.11
 * Source directory (CMAKE_USE_DIR): "/var/tmp/portage/dev-libs/libdigidocpp-3.14.11/work/libdigidocpp-3.14.11"
 * Build directory  (BUILD_DIR):     "/var/tmp/portage/dev-libs/libdigidocpp-3.14.11/work/libdigidocpp-3.14.11_build"
ctest -j 5 --test-load 999
Test project /var/tmp/portage/dev-libs/libdigidocpp-3.14.11/work/libdigidocpp-3.14.11_build
      Start  1: runtest
      Start  2: TSLTest_CA-invalid-type
      Start  3: TSLTest_CA-non-qa
      Start  4: TSLTest_CA-withdrawn
      Start  5: TSLTest_CA-withdrawn-granted-before
 1/16 Test  #2: TSLTest_CA-invalid-type .................   Passed    0.09 sec
      Start  6: TSLTest_CA-withdrawn-granted-after
 2/16 Test  #3: TSLTest_CA-non-qa .......................***Failed    0.09 sec
      Start  7: TSLTest_OCSP-invalid-type
 3/16 Test  #5: TSLTest_CA-withdrawn-granted-before .....   Passed    0.09 sec
      Start  8: TSLTest_OCSP-withdrawn
 4/16 Test  #4: TSLTest_CA-withdrawn ....................   Passed    0.11 sec
      Start  9: TSLTest_OCSP-withdrawn-granted-before
 5/16 Test  #1: runtest .................................***Failed    0.13 sec
      Start 10: TSLTest_OCSP-withdrawn-granted-after
 6/16 Test  #6: TSLTest_CA-withdrawn-granted-after ......   Passed    0.08 sec
      Start 11: TSLTest_TSA-invalid-type
 7/16 Test  #7: TSLTest_OCSP-invalid-type ...............   Passed    0.08 sec
      Start 12: TSLTest_TSA-withdrawn
 8/16 Test  #8: TSLTest_OCSP-withdrawn ..................   Passed    0.08 sec
      Start 13: TSLTest_TSA-withdrawn-granted-before
 9/16 Test  #9: TSLTest_OCSP-withdrawn-granted-before ...***Failed    0.09 sec
      Start 14: TSLTest_TSA-withdrawn-granted-after
10/16 Test #10: TSLTest_OCSP-withdrawn-granted-after ....   Passed    0.09 sec
      Start 15: TSLTest_EE_T-no_QCStatement
11/16 Test #11: TSLTest_TSA-invalid-type ................   Passed    0.08 sec
      Start 16: TSLTest_EE_T-no_QCSD
12/16 Test #14: TSLTest_TSA-withdrawn-granted-after .....   Passed    0.08 sec
13/16 Test #12: TSLTest_TSA-withdrawn ...................***Failed    0.11 sec
14/16 Test #15: TSLTest_EE_T-no_QCStatement .............   Passed    0.08 sec
15/16 Test #13: TSLTest_TSA-withdrawn-granted-before ....***Failed    0.12 sec
16/16 Test #16: TSLTest_EE_T-no_QCSD ....................   Passed    0.07 sec

69% tests passed, 5 tests failed out of 16

Total Test time (real) =   0.33 sec

The following tests FAILED:
          1 - runtest (Failed)
          3 - TSLTest_CA-non-qa (Failed)
          9 - TSLTest_OCSP-withdrawn-granted-before (Failed)
         12 - TSLTest_TSA-withdrawn (Failed)
         13 - TSLTest_TSA-withdrawn-granted-before (Failed)
Errors while running CTest

LastTest.log
build.log

2023: token signing died for browsers, what's next for Gentoo?

I'm currently unclear on how to get https://www.id.ee/en/article/web-eid/ going, your thoughts please?

As-is, I think I'm not able to use ID cards in browser right now, as of Jul 2023?

libdigidocpp-3.13.5/src/PDF.cpp:49:1: error: expected class-name before '{' token

Error when compiling dev-libs/libdigidocpp-3.13.5:

In file included from /var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/DDoc.cpp:22:0:
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/Conf.h:40:46: note: declared here
     DEPRECATED_DIGIDOCPP virtual std::string libdigidocConf() const;
                                              ^~~~~~~~~~~~~~
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:49:1: error: expected class-name before '{' token
 {
 ^


/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp: In constructor 'digidoc::DSSPdfSigIncMemDocument::DSSPdfSigIncMemDocument(const char*)':
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:51:58: error: class 'digidoc::DSSPdfSigIncMemDocument' does not have any field named 'PdfSigIn
cMemDocument'
     DSSPdfSigIncMemDocument(const char* pszInpFilename): PdfSigIncMemDocument(pszInpFilename) {}
                                                          ^~~~~~~~~~~~~~~~~~~~
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp: In member function 'PoDoFo::PdfAcroForm* digidoc::DSSPdfSigIncMemDocument::GetAcroForm()':
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:52:67: error: 'GetExistedAcroForm' was not declared in this scope
     PdfAcroForm* GetAcroForm() { return GetExistedAcroForm(nullptr); }
                                                                   ^
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp: In member function 'virtual digidoc::Signature* digidoc::PDF::sign(digidoc::Signer*)':
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:329:13: error: 'class digidoc::DSSPdfSigIncMemDocument' has no member named 'GetSignatureField'
         doc.GetSignatureField()->SetSignatureDate(PdfDate());
             ^~~~~~~~~~~~~~~~~
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:330:13: error: 'class digidoc::DSSPdfSigIncMemDocument' has no member named 'GetSignatureField'
         doc.GetSignatureField()->SetSignatureReason(roles);
             ^~~~~~~~~~~~~~~~~
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:331:13: error: 'class digidoc::DSSPdfSigIncMemDocument' has no member named 'Initialize'
         doc.Initialize();
             ^~~~~~~~~~
/var/tmp/portage/dev-libs/libdigidocpp-3.13.5/work/libdigidocpp-3.13.5/src/PDF.cpp:359:13: error: 'class digidoc::DSSPdfSigIncMemDocument' has no member named 'Write'
         doc.Write(&out);
             ^~~~~
make[2]: *** [src/CMakeFiles/digidocpp.dir/build.make:184: src/CMakeFiles/digidocpp.dir/PDF.cpp.o] Error 1

www-plugins/chrome-token-signing-1.1.5-r1 fails 11 tests

[ebuild U ~] www-plugins/chrome-token-signing-1.1.5-r1::esteid [1.1.5::esteid] USE="chrome firefox" 0 KiB

>>> Test phase: www-plugins/chrome-token-signing-1.1.5-r1
make -j5   test
make `uname`
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
make[1]: Entering directory '/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5'
make -C host-linux
make[2]: Entering directory '/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-linux'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory '/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-linux'
make[1]: Leaving directory '/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5'
# wildcard will resolve to an empty string with a missing file
# so that OSX will not run with xvfb
python host-test/pipe-test.py -v
test_empty_json (__main__.TestHostPipe.test_empty_json) ... 
Running native component on PID 32
SEND: {}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_inconsistent_origin (__main__.TestHostPipe.test_inconsistent_origin) ... 
Running native component on PID 33
SEND: {"type": "VERSION", "nonce": "e3f3b605-d363-4ee5-afaa-a05ec0d2b29f", "origin": "http://example.com/"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_plain_string (__main__.TestHostPipe.test_plain_string) ... 
Running native component on PID 34
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_random_string (__main__.TestHostPipe.test_random_string) ... 
Running native component on PID 35
SEND: BLAH
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_utopic_length (__main__.TestHostPipe.test_utopic_length) ... 
Running native component on PID 36
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_file_origin (__main__.TestHostPipe.test_version_file_origin) ... 
Running native component on PID 37
SEND: {"type": "VERSION", "nonce": "e633caad-12e1-44a2-a355-0f4de7188e9c", "origin": "file:///tmp/index.html"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_http_origin (__main__.TestHostPipe.test_version_http_origin) ... 
Running native component on PID 38
SEND: {"type": "VERSION", "nonce": "2547022d-380b-4db4-8f8b-90c5861bdcbd", "origin": "http://example.com/"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_https (__main__.TestHostPipe.test_version_https) ... 
Running native component on PID 39
SEND: {"type": "VERSION", "nonce": "645f7ec7-b6ea-4fed-92c7-ec8bf7e1fb2a", "origin": "https://example.com/"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_invalid_origin (__main__.TestHostPipe.test_version_invalid_origin) ... 
Running native component on PID 40
SEND: {"type": "VERSION", "nonce": "e0ccc26a-45f8-4db1-bafa-b1d04a1a9c49", "origin": "foobar in da house"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_no_nonce (__main__.TestHostPipe.test_version_no_nonce) ... 
Running native component on PID 41
SEND: {"type": "VERSION", "origin": "https://example.com/"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR
test_version_no_origin (__main__.TestHostPipe.test_version_no_origin) ... 
Running native component on PID 42
SEND: {"type": "VERSION", "nonce": "9ece7968-21d8-4837-904b-8d39a4cbaa84"}
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

ERROR

======================================================================
ERROR: test_empty_json (__main__.TestHostPipe.test_empty_json)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 78, in test_empty_json
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_inconsistent_origin (__main__.TestHostPipe.test_inconsistent_origin)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 101, in test_inconsistent_origin
    resp1 = self.transceive(json.dumps(cmd))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_plain_string (__main__.TestHostPipe.test_plain_string)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 72, in test_plain_string
    resp = self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_random_string (__main__.TestHostPipe.test_random_string)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 66, in test_random_string
    resp = self.transceive(cmd)
           ^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_utopic_length (__main__.TestHostPipe.test_utopic_length)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 86, in test_utopic_length
    resp = self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_file_origin (__main__.TestHostPipe.test_version_file_origin)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 125, in test_version_file_origin
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_http_origin (__main__.TestHostPipe.test_version_http_origin)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 131, in test_version_http_origin
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_https (__main__.TestHostPipe.test_version_https)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 137, in test_version_https
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_invalid_origin (__main__.TestHostPipe.test_version_invalid_origin)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 119, in test_version_invalid_origin
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_no_nonce (__main__.TestHostPipe.test_version_no_nonce)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 109, in test_version_no_nonce
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

======================================================================
ERROR: test_version_no_origin (__main__.TestHostPipe.test_version_no_origin)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 114, in test_version_no_origin
    resp = self.transceive(json.dumps(cmd))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 49, in transceive
    return self.get_response()
           ^^^^^^^^^^^^^^^^^^^
  File "/var/tmp/portage/www-plugins/chrome-token-signing-1.1.5-r1/work/chrome-token-signing-1.1.5/host-test/pipe-test.py", line 36, in get_response
    response_length = struct.unpack("=I", self.p.stdout.read(4))[0]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack requires a buffer of 4 bytes

----------------------------------------------------------------------
Ran 11 tests in 0.172s

FAILED (errors=11)
make: *** [GNUmakefile:42: test] Error 1

build.log

dev-libs/libdigidocpp-3.13.8 installs Doxygen documentation to incorrect location

 * The ebuild is installing to one or more unexpected paths:
 * 
 *   /usr/share/doc/libdigidocpp
 * 
 * Please fix the ebuild to use correct FHS/Gentoo policy paths.

I suggest the Doxygen files be installed to /usr/share/doc/libdigidocpp-3.13.8/html/ or similar instead.

app-crypt/qdigidoc4-4.2.8 fails to compile: error: variable 'QPainterPath path' has initializer but incomplete type

# ebuild /var/overlays/esteid/app-crypt/qdigidoc4/qdigidoc4-4.2.8.ebuild merge
>>> Existing ${T}/environment for 'qdigidoc4-4.2.8' will be sourced. Run
>>> 'clean' to start with a fresh environment.
>>> Checking qdigidoc4-4.2.8.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'pretend' has already executed for 'qdigidoc4-4.2.8'; skipping.
>>> Remove '/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/.pretended' to force pretend.
>>> It appears that 'setup' has already executed for 'qdigidoc4-4.2.8'; skipping.
>>> Remove '/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'qdigidoc4-4.2.8'; skipping.
>>> Remove '/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'qdigidoc4-4.2.8'; skipping.
>>> Remove '/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/.prepared' to force prepare.
>>> It appears that 'configure' has already executed for 'qdigidoc4-4.2.8'; skipping.
>>> Remove '/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/.configured' to force configure.
>>> Compiling source in /var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4 ...
 * Working in BUILD_DIR: "/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4-4.2.8_build"
ninja -v -j10 -l0
[1/3] /usr/bin/x86_64-pc-linux-gnu-g++ -DAPP=\"qdigidoc4\" -DBUILD_DATE=\"07.04.2021\" -DBUILD_VER=0 -DCONFIG_URL=\"https://id.eesti.ee/config.json\" -DMAJOR_VER=4 -DMINOR_VER=2 -DMOBILEID_URL=\"https://dd-mid.ria.ee/mid-api\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DRELEASE_VER=8 -DSMARTID_URL=\"https://dd-sid.ria.ee/v1\" -DVER_SUFFIX=\"\" -Iclient -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client -Iclient/qdigidoc4_autogen/include -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4 -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/common -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg  -DOF=_Z_OF -O2 -pipe -mtune=native -ggdb -flto -fno-fat-lto-objects -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -MD -MT client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o -MF client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o.d -o client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o -c /var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/MainAction.cpp
FAILED: client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o 
/usr/bin/x86_64-pc-linux-gnu-g++ -DAPP=\"qdigidoc4\" -DBUILD_DATE=\"07.04.2021\" -DBUILD_VER=0 -DCONFIG_URL=\"https://id.eesti.ee/config.json\" -DMAJOR_VER=4 -DMINOR_VER=2 -DMOBILEID_URL=\"https://dd-mid.ria.ee/mid-api\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DRELEASE_VER=8 -DSMARTID_URL=\"https://dd-sid.ria.ee/v1\" -DVER_SUFFIX=\"\" -Iclient -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client -Iclient/qdigidoc4_autogen/include -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4 -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/common -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg  -DOF=_Z_OF -O2 -pipe -mtune=native -ggdb -flto -fno-fat-lto-objects -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -MD -MT client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o -MF client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o.d -o client/CMakeFiles/qdigidoc4.dir/widgets/MainAction.cpp.o -c /var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/MainAction.cpp
/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/MainAction.cpp: In member function 'virtual bool MainAction::eventFilter(QObject*, QEvent*)':
/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/MainAction.cpp:118:22: error: variable 'QPainterPath path' has initializer but incomplete type
  118 |    QPainterPath path(rect.bottomLeft());
      |                      ^~~~
[2/3] /usr/bin/x86_64-pc-linux-gnu-g++ -DAPP=\"qdigidoc4\" -DBUILD_DATE=\"07.04.2021\" -DBUILD_VER=0 -DCONFIG_URL=\"https://id.eesti.ee/config.json\" -DMAJOR_VER=4 -DMINOR_VER=2 -DMOBILEID_URL=\"https://dd-mid.ria.ee/mid-api\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DRELEASE_VER=8 -DSMARTID_URL=\"https://dd-sid.ria.ee/v1\" -DVER_SUFFIX=\"\" -Iclient -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client -Iclient/qdigidoc4_autogen/include -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4 -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/common -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg  -DOF=_Z_OF -O2 -pipe -mtune=native -ggdb -flto -fno-fat-lto-objects -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -MD -MT client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o -MF client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o.d -o client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o -c /var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/CheckBox.cpp
FAILED: client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o 
/usr/bin/x86_64-pc-linux-gnu-g++ -DAPP=\"qdigidoc4\" -DBUILD_DATE=\"07.04.2021\" -DBUILD_VER=0 -DCONFIG_URL=\"https://id.eesti.ee/config.json\" -DMAJOR_VER=4 -DMINOR_VER=2 -DMOBILEID_URL=\"https://dd-mid.ria.ee/mid-api\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DRELEASE_VER=8 -DSMARTID_URL=\"https://dd-sid.ria.ee/v1\" -DVER_SUFFIX=\"\" -Iclient -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client -Iclient/qdigidoc4_autogen/include -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4 -I/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/common -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg  -DOF=_Z_OF -O2 -pipe -mtune=native -ggdb -flto -fno-fat-lto-objects -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -MD -MT client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o -MF client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o.d -o client/CMakeFiles/qdigidoc4.dir/widgets/CheckBox.cpp.o -c /var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/CheckBox.cpp
/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/CheckBox.cpp: In member function 'virtual void CheckBox::paintEvent(QPaintEvent*)':
/var/tmp/portage/app-crypt/qdigidoc4-4.2.8/work/qdigidoc4/client/widgets/CheckBox.cpp:48:29: error: variable 'QPainterPath path' has initializer but incomplete type
   48 |   QPainterPath path(QPointF(rect.left(), rect.center().y()));
      |                             ^~~~
ninja: build stopped: subcommand failed.
 * ERROR: app-crypt/qdigidoc4-4.2.8::esteid failed (compile phase):
 *   ninja -v -j10 -l0 failed
 * 
 * Call stack:
 *     ebuild.sh, line  125:  Called src_compile
 *   environment, line 2049:  Called cmake_src_compile
 *   environment, line  731:  Called cmake_build
 *   environment, line  700:  Called eninja
 *   environment, line 1152:  Called die
 * The specific snippet of code:
 *       "$@" || die "${nonfatal_args[@]}" "${*} failed"

Apparently the faulting C++ files are missing the correct #include lines for class QPainterPath. Manually adding the missing lines seems to be a workaround.

Merge or link https://github.com/urmet/esteid-overlay

There is a Gentoo overlay at https://github.com/urmet/esteid-overlay containing all the necessary software for Estonian ID-card to work. Perhaps you could either pull it here or at least link to it? That repository was last updated in September, and thus is a bit outdated (although working), but copying the ebuilds for their names to point to the latest versions worked well.

Adding repo in Gentoo

To add Esteid repo into layman just run command:

layman -o https://raw.githubusercontent.com/open-eid/gentoo/master/profiles/overlay.xml -f -a esteid

Ebuilds (qdigidoc4, ...?): missing `xdg_icon_cache_update()` call

Emerge is spitting out

* Updating shared mime info database ...                                                                                                           [ ok ]
 * Updating .desktop files database ...                                                                                                             [ ok ]
 * QA Notice: new icons were found installed but icon cache
 * has not been updated:
 *   /usr/share/icons/hicolor/22x22/apps/qdigidoc4.png
 *   /usr/share/icons/hicolor/22x22/mimetypes/application-x-cdoc.png
 *   /usr/share/icons/hicolor/22x22/mimetypes/application-vnd.lt.archyvai.adoc-2008.png
 *   /usr/share/icons/hicolor/22x22/mimetypes/application-x-ddoc.png
 *   /usr/share/icons/hicolor/22x22/mimetypes/application-vnd.etsi.asic-s+zip.png
 *   /usr/share/icons/hicolor/22x22/mimetypes/application-vnd.etsi.asic-e+zip.png
 *   /usr/share/icons/hicolor/32x32/apps/qdigidoc4.png
 *   /usr/share/icons/hicolor/32x32/mimetypes/application-x-cdoc.png
 *   /usr/share/icons/hicolor/32x32/mimetypes/application-vnd.lt.archyvai.adoc-2008.png
 *   /usr/share/icons/hicolor/32x32/mimetypes/application-x-ddoc.png
 *   /usr/share/icons/hicolor/32x32/mimetypes/application-vnd.etsi.asic-s+zip.png
 *   /usr/share/icons/hicolor/32x32/mimetypes/application-vnd.etsi.asic-e+zip.png
 *   /usr/share/icons/hicolor/48x48/apps/qdigidoc4.png
 *   /usr/share/icons/hicolor/48x48/mimetypes/application-x-cdoc.png
 *   /usr/share/icons/hicolor/48x48/mimetypes/application-vnd.lt.archyvai.adoc-2008.png
 *   /usr/share/icons/hicolor/48x48/mimetypes/application-x-ddoc.png
 *   /usr/share/icons/hicolor/48x48/mimetypes/application-vnd.etsi.asic-s+zip.png
 *   /usr/share/icons/hicolor/48x48/mimetypes/application-vnd.etsi.asic-e+zip.png
 *   /usr/share/icons/hicolor/128x128/apps/qdigidoc4.png
 *   /usr/share/icons/hicolor/128x128/mimetypes/application-x-cdoc.png
 *   /usr/share/icons/hicolor/128x128/mimetypes/application-vnd.lt.archyvai.adoc-2008.png
 *   /usr/share/icons/hicolor/128x128/mimetypes/application-x-ddoc.png
 *   /usr/share/icons/hicolor/128x128/mimetypes/application-vnd.etsi.asic-s+zip.png
 *   /usr/share/icons/hicolor/128x128/mimetypes/application-vnd.etsi.asic-e+zip.png
 *   /usr/share/icons/hicolor/16x16/apps/qdigidoc4.png
 *   /usr/share/icons/hicolor/16x16/mimetypes/application-x-cdoc.png
 *   /usr/share/icons/hicolor/16x16/mimetypes/application-vnd.lt.archyvai.adoc-2008.png
 *   /usr/share/icons/hicolor/16x16/mimetypes/application-x-ddoc.png
 *   /usr/share/icons/hicolor/16x16/mimetypes/application-vnd.etsi.asic-s+zip.png
 *   /usr/share/icons/hicolor/16x16/mimetypes/application-vnd.etsi.asic-e+zip.png
 * Please make sure to call xdg_icon_cache_update()
 * in pkg_postinst() and pkg_postrm() phases of of appropriate pkgs.
>>> app-crypt/qdigidoc4-4.2.4 merged.

dev-libs/libdigidoc-3.10.4 installs Doxygen documentation to incorrect location

 * The ebuild is installing to one or more unexpected paths:
 *
 *   /usr/share/doc/libdigidoc
 *
 * Please fix the ebuild to use correct FHS/Gentoo policy paths.

I suggest the Doxygen files be installed to /usr/share/doc/libdigidoc-3.10.4/html/ or similar instead.

Version bump www-plugins/firefox-pkcs11-loader-3.13.4

https://github.com/open-eid/firefox-pkcs11-loader/releases/latest

ERROR: app-crypt/qesteidutil-3.12.10::esteid failed (depend phase): External commands disallowed while sourcing ebuild: replace_version_separator _ -

Cannot find file 'EE.xml'

Ei tea, mis keeles siin rääkima peaks...
While trying to compile qdigidoc via either the -3.13.5 or -9999 ebuild, it hits an error at "Generating qrc_TSL.cpp"

cd /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client && /usr/lib64/qt5/bin/rcc --name TSL --output /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client/qrc_TSL.cpp /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client/TSL.qrc
RCC: Error in '/var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client/TSL.qrc':
Cannot find file 'EE.xml'

While checking through the build log, I found a reference to EE.xml at "Generating TSL.qrc, tl-mp.xml, EE.xml", which does this:

cd /usr/bin && /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client/TSLDownload /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client EE

After checking /var/tmp/portage/app-crypt/qdigidoc-9999/work/qdigidoc-9999_build/client, I found that it wasn't there. After running that command manually, though, the file EE.xml appears there.

I tried unsetting some FEATURES like fakeroot, userpriv andusersandbox and setting -j1 in case they were interfering, but it didn't change anything. I'm guessing it just failed because Portage sandboxing didn't allow it to cd to /usr/bin and therefore the TSLDownload didn't run in the first place.
Using the same sources from the distfiles and mkdir build && cd build && cmake .. && make -j6 worked, so it has to be Portage.