unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Mortimer Cladwell <mbcladwell@gmail.com>,
	Timothy Sample <samplet@ngyro.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to use guix hash --serializer?
Date: Tue, 04 Jan 2022 21:17:06 +0100	[thread overview]
Message-ID: <86mtkbcl31.fsf@gmail.com> (raw)
In-Reply-To: <CAOcxjM6P+P5kLXbtGETkmBugBtgVDFVej40rcisBYvARyrn9qg@mail.gmail.com>

Hi Mortimer,

On Tue, 04 Jan 2022 at 14:48, Mortimer Cladwell <mbcladwell@gmail.com> wrote:

> mbc@HP8300:~/projects$ cd shinyln/
> mbc@HP8300:~/projects/shinyln$ guix hash -S nar -x .
> 1ykbpz6pqx0bkvfp3c60qfb9r0xvpmrs0ldlxm2qw0zd8f67lmaj

Could you report:

  git --no-pager log -1 --oneline
  git status

?

> FYI from https://guix.gnu.org/manual/en/html_node/Invoking-guix-hash.html
> at the bottom explaining --exclude-vcs:
>
> $ git clone http://example.org/foo.git
> $ cd foo
> $ guix hash -rx .
>
> Suggests (to me) that you go inside the directory to calculate hash,
> though as above seems not to matter.

Yes, indeed.  I tried outside without fulling checking. :-)


Cheers,
simon


  parent reply	other threads:[~2022-01-04 20:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:32 How to use guix hash --serializer? Mortimer Cladwell
2022-01-04 16:53 ` zimoun
2022-01-04 19:09   ` Timothy Sample
2022-01-04 19:48     ` Mortimer Cladwell
2022-01-04 19:57       ` Tobias Geerinckx-Rice
2022-01-04 19:58       ` Mortimer Cladwell
2022-01-04 20:17       ` zimoun [this message]
2022-01-04 20:44         ` Mortimer Cladwell
2022-01-04 20:57           ` Tobias Geerinckx-Rice
2022-01-04 21:02           ` zimoun
2022-01-04 21:16             ` Mortimer Cladwell
2022-01-04 20:54     ` zimoun
2022-01-05  1:44       ` Timothy Sample
2022-01-05  7:43         ` zimoun

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=86mtkbcl31.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mbcladwell@gmail.com \
    --cc=samplet@ngyro.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. 
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).