[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916735: marked as done (lintian: appstream-metadata-missing-modalias-provide should be info, not warn)

Your message dated Tue, 17 Dec 2019 06:27:33 -0800
with message-id <CAFHYt56uMReCVfG0T-hs+h8U+1XJiMhc_AO8sQ4ALDEwM262RQ@mail.gmail.com>
and subject line Re: Bug#916735: lintian: appstream-metadata-missing-modalias-provide should be info, not warn
has caused the Debian Bug report #916735,
regarding lintian: appstream-metadata-missing-modalias-provide should be info, not warn
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 owner@bugs.debian.org
immediately.)


-- 
916735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916735
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.5.117
Severity: normal

The appstream-metadata-missing-modalias-provide relates to a nice to have
feature.  Lintian treating this at a "Warning" level seems excessive for
something that's completely optional.  Info seems right.

Scott K

--- End Message ---
--- Begin Message --- 
Hi Scott,

On Tue, Dec 18, 2018 at 11:39 PM Scott Kitterman <debian@kitterman.com> wrote:
>
> I'm not arguing it's a bad idea to have the check, but personally, I get tired of looking at it.  If this is important, get it in Policy as a should and then I think warning would be appropriate.
>
> Why don't I just fix it?  I read the referenced material on what needs doing and concluded I don't have the spare mental cycles to learn all about this for one package.
>
> It'd be much more efficient for someone who both understands what needs doing and cares to run through the affected packages and submit patches.

Here is a merge request that provides a working metadata file and
removes the Lintian override. The sole purpose is to close this bug
report.

    https://salsa.debian.org/kitterman/libnitrokey/merge_requests/2

I also saw your bug #916911, which prompted upstream to provide
similar data with the package nitrokey-app. Perhaps the udev rules
should also ship in nitrokey-app. I copied that bug and the people who
commented on this message.

For their benefit, the Appstream metadata file from the merge request
is also attached to this message.

> In the meantime, I think info is the right level.

I have no opinion and left the severity as is.

Kind regards
Felix Lechner

<?xml version="1.0" encoding="UTF-8"?>
<component>
  <id>com.github.Nitrokey.libnitrokey</id>
  <metadata_license>LGPL-3.0+</metadata_license>
  <name>libnitrokey</name>
  <summary>Library to communicate with Nitrokey stick devices</summary>
  <description>
    <p>
	Library to communicate with Nitrokey Pro and Storage devices
	in a clean and easy manner. Written in C++14, testable with
	py.test and Catch frameworks, with C API, Python access.
    </p>
  </description>
  <provides>
    <modalias>usb:v2581pF1D0d*</modalias>
    <modalias>usb:v20A0p4287d*</modalias>
    <modalias>usb:v20A0p42B1d*</modalias>
    <modalias>usb:v20A0p4107d*</modalias>
    <modalias>usb:v20A0p4108d*</modalias>
    <modalias>usb:v20A0p4109d*</modalias>
    <modalias>usb:v20A0p4211d*</modalias>
    <modalias>usb:v20A0p4230d*</modalias>
  </provides>
</component>

--- End Message ---
Reply to: