Bug#884651: RFS: stlcmd/1.0-1 [ITP]
> Well, how else can uscan verify it?
> It's also used to verify the orig tarball once it's in the archive.
The watch file describes how to download the upstream tar ball and its
signature file. I'm not sure what to do here. Right now I do a debsign
on the .changes file and it signs the .dsc file as well. Then I use
dput which uploads all the files listed in the changes file to
mentors.debian.net. Do I manually sign the .orig file before that?
> Usually, UNRELEASED means the package is not yet ready for uploading. This
> obviously conflicts with a request to upload the package to the official
> archive. I can change this myself, but it's better to ask.
I changed this to unstable.
> Both the fork and the original have plausibly looking statements on their
> front pages on GitHub. That is:
>
> Copyright (c) 2012 Joost Nieuwenhuijse (joost@newhouse.nl)
> Copyright (c) 2011 Evan Wallace (http://madebyevan.com/)
> License: MIT
I added those as well as 2017 @jscad, which is listed in the LICENSE
file in its github repo.
As for the help2man issues. I added help2man to the Build-Depends
field in debian/control, is that all I need to do? How do I test that
it works?
My latest changes are up: https://mentors.debian.net/package/stlcmd
Reply to: