GNU bug report logs - #37556
gpg "-unknown" version string

Previous Next

Full log

View this message in rfc822 format

From: Kazuhiro Ito <kzhr <at> d1.dion.ne.jp>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Juanma Barranquero <lekktu <at> gmail.com>, Noam Postavsky <npostavs <at> gmail.com>, 37556 <at> debbugs.gnu.org
Subject: bug#37556: gpg "-unknown" version string
Date: Tue, 01 Oct 2019 23:59:20 +0900

> >>> I don't understand why making -unknown equivalent to a lesser version
> >>> makes sense.  Shouldn't 2.2.17 and 2.2.17-unknown in fact be equal?
> >>
> >> Should they?  2.2.17-pre and 2.2.17-alpha should be less than 2.2.17,
> >> but how do we know that -unknown isn't something -alpha-ish?
> >
> > It's "unknown", so it could be something opposite-of-alpha-ish too,
> > right?  On average, 0 seems right.
> 
> That's possible.  Does anybody know how usual these -unknown things are,
> and why they exist?

I don't know "why", but I described when the suffix was added in the
past post.

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35629#11

> GnuPG's autogen.sh makes "-unknown" suffix version configure script if
> source code directory doesn't have .git directory.

If you have the repository, autogen.sh can set an apropriate revision
number.  I guess "-unknown" version means "unknown version" literally,
because they couldn't decide the source code revision without
repository.

-- 
Kazuhiro Ito

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.