From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37556@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#37556: gpg "-unknown" version string
Date: Mon, 30 Sep 2019 09:49:06 +0200 [thread overview]
Message-ID: <CAAeL0SSUnxN2aJUHDDMjLZwjLU1d81C9cMbk4o-urR1rqyvx=g@mail.gmail.com> (raw)
In-Reply-To: <837e5qdzim.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On Mon, Sep 30, 2019 at 9:17 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> "-unknown" is unusual in version strings, IME.
Yes, but, why would that be a problem? It's not like we're going to find a
lot of strings 1.2.3-unknown that aren't really version numbers, are we?
> If this is somehow
> related to gpg, maybe we should chop that before we invoke the
> version-comparison functions, in gpg-related Lisp files only?
Chopping would mean that 2.2.17 and 2.2.17-unknown are equal, but currently
2.2.17-unknown (in epg) is less than 2.2.17.
Certainly the problem can be fixed by wrapping more code with (let
((version-regexp-alist (cons ...)) ...). It's just that it seems a bit
kludgy to me. But whatever, not really a big issue.
[-- Attachment #2: Type: text/html, Size: 975 bytes --]
next prev parent reply other threads:[~2019-09-30 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 22:59 bug#37556: gpg "-unknown" version string Juanma Barranquero
2019-09-30 5:34 ` Lars Ingebrigtsen
2019-09-30 7:17 ` Eli Zaretskii
2019-09-30 7:49 ` Juanma Barranquero [this message]
2019-09-30 8:46 ` Eli Zaretskii
2019-09-30 9:32 ` Juanma Barranquero
2019-09-30 14:04 ` Lars Ingebrigtsen
2019-09-30 14:25 ` Noam Postavsky
2019-09-30 14:42 ` Lars Ingebrigtsen
2019-09-30 14:46 ` Noam Postavsky
2019-10-01 12:09 ` Lars Ingebrigtsen
2019-10-01 14:59 ` Kazuhiro Ito
2019-10-13 3:01 ` Lars Ingebrigtsen
2019-10-13 5:12 ` Juanma Barranquero
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SSUnxN2aJUHDDMjLZwjLU1d81C9cMbk4o-urR1rqyvx=g@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=37556@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).