From: Bengt Richter <bokr@bokr.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 42212@debbugs.gnu.org
Subject: bug#42212: Guix version rendered as 0.0-git in info manual
Date: Thu, 16 Jul 2020 02:46:00 +0200 [thread overview]
Message-ID: <20200716004600.GA3021@LionPure> (raw)
In-Reply-To: <871rlczc8i.fsf@systemreboot.net>
On +2020-07-16 03:12:37 +0530, Arun Isaac wrote:
>
> > The “0.0-git” string comes from (guix self). As noted there, we can’t
> > really afford to change the version string at each commit, or we’d have
> > to rebuild the manual at each commit.
> >
> > We could perhaps choose a more meaningful version string, though, maybe
> > by looking at the closest tag or something.
>
> That sounds good, and `git describe` could provide us with the closest
> tag. Unfortunately, (git) doesn't seem to be available during `guix
> pull`. I'm trying to come up with workarounds. Do you have any ideas?
What does (copied from another laptop screen by hand, typos possible ;)
--8<---------------cut here---------------start------------->8---
readlink -f /var/guix/profiles/per-user/{$USER,root}/current-guix/manifest|xargs grep -m1 -A1 guix
--8<---------------cut here---------------end--------------->8---
get you? Anything useful?
On my other laptop, it got me (again copied/...elided from other screen)
--8<---------------cut here---------------start------------->8---
/gnu/store/.../manifest: (("guix"
/gnu/store/.../manifest- "87850c0"
--
/gnu/store/.../manifest: (("guix"
/gnu/store/.../manifest- "0.16.0"
--8<---------------cut here---------------end--------------->8---
You can see that's ancient, so IDK if the same command will work for you.
"guix -V" there still shows 0.16.0 (which version should that show, BTW?)
I don't know how these versions correspond to what pull creates,
but zimoun is a whiz on that stuff, so maybe he will chime in :)
(I Cc'd him to raise the probability :)
HTH
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-07-16 0:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 7:59 bug#42212: Guix version rendered as 0.0-git in info manual Arun Isaac
2020-07-09 22:29 ` Ludovic Courtès
2020-07-15 21:42 ` Arun Isaac
2020-07-15 23:26 ` Ludovic Courtès
2020-07-16 0:46 ` Bengt Richter [this message]
2020-07-16 5:08 ` Bengt Richter
2020-07-16 10:06 ` zimoun
2020-07-16 9:37 ` zimoun
2020-07-16 9:48 ` Ludovic Courtès
2020-07-16 10:19 ` zimoun
2020-07-16 19:36 ` Efraim Flashner
2020-07-17 23:55 ` bug#42212: [PATCH 0/1] Use nearest tag as the version string in documentation Arun Isaac
2020-07-17 23:55 ` bug#42212: [PATCH 1/1] self: " Arun Isaac
2020-07-20 8:13 ` Ludovic Courtès
2020-07-20 8:36 ` Arun Isaac
2020-07-20 12:32 ` Ludovic Courtès
2020-07-20 13:42 ` zimoun
2020-07-27 23:13 ` bug#42212: [PATCH v2 0/1] " Arun Isaac
2020-07-27 23:13 ` bug#42212: [PATCH v2 1/1] " Arun Isaac
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=20200716004600.GA3021@LionPure \
--to=bokr@bokr.com \
--cc=42212@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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).