Bug 2071304

Before updating libdigidocpp to the lastest version, we need upstream developer to fix this
https://github.com/open-eid/libdigidocpp/issues/462

I have a problem which I think is related to this one (the same error appears on the console). QDigiDoc4 will crash when trying to open .asice files which have been signed by other people.

There's now a new release of qdigidoc4 (https://github.com/open-eid/DigiDoc4-Client/releases/tag/v4.2.12) and libdigidocpp (the newest release that's been prepared today has not been tagged yet, so see https://github.com/open-eid/libdigidocpp/commits/master)

It would be great to see some progress on this. I am unable to open .asice files from other people.

Hello, I have just written to upstream developer because I don't know how to apply patch to qt-common/blob/master/CMakeLists.txt as explained at
https://github.com/open-eid/DigiDoc4-Client/wiki/DeveloperTips#building-in-sandboxed-environment
As soon I will receive a reply, I will update the package to the lastest version

Can't release an update until [1] will be fixed
[1]: https://github.com/open-eid/DigiDoc4-Client/issues/1119

To anyone that commented this bugreport and is **CURRENTLY** also a Fedora package maintainer. I need your help in fixing qdigidoc build failures. I contacted upstream developer and added patch1
https://src.fedoraproject.org/rpms/qdigidoc/blob/rawhide/f/qdigidoc.spec#_33
but the build still fails.
I am currently very busy, can I ask you if you have some time to check if you manage to fix it and please send a pull request?
Thank you and have a nice day!

FEDORA-2022-f29121e528 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f29121e528

FEDORA-2022-a8c65b1511 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a8c65b1511

surprisingly a new build successfully built. So it must have been a problem of libraries. Please leave a karma feedback on previous URLs so that the update can go as soon as possible into stable repository

FEDORA-2022-5ecb512d1f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5ecb512d1f

FEDORA-2022-f29121e528 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-f29121e528`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f29121e528

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-a8c65b1511 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a8c65b1511`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a8c65b1511

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-5ecb512d1f has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5ecb512d1f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5ecb512d1f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-a8c65b1511 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-5ecb512d1f has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-f29121e528 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.