Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[John Allwine]

I was building my Docker image on top of ubuntu:16.04. Switching to
debian:latest fixed this. Oops!

On Mon, Dec 18, 2017 at 7:33 PM, John Allwine  wrote:
> Maybe I'm using an old version that doesn't pick that up? Or I'm not
> naming it correctly? Here's the script that I run in an unbuntu docker
> image: 
> https://github.com/AllwineDesigns/build_stlcmd_deb/blob/master/build_stlcmd.sh
> ( (If you have docker installed you can clone that repo and do a
> docker build . to try it out)
> You can see at line 11 that I'm downloading the .asc file (right after
> downloading the .orig file). At the bottom I'm using debuild to build
> the package, but it's not picking up the .asc file.
>
> On Mon, Dec 18, 2017 at 6:41 PM, Adam Borowski  wrote:
>> On Mon, Dec 18, 2017 at 06:36:00PM -0700, John Allwine wrote:
>>> Thanks Adam! I really appreciate you taking the time to look through
>>> this. I'm still unclear on how to include the .asc file in my upload.
>>> The dput command takes the .changes file, which determines which files
>>> are uploaded, so how do I include the .asc file since it's not listed?
>>> Do I manually edit the .changes file? Is there another method with
>>> more control over what I upload?
>>
>> Just have it in the parent directory when you build the source (with
>> dpkg-buildpackage -S or a wrapper which calls it), next to .orig.
>>
>>
>> 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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[John Allwine]

Maybe I'm using an old version that doesn't pick that up? Or I'm not
naming it correctly? Here's the script that I run in an unbuntu docker
image: 
https://github.com/AllwineDesigns/build_stlcmd_deb/blob/master/build_stlcmd.sh
( (If you have docker installed you can clone that repo and do a
docker build . to try it out)
You can see at line 11 that I'm downloading the .asc file (right after
downloading the .orig file). At the bottom I'm using debuild to build
the package, but it's not picking up the .asc file.

On Mon, Dec 18, 2017 at 6:41 PM, Adam Borowski  wrote:
> On Mon, Dec 18, 2017 at 06:36:00PM -0700, John Allwine wrote:
>> Thanks Adam! I really appreciate you taking the time to look through
>> this. I'm still unclear on how to include the .asc file in my upload.
>> The dput command takes the .changes file, which determines which files
>> are uploaded, so how do I include the .asc file since it's not listed?
>> Do I manually edit the .changes file? Is there another method with
>> more control over what I upload?
>
> Just have it in the parent directory when you build the source (with
> dpkg-buildpackage -S or a wrapper which calls it), next to .orig.
>
>
> 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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[Adam Borowski]

On Mon, Dec 18, 2017 at 06:36:00PM -0700, John Allwine wrote:
> Thanks Adam! I really appreciate you taking the time to look through
> this. I'm still unclear on how to include the .asc file in my upload.
> The dput command takes the .changes file, which determines which files
> are uploaded, so how do I include the .asc file since it's not listed?
> Do I manually edit the .changes file? Is there another method with
> more control over what I upload?

Just have it in the parent directory when you build the source (with
dpkg-buildpackage -S or a wrapper which calls it), next to .orig.


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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[John Allwine]

> 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 (jo...@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

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[Adam Borowski]

On Mon, Dec 18, 2017 at 04:00:53PM -0700, John Allwine wrote:
> The signing-key.asc is for uscan when checking for updates in the watch. 
> Am I supposed to sign the orig tar ball?

Well, how else can uscan verify it?
It's also used to verify the orig tarball once it's in the archive.

On the other hand, signed tarballs are far less useful when maintainer is
the same person as upstream -- you don't need to rely on any untrusted
paths.

> I left it as UNRELEASED as that was suggested in the walkthrough I went
> through.  I can change it to unstable.

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.

> Will add the original license of CSG.js as well.

Both the fork and the original have plausibly looking statements on their
front pages on GitHub.  That is:

Copyright (c) 2012 Joost Nieuwenhuijse (jo...@newhouse.nl)
Copyright (c) 2011 Evan Wallace (http://madebyevan.com/)
License: MIT


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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[John Allwine]

Thanks Adam!

Ack, I just introduced that help2man issue fixing the lintian warnings about 
man pages. Will reorganize a bit to fix that.

The signing-key.asc is for uscan when checking for updates in the watch. Am I 
supposed to sign the orig tar ball?

I left it as UNRELEASED as that was suggested in the walkthrough I went 
through. I can change it to unstable.

Will add the original license of CSG.js as well.

John Allwine
Owner of Allwine Designs
http://www.allwinedesigns.com

> On Dec 18, 2017, at 3:29 PM, Adam Borowski  wrote:
> 
>> On Sun, Dec 17, 2017 at 09:54:10PM -0700, John Allwine wrote:
>> * Package name: stlcmd
>>   Version : 1.0-1
> 
>>  stlcmd - Suite of commands for generating, inspecting and
>> manipulating STL files.
> 
> Alas, it fails to build:
> /bin/sh: 2: help2man: not found
> 
> I also don't see any copyright data for src/csgjs/ which obviously comes
> from a different set of authors.
> 
> The .orig tarball's signature seems to be missing -- despite you apparently
> wanting it to be signed (debian/upstream/signing-key.asc is present).
> 
> The target distribution is set to UNRELEASED, I assume you wanted unstable
> instead, right?
> 
> 
> 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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[Adam Borowski]

On Sun, Dec 17, 2017 at 09:54:10PM -0700, John Allwine wrote:
>  * Package name: stlcmd
>Version : 1.0-1

>   stlcmd - Suite of commands for generating, inspecting and
> manipulating STL files.

Alas, it fails to build:
/bin/sh: 2: help2man: not found

I also don't see any copyright data for src/csgjs/ which obviously comes
from a different set of authors.

The .orig tarball's signature seems to be missing -- despite you apparently
wanting it to be signed (debian/upstream/signing-key.asc is present).

The target distribution is set to UNRELEASED, I assume you wanted unstable
instead, right?


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.

Bug#884651: RFS: stlcmd/1.0-1 [ITP]

[John Allwine]

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 
 * 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