From: Mortimer Cladwell <mbcladwell@gmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to use guix hash --serializer?
Date: Tue, 4 Jan 2022 14:58:19 -0500 [thread overview]
Message-ID: <CAOcxjM4YC58pLavs5Dw=928GOvUt7p-9qBBQcO4rShPJdfTqtw@mail.gmail.com> (raw)
In-Reply-To: <CAOcxjM6P+P5kLXbtGETkmBugBtgVDFVej40rcisBYvARyrn9qg@mail.gmail.com>
So I am seeing the result for guix hash -S . which is wrong, but when the
bug is fixed I will get the results for
guix hash -S -x .
Is that what you are implying?
Thanks
Mortimer
On Tue, Jan 4, 2022 at 2:48 PM Mortimer Cladwell <mbcladwell@gmail.com>
wrote:
> Thanks Tim, Simon, but that does not work for me.
>
> ====nar==============
> mbc@HP8300:~/projects$ guix hash -S nar -x ./shinyln
> 1ykbpz6pqx0bkvfp3c60qfb9r0xvpmrs0ldlxm2qw0zd8f67lmaj
> mbc@HP8300:~/projects$ cd shinyln/
> mbc@HP8300:~/projects/shinyln$ guix hash -S nar -x .
> 1ykbpz6pqx0bkvfp3c60qfb9r0xvpmrs0ldlxm2qw0zd8f67lmaj
>
> ====git==================
> mbc@HP8300:~/projects/shinyln$ guix hash -S git -x .
> 0lai57r0p11q041b3flriv56j6n8lizwb69yv7j396yiivkspv3x
> mbc@HP8300:~/projects/shinyln$ cd ..
> mbc@HP8300:~/projects$ guix hash -S git -x ./shinyln
> 0lai57r0p11q041b3flriv56j6n8lizwb69yv7j396yiivkspv3x
>
> ====error during packaging=============
> building /gnu/store/2a2016wffiy0cwvayvsz64r1f88k05mg-git-checkout.drv...
> \r:sha256 hash mismatch for
> /gnu/store/w2sl6n4jnbhzs8qp1k4lff35h1yml2c4-git-checkout:
> expected hash: 1ykbpz6pqx0bkvfp3c60qfb9r0xvpmrs0ldlxm2qw0zd8f67lmaj
> actual hash: 10nfjllq28jrzxd4dfqm6xzx8f2g1m6p2vivzihxc7d3ac1imnk2
>
> So seems like it doesn't matter whether I am inside or outside the
> directory I get the same hash (reasonable).
> Neither git nor nar provide the correct hash
>
> 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.
>
> Thanks
>
> Mortimer
>
>
>
>
>
>
>
> On Tue, Jan 4, 2022 at 2:09 PM Timothy Sample <samplet@ngyro.com> wrote:
>
>> Hi zimoun,
>>
>> zimoun <zimon.toutoune@gmail.com> writes:
>>
>> > Indeed,
>> >
>> > $ guix hash -S git foo -x
>> > 0czq9304mdv9f2j6a8cdi9855sl8w595p06c1m8bn9pg391lhcal
>> > $ guix hash -S git foo
>> > 0czq9304mdv9f2j6a8cdi9855sl8w595p06c1m8bn9pg391lhcal
>> >
>> > Hum, I will check if it is expected.
>>
>> I’m pretty sure it’s a bug. Fortunately, with Disarchive 0.4.0, the
>> following (untested) patch should fix it:
>>
>>
>> Hope that helps!
>>
>>
>> -- Tim
>>
>
next prev parent reply other threads:[~2022-01-04 19:58 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 [this message]
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='CAOcxjM4YC58pLavs5Dw=928GOvUt7p-9qBBQcO4rShPJdfTqtw@mail.gmail.com' \
--to=mbcladwell@gmail.com \
--cc=help-guix@gnu.org \
--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).