From: Chris Marusich <cmmarusich@gmail.com>
To: Aiko Kyle <aikokyle@gmail.com>
Cc: 52908@debbugs.gnu.org
Subject: bug#52908: 'tests/guix-system.sh' fails on aarch64-linux
Date: Mon, 03 Jan 2022 20:53:22 -0800 [thread overview]
Message-ID: <87bl0s5cfx.fsf@gmail.com> (raw)
In-Reply-To: <CAPWcbYHDLkQxxO4Y+Z=FCC6jDprUm_NfYF1rBDaJDn40KP+Duw@mail.gmail.com> (Aiko Kyle's message of "Mon, 3 Jan 2022 20:43:27 -0700")
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Hi Aiko,
Aiko Kyle <aikokyle@gmail.com> writes:
> Commit 9309b48 seems to be a week old and I can't seem to apply this
> patch on top of the latest commit on master e6fe4e5819.
How did you apply the patch? I was able to apply the patch locally to
commit 80ebf564e3e264a006d7c7b1f7f2e57fc2468ef1 (".guix-authorizations:
Remove Miguel Ángel Arruga Vivas due to inactivity."), which is
currently the latest commit on master.
I applied by patch by saving the MIME part to a file named "/tmp/patch".
Then I ran the following command from a clean Git checkout of commit
80ebf564e3e264a006d7c7b1f7f2e57fc2468ef1:
git am /tmp/patch
For the record, the SHA-256 hash value of the patch file is
6650872d41068f6031633d2720553eeb05e7d650a51723dfdd2a3c2df3df294e. If
you run "sha256sum /tmp/patch", do you see the same hash value?
--
Chris
PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-01-04 4:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 23:52 bug#52908: 'tests/guix-system.sh' fails on aarch64-linux Leo Famulari
2022-01-04 2:15 ` Chris Marusich
2022-01-04 3:43 ` Aiko Kyle
2022-01-04 4:53 ` Chris Marusich [this message]
2022-01-04 5:08 ` Aiko Kyle
2022-01-05 9:58 ` Chris Marusich
2022-01-05 10:47 ` Pierre Langlois
2022-01-06 7:28 ` Chris Marusich
2022-01-05 17:34 ` Aiko Kyle
2022-01-04 17:28 ` Leo Famulari
2022-01-06 16:39 ` Ludovic Courtès
2022-01-07 4:32 ` Chris Marusich
2022-01-07 10:48 ` Maxime Devos
2022-01-09 4:42 ` Chris Marusich
2022-01-08 1:26 ` Aiko Kyle
2022-01-08 2:18 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl0s5cfx.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=52908@debbugs.gnu.org \
--cc=aikokyle@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.