unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Josh <randomenduser@fastmail.com>, 39310@debbugs.gnu.org
Subject: bug#39310: MariaDB reproducibility issue
Date: Mon, 27 Jan 2020 20:21:33 +0100	[thread overview]
Message-ID: <87pnf4so1u.fsf@devup.no> (raw)
In-Reply-To: <f48564ea-f58e-41e1-a29d-faaa68ee1d8f@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Josh <randomenduser@fastmail.com> writes:

> Hi Guix,                                                                                 
>                                                                                          
> I ran into this issue when building mariadb 10.1.38. I've attached the                   
> last 300 lines of the log. Thanks

I can reproduce this failure by checking out Guix 1.0.1 in a "time 
machine" and trying to build MariaDB.  The problem is that the failing test
expects the current time to be earlier than 2020-01-21 15:32:22.

This was properly fixed in 10.1.39[0], at least until the year 2038.

Unfortunately there is little we can do about it now.  If you are
hitting this problem while trying to install Guix 1.0.1, I recommend to
either:

1) enable binary substitutes
2) set the system clock to some time last year while building MariaDB
3) install a minimal configuration that does not pull in MariaDB, and
reconfigure with the "full" configuration once you have 'guix pull'd.

Will that work for you?

Thanks for the report, and sorry for the inconvenience!

[0] https://github.com/MariaDB/server/commit/cfe0fe1ad1f7c75102285d445c3ba8167f5b9c44

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-01-27 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 14:23 bug#39310: MariaDB reproducibility issue Josh
2020-01-27 19:21 ` Marius Bakke [this message]
2021-01-24 16:12   ` Ludovic Courtès
2023-11-01  9:53     ` Christopher Baines

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=87pnf4so1u.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=39310@debbugs.gnu.org \
    --cc=randomenduser@fastmail.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 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).