From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Mortimer Cladwell <mbcladwell@gmail.com>
Cc: Timothy Sample <samplet@ngyro.com>, help-guix@gnu.org
Subject: Re: How to use guix hash --serializer?
Date: Tue, 04 Jan 2022 20:57:02 +0100 [thread overview]
Message-ID: <87fsq3uuyc.fsf@nckx> (raw)
In-Reply-To: <CAOcxjM6P+P5kLXbtGETkmBugBtgVDFVej40rcisBYvARyrn9qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Hi Mortimer,
This is no bug:
> expected hash:
> 1ykbpz6pqx0bkvfp3c60qfb9r0xvpmrs0ldlxm2qw0zd8f67lmaj
> actual hash:
> 10nfjllq28jrzxd4dfqm6xzx8f2g1m6p2vivzihxc7d3ac1imnk2
It really means you're not hashing what you think you're hashing
and it won't matter which arguments you give ‘guix hash’: garbage
in, garbage out :-)
You probably have untracked files laying around. Reset your local
checkout, or start again:
/tmp λ git clone git://github.com/mbcladwell/shinyln.git
Cloning into 'shinyln'...
remote: Enumerating objects: 74, done.
remote: Counting objects: 100% (74/74), done.
remote: Compressing objects: 100% (48/48), done.
remote: Total 74 (delta 34), reused 59 (delta 19), pack-reused 0
Receiving objects: 100% (74/74), 34.75 KiB | 444.00 KiB/s, done.
Resolving deltas: 100% (34/34), done.
/tmp λ cd shinyln
/tmp/shinyln master λ git reset --hard
9f06568ffa61953ab48c93e1623d88b4e672af42
HEAD is now at 9f06568 removed chmod statement
/tmp/shinyln master λ guix hash -S nar -x .
10nfjllq28jrzxd4dfqm6xzx8f2g1m6p2vivzihxc7d3ac1imnk2
The ‘-S git’ bug you found does not affect this.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-01-04 20:06 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 [this message]
2022-01-04 19:58 ` Mortimer Cladwell
2022-01-04 20:17 ` zimoun
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=87fsq3uuyc.fsf@nckx \
--to=me@tobias.gr \
--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).