Your message dated Mon, 13 Apr 2020 17:47:36 -0400 with message-id <[🔎] 877dyjys5j.fsf@fifthhorseman.net> and subject line Re: Bug#956613: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated has caused the Debian Bug report #956613, regarding lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated 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.) -- 956613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956613 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated
- From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
- Date: Mon, 13 Apr 2020 12:36:32 -0400
- Message-id: <[🔎] 87imi37373.fsf@fifthhorseman.net>
Package: lintian Version: 2.65.0 in balsa 2.6.0, balsa.appdata.xml is generated during the build from balsa.appdata.xml.in. While d/copyright correctly indicates that balsa.appdata.xml.in is CC0-1.0, lintian still complains with: W: balsa source: inconsistent-appstream-metadata-license balsa.appdata.xml (cc0-1.0 != gpl-2+) It seems that to quiet this warning, i would need to add a d/copyright entry for a file (balsa.appdata.xml) that is not shipped in the source package, which would be weird and (i think) wrong. Rather, i think lintian should avoid warning about license information in a file that is not part of the source package. Thanks for maintaining lintian in debian! --dkgAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Felix Lechner <felix.lechner@lease-up.com>
- Cc: 956613@bugs.debian.org, 956613-done@bugs.debian.org
- Subject: Re: Bug#956613: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated
- From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
- Date: Mon, 13 Apr 2020 17:47:36 -0400
- Message-id: <[🔎] 877dyjys5j.fsf@fifthhorseman.net>
- In-reply-to: <[🔎] CAFHYt542ENnpPzr-Su-PsE1QaRJkqOowwQpw6fYww0VJRaji2A@mail.gmail.com>
- References: <[🔎] 87imi37373.fsf@fifthhorseman.net> <[🔎] CAFHYt542ENnpPzr-Su-PsE1QaRJkqOowwQpw6fYww0VJRaji2A@mail.gmail.com>
On Mon 2020-04-13 09:52:32 -0700, Felix Lechner wrote: > I do not see that tag when running lintian's development version > against balsa from unstable: there are separate issues with the appdata files in 2.5.9 (that have since been fixed upstream): https://gitlab.gnome.org/GNOME/balsa/-/merge_requests/22 so the issue only shows up in 2.6.0 (which just landed in unstable today) > Lintian should not complain, for a source package, about files not > shipped within it. Was the file perhaps included accidentally? ah, i might have gotten confused about the file name due to it being overwritten during the build. i do most of my packaging work from a gbp tree, and that tree has the generated files already pre-stripped (via an import-orig filter in debian/gbp.conf). Looks like upstream does in fact ship a copy of these generated files in the tarball, though, so i probably should mark them in debian/copyright anyway. I'm closing this ticket because it looks like i do need to mark the generated file in d/copyright anyway, which means there's a more obvious fix for me to do in this packaging. sorry for the noise! --dkgAttachment: signature.asc
Description: PGP signature
--- End Message ---