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

2017-12-20 Thread 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

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

2017-12-18 Thread 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

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

2017-12-18 Thread 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 ho

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

2017-12-18 Thread 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 a

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

2017-12-18 Thread 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

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

2017-12-18 Thread 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 suggeste

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

2017-12-18 Thread 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

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

2017-12-17 Thread 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