From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Mathieu Othacehe" <othacehe@gnu.org>
Cc: 44835-done@debbugs.gnu.org
Subject: bug#44835: gnu/ci.go: Embeds build path, breaking reproducible builds
Date: Thu, 07 Mar 2024 13:46:01 -0800 [thread overview]
Message-ID: <875xxxogva.fsf@wireframe> (raw)
In-Reply-To: <87o8jbdnvb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On 2020-12-03, Ludovic Courtès wrote:
> Mathieu Othacehe <othacehe@gnu.org> skribis:
>
>>> … but I don’t think we can assume that the checkout is in the
>>> ‘%load-path’ when this code is executed. WDYT, Mathieu?
>>
>> Cuirass happens to add checkouts to the %load-path just before loading
>> this file.
>
> Is that systematic? Isn’t it only when ‘load_path_inputs’ is non-empty?
>
>> I tested your path, it works fine. I think it is acceptable as this (gnu
>> ci) interface needs a big rework anyway.
>>
>> I can apply your patch if it's ok for you.
>
> Sure if you’re confident you can go ahead. :-)
This looks to have been fixed some time ago in:
76bea3f8bcd951ded88dfb7f8cad5bc3e5a1701f ci: Remove hydra support.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2024-03-07 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r1ojgzdh.fsf@yucca>
2020-11-26 21:39 ` bug#44835: gnu/ci.go: Embeds build path, breaking reproducible builds Ludovic Courtès
2020-12-01 9:41 ` Mathieu Othacehe
2020-12-03 13:23 ` Ludovic Courtès
2024-03-07 21:46 ` Vagrant Cascadian [this message]
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=875xxxogva.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=44835-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).