Bug#930595: RFS: uacme/1.0.15-2 [ITP]

[Adam Borowski <kilobyte@angband.pl>]

(Sorry for slow response time.)

On Sun, Jun 23, 2019 at 10:18:20AM +0200, Nicola Di Lieto wrote:
> https://mentors.debian.net/debian/pool/main/u/uacme/uacme_1.0.16-7.dsc

I haven't actually tested the functionality, but packaging seems almost
ready.

One issue is the watch file being empty (save for comments).  If there's
nothing inside, it should be deleted.  But, for a Github project that does
sane release, it's too trivial to fill it instead:
.----
version=4
opts=filenamemangle=s/.+\/v(\d\S*)\.tar\.gz/uacme-$1\.tar\.gz/ \
  https://github.com/ndilieto/uacme/tags .*/v(\d\S*)\.tar\.gz
`----

The other thing are changelog entries that have never entered the archive.
The changelog is supposed to include only actually released changes -- it's
natural that there are multiple iterations during review, but those are
not interesting to the end-user -- especially these days as we have git
repositories for such minutiae.

Thus, unless there's a good reason, such changelog entries get squashed;
and, since there's no previous release, just a single "Initial release
(Closes: #123456)" is enough.  Also, both people and tools tend to get
confused when there's a -7 but no -1.

("Good reasons" include the package being deployed to some actual users,
such as a different distribution or even a company's or a cluster's internal
machines -- in which case, reusing version numbers would cause harm.)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up.  This
⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project.
⠈⠳⣄⠀⠀⠀⠀