Bug#930595: RFS: uacme/1.0.15-2 [ITP]
On Sun, Jun 16, 2019 at 10:52:00AM +0200, Nicola Di Lieto wrote:
> * Package name : uacme
> Version : 1.0.15-2
> Upstream Author : Nicola Di Lieto <nicola.dilieto@gmail.com>
> * URL : https://github.com/ndilieto/uacme
> uacme - Lightweight client for the RFC8555 ACMEv2 protocol
There's already a team in Debian dedicated to packaging of stuff made by
that anvil-making company. Have you contacted them?
The package doesn't build for me:
http://ix.io/1LVo
./configure: line 5401: syntax error near unexpected token `$CFLAGS'
./configure: line 5401: `AX_CHECK_COMPILE_FLAG($CFLAGS -Wall, CFLAGS="$CFLAGS -Wall")'
Not building something (like the man page) from source is usually a serious
error. In this particular case, groff is nearly as sourcey format as
asciidoc -- but it'd still be a problem with upstreaming. Someone wanting
to improve the man page can't easily test asciidoc (as the patched build
system doesn't use that) yet improvements done as groffage wouldn't be liked
by upstream (in this case you). But, what about using asciidoctor instead?
That's supposed to be a drop-in replacement for asciidoc.
Your upstream project seems to use straightforward sane github-based release
workflow, that makes watch files easy to write (just copy one of existing
recipes). Watch files are not mandatory, but are nice to have.
A new package can be uploaded only to unstable (or experimental) -- your
version is targetted at stretch. For a backport, it needs to first be in
testing, thus please retarget at unstable even if you eventually do want to
include a backport later. And, we care about future releases more than
past.
But generally, the above problems aside, the package seems to be well made.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Secret tech: have up-to-date backups. Rules of this world say
⢿⡄⠘⠷⠚⠋⠀ a failure can ever happen if you don't have them, which saves a
⠈⠳⣄⠀⠀⠀⠀ lot of downtime spent restoring.
Reply to: