Hi,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> I lost track of the details -- is this problem still likely to bite us
>> in the future, or was something committed to mitigate against it?
>
> “Time bombs” are the worst of non-reproducibility bugs because (1) we
> don’t have
Hi,
Maxim Cournoyer skribis:
> I lost track of the details -- is this problem still likely to bite us
> in the future, or was something committed to mitigate against it?
“Time bombs” are the worst of non-reproducibility bugs because (1) we
don’t have workarounds other than changing the system
Hi everyone,
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> Ludovic Courtès writes:
>>
>>> Perhaps we could start by testing this hypothesis on a separate build
>>> farm. Chris, Mathieu, WDYT?
>>
>> I'm currently thinking about attempting these kind of things (testing
>>
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> Ludovic Courtès writes:
>>
>>> Perhaps we could start by testing this hypothesis on a separate build
>>> farm. Chris, Mathieu, WDYT?
>>
>> I'm currently thinking about attempting these kind of things (testing
>> building
Hi,
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> Perhaps we could start by testing this hypothesis on a separate build
>> farm. Chris, Mathieu, WDYT?
>
> I'm currently thinking about attempting these kind of things (testing
> building derivations under different conditions)
Ludovic Courtès writes:
> Perhaps we could start by testing this hypothesis on a separate build
> farm. Chris, Mathieu, WDYT?
I'm currently thinking about attempting these kind of things (testing
building derivations under different conditions) through the agent tags
in the Guix Build
It occurred to me that, just like we have childhurds, we could provide a
service that sets up a sub-Guix System running in a VM with its clock
set years ahead, and you would offload to that. That’s not perfect, but
it’s a rather easy addition.
Another option would be to have built-in support in
Hi,
Maxime Devos skribis:
> On Fri, 2021-02-19 at 16:33 +0100, Ludovic Courtès wrote:
>> [...]
>> Longer-term, we need to find a way to address or avoid this issue. A
>> brute-force approach would be to have the build machines at ci.guix run
>> with a clock ten years ahead. That should
Hi Guix!
Thanks to all of you for your thoughtful replies!
On Feb 19, 2021, at 10:33 AM, Ludovic Courtès wrote:
> I agree it’s a problem, and yes, it would probably be a good idea to
> release 1.2.1 with the upgraded GnuTLS we now have in ‘master’.
I’m very heartened by your affirmation of the
Hi Guix,
On Fri, 2021-02-19 at 16:33 +0100, Ludovic Courtès wrote:
> [...]
> Longer-term, we need to find a way to address or avoid this issue. A
> brute-force approach would be to have the build machines at ci.guix run
> with a clock ten years ahead. That should generally be fine since the
>
Hi Carl,
Carl Dong skribis:
> As bitcoin core begins the planning to officially transition to Guix-based
> releases, I've had many community members build guix v1.2.0 from source and
> afterward attempt `--bootstrap --no-substitutes` builds. As you may imagine,
> they are getting stuck on
On Tue, Feb 16, 2021 at 04:00:11PM -0500, Carl Dong wrote:
> Hi all,
>
> As bitcoin core begins the planning to officially transition to Guix-based
> releases, I've had many community members build guix v1.2.0 from source and
> afterward attempt `--bootstrap --no-substitutes` builds. As you may
Hi all,
As bitcoin core begins the planning to officially transition to Guix-based
releases, I've had many community members build guix v1.2.0 from source and
afterward attempt `--bootstrap --no-substitutes` builds. As you may imagine,
they are getting stuck on this gnutls problem and cannot
I created a procedure to work around the build failure and enable a
successful build:
# when gnutls-3.6.12 build breaks you need to do:
# run the following as root
# turn off networking
ip link set enp0s25 down
# Fixup the time so that the build will succeed
timedatectl set-ntp false
timedatectl
Hi,
Marius Bakke skribis:
> Ludovic Courtès writes:
>
>> The question for us becomes how to ensure long-term reproducibility in
>> the presence of such bugs.
>>
>> In this case, I think the only solution would be to change the system
>> clock when one rebuilds GnuTLS (or to use
Ludovic Courtès writes:
> The question for us becomes how to ensure long-term reproducibility in
> the presence of such bugs.
>
> In this case, I think the only solution would be to change the system
> clock when one rebuilds GnuTLS (or to use ‘--without-tests=gnutls’, but
> you end up with
Hi,
Christopher Baines skribis:
> I found this when trying to build guile3.0-gnutls:
>
> guix time-machine --commit=94585fffb23079fe71110e2bf99782eb4ccfa12b --
> build --no-grafts --check guile3.0-gnutls
>
>
> FAIL: status-request-revoked
>
>
> trying
I found this when trying to build guile3.0-gnutls:
guix time-machine --commit=94585fffb23079fe71110e2bf99782eb4ccfa12b -- build
--no-grafts --check guile3.0-gnutls
FAIL: status-request-revoked
trying NORMAL:-VERS-ALL:+VERS-TLS1.2
received status request
18 matches
Mail list logo
