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

Bug#956613: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated



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!

    --dkg

Attachment: signature.asc
Description: PGP signature


Reply to: