all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Subject: Re: check guix human readable version
Date: Thu, 02 May 2019 19:58:29 +0200	[thread overview]
Message-ID: <87v9ysu4ai.fsf@nckx> (raw)
In-Reply-To: <925509d741ad7d71821e7a77a55f67bb@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

Znavko,

znavko@disroot.org wrote:
> 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:

This won't help you, but I can confirm:

  ~ λ guix describe
  Generation 43	May 02 2019 19:51:49	(current)
    nckx 22adf20
      repository URL: file:///home/nckx/nckx-chan
      branch: master
      commit: 22adf2056ce9bc9b32845c61e7426f595a5f451f
    guix 48f19e6
      repository URL: https://git.savannah.gnu.org/git/guix.git
      branch: master
      commit: 48f19e60c4677e392ee2c23f28098cfcaf9d1710

I'm pretty sure that it's supposed to work off of the most recent 
tag (like its namesake ‘git describe’), and am almost certain that 
it used to, so this is probably ‘just’ a bug & you're using the 
correct command :-)

Kind regards,

T G-R

PS: I'm low on bandwidth or I'd find out what ‘guix pull 
--commit=<much earlier commit…> && git describe’ produces.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-05-02 17:58 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 [this message]
2019-05-02 22:05 ` Ricardo Wurmus
2019-05-03  9:56   ` Ludovic Courtès

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=87v9ysu4ai.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.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.