Hi, On 2021-04-14 19:02, gregor herrmann wrote: > On Wed, 14 Apr 2021 09:06:19 +0300, Andrius Merkys wrote: > >> CPAN's default bugtracker is rt.cpan.org. Therefore, it would be nice to >> have Bug-Database and Bug-Submit fields of debian/upstream/metadata >> auto-filled in with appropriate default values for CPAN packages: >> >> Bug-Database: https://rt.cpan.org/Dist/Display.html?Name=$PKG >> Bug-Submit: https://rt.cpan.org/Ticket/Create.html?Queue=$PKG > > [$PKG -> $CPAN_Distribution]
Right, that's what I meant, thanks for correction. > I'm not sure this makes sense. Here's my quick train of thought: > > I know of 3 producers of debian/upstream/metadata: our own > dh-make-perl and dpt-debian-pstream, plus lintian-brush (run manually > or via the janitor). I think all of them do basically the same: Add > Bug-* entries if this information is present in META.yml or > META.json, plus some guesswork to add GitHub issues if there is no > bugtracker information but a GutHub repo. > > Then I know of one consumer of debian/upstream/metadata: dpt-forward, > which already uses CPAN RT as a default value if it doesn't find a > better info anywhere else (in META.* or debian/upstream/metadata). UltimateDebianDatabase also seems to ingest debian/upstream/metadata to its tables, but I haven't checked how they look there. Also I am not aware of services using the UDD. > I'm not opposed to adding "Bug-*: CPAN RT" to > debian/upstream/metadata in both dpt-debian-upstream and dh-make-perl > for cases where there is no explicit bugtracker in META.* and there > is no upstream repo on GitHub; but the result at least for my use and > the consumers I know would just be that dpt-forward does the same as > it does now: use CPAN RT for forwarding bug reports/patches. > > But it's of course possible that there are other consumers or other > use cases where this would help. I agree. Most likely this would not add much benefit. Best, Andrius