From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: check guix human readable version
Date: Fri, 03 May 2019 11:56:51 +0200 [thread overview]
Message-ID: <87v9yreu8s.fsf@gnu.org> (raw)
In-Reply-To: <877eb8wlzt.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 03 May 2019 00:05:26 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> znavko@disroot.org writes:
>
>> Hi! I want be able to see which version number of guix I have, not commit but human-readable version, such as 1.0.0. How to do this?
>> Once performing `guix pull` I saw it, but now I cannot do it this ways:
>>
>> # guix describe
>> Generation 88 May 02 2019 17:18:30 (current)
>> guix 48f19e6
>> repository URL: https://git.savannah.gnu.org/git/guix.git
>> branch: master
>> commit: 48f19e60c4677e392ee2c23f28098cfcaf9d1710
>>
>> # guix pull
>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>> Building from this channel:
>> guix https://git.savannah.gnu.org/git/guix.git 48f19e6
>> Computing Guix derivation for 'x86_64-linux'... |
>> nothing to be done
>>
>> How to see guix version: 1.0.0 ?
>
> It’s not yet possible. “guile-git” only recently gained support for
> pretty “git describe”-style formats, but there has not been a new
> release of “guile-git” that contains these changes.
>
> Once a new version of “guile-git” becomes available we should be able to
> adjust “guix describe”.
Yup!
But I sympathize: it’s disappointing that ‘guix describe’ doesn’t show
something like:
commit: v1.0.0 \o/ 🙌
Ludo’.
prev parent reply other threads:[~2019-05-03 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 16:19 check guix human readable version znavko
2019-05-02 17:58 ` Tobias Geerinckx-Rice
2019-05-02 22:05 ` Ricardo Wurmus
2019-05-03 9:56 ` Ludovic Courtès [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9yreu8s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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/guix.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).