From: indieterminacy <indieterminacy@libre.brussels>
To: jgart <jgart@dismail.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: How do I verify my hashes?
Date: Sun, 10 Jul 2022 15:25:36 +0200 [thread overview]
Message-ID: <aaef1d732224fd534010bb70d1b10dc9@libre.brussels> (raw)
In-Reply-To: <20220709211259.GB25347@gac>
On 10-07-2022 04:12, jgart wrote:
> Hi Guixers,
>
> Today Bonface mentioned to me that I should be cloning my packages and
> verifying the hashes with `git hash-object` or `git hash` iirc?
>
Bonface gives very cogent demonstrations of workflow, encourage him to
do a screencast!
> Do others do this when packaging?
>
> My workflow currently is the lazy way:
>
> 1. I change the version in the package definition.
>
> 2. build the package
>
> 3. package blows up on stdout
>
> 4. I retrieve the hash and add it
>
> 5. profit!
>
> But how can I trust that computed hash?
>
> wdyt
Im slowly moving up the value-chain with my usage of Emacs' Git
porceline, Magit.
IMHO, the ultimate experience would be for everything operating from
Magit's interface - for the beneficence of Guix.
>
> Am I committing a newbie sin with the above workflow?
>
> I know `guix refresh` exists but sometimes it is slowwww (e.g. outdated
> *.go)
>
> I know `make go-clean` exists but sometimes it breaks things in my
> tree...
>
> Should I stop worrying and just `git send-email
> --to="guix-patches@gnu.org" -1`?
>
> all best,
>
> jgart
--
Jonathan McHugh
indieterminacy@libre.brussels
next prev parent reply other threads:[~2022-07-10 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 2:12 How do I verify my hashes? jgart
2022-07-10 4:13 ` Vagrant Cascadian
2022-07-10 10:09 ` Csepp
2022-07-10 13:25 ` indieterminacy [this message]
2022-07-10 16:59 ` jgart
2022-07-14 8:52 ` Munyoki Kilyungi
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=aaef1d732224fd534010bb70d1b10dc9@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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).