Bug#884651: marked as done (RFS: stlcmd/1.0-1 [ITP])
Your message dated Tue, 19 Dec 2017 02:03:22 +0100
with message-id <20171219010322.i5hea3tp5cxn5m4m@angband.pl>
and subject line Re: Bug#884651: RFS: stlcmd/1.0-1 [ITP]
has caused the Debian Bug report #884651,
regarding RFS: stlcmd/1.0-1 [ITP]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
884651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884651
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "stlcmd"
* Package name : stlcmd
Version : 1.0-1
Upstream Author : John Allwine <john@allwinedesigns.com>
* URL : https://www.github.com/AllwineDesigns/stl_cmd
* License : GPL
Section : misc
It builds those binary packages:
stlcmd - Suite of commands for generating, inspecting and
manipulating STL files.
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/stlcmd
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/s/stlcmd/stlcmd_1.0-1.dsc
More information about stl_cmd can be obtained from
https://www.allwinedesigns.com/blog/stlcmd.
Changes since the last upload:
* Initial release. (Closes: #884310)
Regards,
John Allwine
--- End Message ---
--- Begin Message ---
On Mon, Dec 18, 2017 at 05:35:54PM -0700, John Allwine wrote:
> 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?
The tarball is properly signed on Github. The watch file also correctly
refers to it. What was missing, was the .asc file in your upload to
mentors. All I had to do was to force uscan to download current version
(uscan -ddv) and repack the source.
It's fine now. You'd just want to remember, the next time you'll upload
Debian packaging of a new upstream release, to have the .asc file sitting on
the disk next to the orig tarball -- the tools will do the right thing
automatically.
> > 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.
Looks fine to me.
> 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?
By building in a fresh clean environment. Of the two tools which automate
this, pbuilder is slower but a lot easier to use.
> My latest changes are up: https://mentors.debian.net/package/stlcmd
Looks great. Uploaded to NEW; any additional changes can go as -2.
Meow!
--
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets. Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.
--- End Message ---
Reply to: