From: "Ludovic Courtès" <ludo@gnu.org>
To: YOANN P <yoann_mac_donald@hotmail.com>
Cc: "37565@debbugs.gnu.org" <37565@debbugs.gnu.org>
Subject: bug#37565: [use profile manifest] upstream VCS informations only available after a guix pull
Date: Tue, 01 Oct 2019 23:02:56 +0200 [thread overview]
Message-ID: <87muekkwlb.fsf@gnu.org> (raw)
In-Reply-To: <DB6P18901MB002211F120E0F01B6B97A73BDB9D0@DB6P18901MB0022.EURP189.PROD.OUTLOOK.COM> (YOANN P.'s message of "Tue, 1 Oct 2019 12:31:19 +0000")
Hi,
YOANN P <yoann_mac_donald@hotmail.com> skribis:
>>> YOANN P <yoann_mac_donald@hotmail.com> skribis:
>>> Not sure if it should be considerated as a bug but it seems that the upstream VCS information are only available after a "guix pull".
>>
>>You mean that ‘guix describe’ doesn’t work for ‘guix’ not obtained from ‘guix pull’, right?
>>
>
> Not exactly but has the same behavior indeed.
> I was talking about upstream VCS informations in ~/.guix-profile/manifest (user profile manifest)
> Every packages installed with "guix install xxx" from a fresh install ( 1.0.1 in my case ) doesn't have upstream VCS informations in ~/.guix-profile/manifest as you described here ( https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00018.html ).
Ah yes, it’s the same issue as with ‘guix describe’.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-10-01 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 20:31 bug#37565: [use profile manifest] upstream VCS informations only available after a guix pull YOANN P
2019-10-01 9:28 ` Ludovic Courtès
2019-10-01 12:31 ` YOANN P
2019-10-01 21:02 ` 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=87muekkwlb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37565@debbugs.gnu.org \
--cc=yoann_mac_donald@hotmail.com \
/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).