Bug#933804: Improve dpt-forward documentation

Alex Muntada alexm at debian.org
Mon Sep 2 00:33:34 BST 2019


Control: owner -1 !
Control: tags -1 + fixed pending

Hi Aniol,
thanks for trying dpt-forward and taking the time to report this
bug. Feedback is very welcome :)

> In the dpt-forward man page the need to belong in an
> organization when forwarding a patch to GitHub is not
> stated, so the user won't know that the default organization
> is pkg-perl-tools and it may have to be changed with the
> variable DPT_GITHUB_ORGNAME. I think that both the need to
> be in a organization and how to change it should be added to
> the man page.

The documentation for DPT_GITHUB_* variables and defaults is
available in man Debian::PkgPerl::GitHub. Unfortunately there
was no mention of that in man dpt-forward, so I just added it:
https://salsa.debian.org/perl-team/modules/packages/pkg-perl-tools/commit/ddb5d96a068a2af7ef91c161c007a14841e68a5e

> On the other hand, it is also not explained that the clone
> process is done through SSH, and it may cause problems if you
> expect it to be HTTPS. In this case I think that adding a
> variable DPT_GITHUB_PROTOCOL={https,ssh} would be very useful.

For the record, we've alreary addressed that in merge request !7:
https://salsa.debian.org/perl-team/modules/packages/pkg-perl-tools/merge_requests/7

Thank you!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada <alexm at debian.org>
  ⢿⡄⠘⠷⠚⠋   Debian Developer 🍥 log.alexm.org
  ⠈⠳⣄⠀⠀⠀⠀

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20190902/3b492310/attachment.sig>


More information about the pkg-perl-maintainers mailing list