Hello Tom, On Thu, 2025-08-07 at 16:44 +0200, schorpp wrote: > > On Thu, 2025-08-07 at 06:44 +0200, Tom Schorpp wrote: > > > This [PATCH]Removes unessecary package dependency blocking backport > > > build install on bookworm > > > > 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 > > 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.
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. > A backport to bullseye was not possible due to Qt6 deps. 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. > 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. 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. > All GUI works and random PIN/PUK and network server operations work so > far, too, logs are fine. That still doesn't prove that it fully works. > Better than Windows 11 Version which does not detect my CSL/Alcor card > Reader or Windows 11 is broken again, reported to > [email protected] > but only stupid FAQ answer received. 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. > I've orderd a Reiner SCT Cyberjack Basis RFID reader which is on the card > reader support list, to be sure. That's the one I'm using as well. > > given the fact that Trixie will be released on Saturday. > > > > Are you not planning to upgrade to Trixie soon? > > 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')" 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/ > > > > If there are any specific issues with the version in Bookworm, please let > > me know. > > 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. 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 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
