From: Leo Famulari <leo@famulari.name>
To: Tomas Volf <~@wolfsden.cz>
Cc: Wilko Meyer <w@wmeyer.eu>,
69105-done@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#69105: [PATCH] gnu: linux-libre-documentation: Fix compilation.
Date: Tue, 20 Feb 2024 20:34:45 -0500 [thread overview]
Message-ID: <ZdVTNQmSL3UQhIfG@jasmine.lan> (raw)
In-Reply-To: <ZdTvfJi0eN6nS1Nc@ws>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Tue, Feb 20, 2024 at 07:29:16PM +0100, Tomas Volf wrote:
> I see, I guess it was a mistake trying to fetch the patch in this way. I've
> sent a v2 that just adds it into the patches/ directory. I hope that will work
> fine.
I double-checked the hash and your original patch had the correct value.
For some reason, when the build farm tried to download the patch file
from the kernel infrastructure, the wrong data was received and the hash
did not match.
But when I downloaded the patch file "by hand" with `curl`, I received
the expected data.
Then, I applied your patch to a checkout of guix.git and successfully
built linux-libre-documentation with `./pre-inst-env [...]`.
So, I think your original patch is good.
Sometimes these transient errors occur. Including the patch directly in
our repo would be more reliable than fetching it, but there is the minor
negative effect of increasing the size of our codebase. I chose to fetch
the data in this case.
Thank you very much for working on this bug!
Patch version 1 pushed as b6f82b9ef1a3d51a39995598eab9f793656e9123
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-21 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 16:22 [bug#69105] [PATCH] gnu: linux-libre-documentation: Fix compilation Tomas Volf
2024-02-18 22:46 ` Leo Famulari
2024-02-20 16:56 ` Leo Famulari
2024-02-20 18:29 ` Tomas Volf
2024-02-21 1:34 ` Leo Famulari [this message]
2024-02-20 18:26 ` [bug#69105] [PATCH v2] " Tomas Volf
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=ZdVTNQmSL3UQhIfG@jasmine.lan \
--to=leo@famulari.name \
--cc=69105-done@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=w@wmeyer.eu \
--cc=~@wolfsden.cz \
/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.