Your message dated Sat, 12 Jul 2025 09:50:43 +0200
with message-id <[email protected]>
and subject line fixed
has caused the Debian Bug report #907635,
regarding add .apk as file extension for jar and jarsigner
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
907635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907635
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash-completion
Version: 1:2.8-1
Android APK files are officially defined as JAR files with JAR
signatures. An APK _must_ have a JAR signature to be considered a valid
APK. JAR signatures in Android land are known as "v1 signatures", there
is now v2 and v3 signatures which are still compatible with JAR, but not
verified or created by JAR tools.
I would really love to see `jarsigner` and `jar` do proper completion
for .apk files.
https://source.android.com/security/apksigning/#schemes
Google used to recommend jarsigner, but now has their own apksigner tool
Microsoft still recommends jarsigner:
https://docs.microsoft.com/en-us/xamarin/android/deploy-test/signing/manually-signing-the-apk#Sign_the_APK_with_jarsigner
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.11-6
--- End Message ---
