Chris,
On Fri, Sep 1, 2017 at 8:11 AM, Chris Lamb <la...@debian.org> wrote:
>
> Can you think of another way your particular versions could be
> detected?
Sorry, I don't understand what you mean by "versions". I do use a
watch file for Unifont; here is the heart of it:
opts=pgpsigurlmangle=s/$/.sig/ \
ftp://ftp.gnu.org/gnu/unifont/unifont-([\d\.]+)/unifont-([\d\.]+)\.tar\.gz
The upstream signature file will always be a ".sig" binary file
generated with "gpg -b", because that is what is required to upload
the tarball to the GNU Project's server.
With my latest Debian Unifont package though, I re-encoded the
original ".sig" file to an ASCII-armored ".asc" file. I used a
method that Guillem Jover posted in the debian-policy thread that I
started, cited in my previous message for this bug report. It was
either that or have lintian generate an error--or override the error,
which I did not want to do.
Thanks,
Paul Hardy
