Bug#946413: lintian-brush: Some thoughts on fixers for debian/upstream/metadata
Package: lintian-brush
Version: 0.44
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Going throught the merge requests for perl packages, I noticed some
issues around the handling of debian/upstream/metadata:
- - The perl YAML libraries we use add "---\n" at the top of the file,
which the used Python libraries in lintian-brush apparently don't
do. No idea what is more correct or if it matters at all; I just
noted that the removal of the line adds some noise.
- - Sometimes when Contact and Name are removed, all that's left in our
files is "Archive: CPAN" which is no so helpful. In those cases I
just removed debian/upstream/metadata completely. Not sure if lintian-brush
should do the same or if I should stop removing it or something
else :)
- - Similarly, if lintian-brush creates debian/upstream/metadata for a
perl package, it might add "Archive: CPAN" (not that we use it but
the Archive field exists …).
- - The URLs lintian-brush finds in META.{json,yml} sometimes have room
for improvement; in our tools [0] we e.g. fix github URLs to use
https etc. It would be nice if lintian-brush could also learn some
of these tricks.
Cheers,
gregor
[0]
https://salsa.debian.org/perl-team/modules/packages/dh-make-perl/blob/master/lib/DhMakePerl/Command/Packaging.pm#L1636
https://salsa.debian.org/perl-team/modules/packages/pkg-perl-tools/blob/master/scripts/debian-upstream#L30
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl3tWFlfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgb7YBAArhND3dDmqw1vIQx5D3DvWMGc4XtZktsxH3CWpbm0oQvO0ijAs2MkuaJz
NH+5uXYcUB6tDmfCzg7stKdvADAMY4tYNeH5BwijwobIW/Ar5sZ6sliA+IDtQhgl
fOSGGEbECSrLLpZXqVBd/xzF4sj1V9pe5fkRIuOp5LWoTyn3iw/sIpKhvo4uk/De
xeXc81NCj4Bk1gx0eBg8PMT/86aoKq5vWU1rkgqJY3xwtzQ7Wb273iXp9MZmejFu
PohUXSJO/qWW5rNnNnH/X5wZzqIz5L5feU6SqbBsbXCvWpziJ0fC41S1RP0cR3wB
fuH/XNGpIQl2y9tqmwPFnoJwiw+tjMx1gHM3Yu/yrrsB58r74kOzk2+lw+psQoU3
YCUAfMIAUYc5kOcHyKlN9YXKh9sGUTkdUKegmf/llVXLBewH1efyX391qNTJ/g7o
fB87kLF457jRGA7aR5rOY7wnj7JiIf6B1Djk1+5UN9QwnJixvbkEbdq+962SCQ1X
a4tNPxXQzi/jLyO6TPGcKcnQK6YngPstou7A0ChG44Q0LGq2vbC03Fa0hnKEeEeo
klPwBnhF522h6ZajkfzXnXvX+bMOvz8iB9fFREPfrGIXMkSmv011hsKSMAw7GCg4
9dlNllbSksvYOzJI85n4ZcyqVMSHIXswvYrJZ9kLO3zjwGdwxiE=
=UBaC
-----END PGP SIGNATURE-----
Reply to: