all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 60725@debbugs.gnu.org, GNU Debbugs <control@debbugs.gnu.org>
Subject: bug#60725: guix lint thinks 2019111-0.7e76d75 is older than 20191111
Date: Wed, 11 Jan 2023 08:43:00 -0500	[thread overview]
Message-ID: <87358hjifv.fsf@gmail.com> (raw)
In-Reply-To: <87ilhdkxv3.fsf@fsfe.org> (Jelle Licht's message of "Wed, 11 Jan 2023 14:24:32 +0100")

retitle 60725 support the special '~' character in our version parser
thanks

Jelle Licht <jlicht@fsfe.org> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Guix,
>>
>> If you run 'guix lint emacs-enh-ruby-mode', it'll print this:
>>
>> --8<---------------cut here---------------start------------->8---
>> emacs-enh-ruby-mode@2019111-0.7e76d75: can be upgraded to 20191111
>> --8<---------------cut here---------------end--------------->8---
> In this particular case, 2019111 seems to have been a typo in the first
> place.  (It misses out on a '1' in our package record).

Thanks!  With this typo fixed, 'guix lint' doesn't suggest a downgrade
anymore.

> AFAIK, any sane versioning scheme would assert that 20191111 > 2019111-anything.

That's not currently the case with Guix.  Guix package version strings
are documented has having the requirement to be 'monotonically
increasing', so '43.rc3' as used by GNOME is seen by Guix as newer than
'43', the final release.

I'll keep this bug open (and retitle it), because implementing ~ would
be useful (GNOME makes use of that scheme, and it's understood by rpm,
dpkg, pkg-config, etc.).

-- 
Thanks,
Maxim




  reply	other threads:[~2023-01-11 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  3:23 bug#60725: guix lint thinks 2019111-0.7e76d75 is older than 20191111 Maxim Cournoyer
2023-01-11 13:24 ` Jelle Licht
2023-01-11 13:43   ` Maxim Cournoyer [this message]
2023-01-11 14:34     ` Jelle Licht
2023-01-11 18:59       ` Maxim Cournoyer

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=87358hjifv.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=60725@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=jlicht@fsfe.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 external index

	https://git.savannah.gnu.org/cgit/guix.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.