#1110501 ausweisapp: [PATCH]Remove unessecary package dependency blocking backport build install on bookworm #1110501
- Package:
- ausweisapp
- Source:
- ausweisapp
- Description:
- Official authentication app for German ID cards and residence permits
- Submitter:
- Tom Schorpp
- Date:
- 2025-09-21 12:03:03 UTC
- Severity:
- normal
- Tags:
Dear Maintainer, This [PATCH]Removes unessecary package dependency blocking backport build install on bookworm --- debian/control.orig 2025-07-08 13:30:30.000000000 +0200 +++ debian/control 2025-08-07 00:51:37.696629436 +0200 @@ -33,7 +33,7 @@ qml6-module-qtqml-statemachine, qml6-module-qtqml-workerscript, qml6-module-qtquick-controls, - qml6-module-qtquick-effects, +# qml6-module-qtquick-effects, qml6-module-qtquick-layouts, qml6-module-qtquick-templates, qml6-module-qtquick-window,
Hello Tom, I have not tested yet whether the current upstream version of AusweisApp works on Bookworm and I'm not sure whether the backport makes sense given the fact that Trixie will be released on Saturday. Are you not planning to upgrade to Trixie soon? If there are any specific issues with the version in Bookworm, please let me know. Adrian
Am 07.08.25 um 09:14 schrieb John Paul Adrian Glaubitz: Hello Adrian, It makes sense, most debian stable users will appreciate it and the upstream authors do not commit to CVE's, so I strongly recommend not to use outdated versions for security concerns. A backport to bullseye was not possible due to Qt6 deps. It's running fine so far on the RPI, not fully tested because I've got no PIN letter for the old ePerso/eID card because in 2010 I was in political opposition to eID, I get an new card the next weeks. All GUI works and random PIN/PUK and network server operations work so far, too, logs are fine. Better than Windows 11 Version which does not detect my CSL/Alcor card Reader or Windows 11 is broken again, reported to support.ausweisapp2@governikus.de but only stupid FAQ answer received. I've orderd a Reiner SCT Cyberjack Basis RFID reader which is on the card reader support list, to be sure. Yes, as stated in my report, apt follows stable arm64 automatically on the PI here: "APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')" I will, thank You, I need it for faster communication with courts and offices, paper letters are too slow, e.g. using Mein Justizportal which needs a Bund ID account and eID card. y tom
Hello Tom, Are there any CVEs that you are aware of? If no, there is no urgent reason for an upgrade. Debian Stable like most LTS distributions doesn't update packages to their latest version by choice. This is to prevent users from breaking changes which can always happen with new upstream versions. I'm not saying updating packages through backports is generally a bad idea, I'm providing such updates. But it's also wrong to insist on having the latest version in the archives for Debian stable when there is no urgent need for it. It's good to know that when I consider looking into backporting the package for Debian Bookworm. I have not decided yet whether I'm going to do that. Well, unless you have fully tested the functionality of the updated package on Debian Bookworm, you can't really be sure that the backport works. It might still be broken due to compatibility issues with OpenSSL, for example. That still doesn't prove that it fully works. There can still be many ways the application may not work properly, hence we need to fully test it when backporting. Being less broken than on Windows 11 shouldn't be our standard, really. That's the one I'm using as well. FWIW, I have backported the latest 2.3.2 version for Debian Trixie now: https://tracker.debian.org/news/1669156/accepted-ausweisapp2-232-1bpo131-source-amd64-all-into-stable-backports/ Sure. I just need to know when there are any issues with the package. I don't need reports that confirm the application works fine. I already know that ;-). Adrian