From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
To: Ken Brown <kbrown@cornell.edu>
Cc: "35629@debbugs.gnu.org" <35629@debbugs.gnu.org>
Subject: bug#35629: 27.0.50; version-to-list fails on Cygwin gpg2 version string
Date: Sat, 11 May 2019 17:32:23 +0900 [thread overview]
Message-ID: <86sgtl5r3c.wl--xmue@d1.dion.ne.jp> (raw)
In-Reply-To: <cfd6ec58-a5de-c57e-62df-776f251ff033@cornell.edu>
> > Cygwin's gpg2 has "-unknown" suffix in version string.
> >
> >> $ gpg2 --version
> >>
> >> gpg (GnuPG) 2.2.15-unknown
> >> ...
>
> This is a bug in the Cygwin build of gnupg2. I've sent a fix to the Cygwin
> mailing list:
> http://www.cygwin.org/ml/cygwin/2019-05/msg00089.html
Thank you for the investigation. Actually, the same problem occurs in
MSYS2 and MSYS2/mingw packages. Furthermore, as far as I tested,
autoreconf on release tarball adds extra "-unknown" in version string
independently of platforms.
I think that two issues are related with my bug report.
#1. Cygwin, MSYS2's gnupg binary has extra "-unknown" in version string
despite of that they should be released version.
I think it is what you've reported to Cygwin ML.
#2. Locally built gnupg binary may become "-unknown" suffix version.
GnuPG's autogen.sh makes "-unknown" suffix version configure script if
source code directory doesn't have .git directory. If "-unknown"
suffix is a bug as a general thing, I think GnuPG's repository should
be fixed. If not, I hope vertion-to-list function accepts "-unknown"
suffix. How do you think?
--
Kazuhiro Ito
next prev parent reply other threads:[~2019-05-11 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:23 bug#35629: 27.0.50; version-to-list fails on Cygwin gpg2 version string Kazuhiro Ito
2019-05-10 18:26 ` Ken Brown
2019-05-11 8:32 ` Kazuhiro Ito [this message]
2019-05-11 21:18 ` Ken Brown
2019-08-26 6:04 ` Lars Ingebrigtsen
2019-08-27 14:50 ` Kazuhiro Ito
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sgtl5r3c.wl--xmue@d1.dion.ne.jp \
--to=kzhr@d1.dion.ne.jp \
--cc=35629@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.