Your message dated Wed, 15 Jan 2025 09:24:25 +0100
with message-id <[email protected]>
and subject line Re: nitrokey-app: Please announce supported hardware via 
appstream
has caused the Debian Bug report #916911,
regarding nitrokey-app: Please announce supported hardware via appstream
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.)


-- 
916911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916911
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nitrokey-app
Version: 1.3.1-1
Tags: patch

It would be nice if the package provided information about what hardware
it support to appstream, to allow the isenkram tool and other users of
appstream data to propose the package when the appropriate USB dongle is
inserted into a machine.

Here is a proposed patch to do so, based on the udev file included in
libnitrokey:

--- data/com.nitrokey.nitrokey-app.appdata.xml.~1~      2018-05-13 
08:58:17.000000000 +0000
+++ data/com.nitrokey.nitrokey-app.appdata.xml  2018-12-20 11:57:44.572350004 
+0000
@@ -21,6 +21,11 @@
   </releases>
   <provides>
          <binary>nitrokey-app</binary>
+         <modalias>usb:v20A0p4107d*</modalias>
+         <modalias>usb:v20A0p4108d*</modalias>
+         <modalias>usb:v20A0p4109d*</modalias>
+         <modalias>usb:v20A0p4211d*</modalias>
+         <modalias>usb:v20A0p4230d*</modalias>
   </provides>
   <launchable type="desktop-id">nitrokey-app.desktop</launchable>
   <url type="homepage">https://www.nitrokey.com/</url>

-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---
--- Begin Message ---
Version: 1.4.2-1

I still do not know in which version it was added, but it is definitely
present in version 1.4.2-1, so I use it when closing this bug to get it
off my radar of packages to get fixed. :)

-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---

Reply via email to