From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>, ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: Let's build 'core-updates'!
Date: Tue, 07 Nov 2017 07:59:14 -0500 [thread overview]
Message-ID: <9DFCCDF5-5F5F-4352-B68F-72C5CED46DC7@famulari.name> (raw)
In-Reply-To: <31DBE911-B1AD-430B-AE11-71BDC382D848@flashner.co.il>
To clarify, I haven't built anything on core-updates yet, so I don't know if this will fail on x86_64. I'm still cherry picking things to master in order to test.
Sorry for top-posting
-------- Original Message --------
From: Efraim Flashner <efraim@flashner.co.il>
Sent: November 7, 2017 6:05:19 AM EST
To: ludo@gnu.org
Cc: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Let's build 'core-updates'!
No one else mentioned it after the acl tests were enabled
On November 7, 2017 11:54:47 AM GMT+02:00, ludo@gnu.org wrote:
>Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> /gnu/store/mivyzxijvxh44g2r39071sm89vm9h0n6-make-boot0-4.2.1/bin/make
>-C test/ tests
>> make[1]: Entering directory
>'/tmp/guix-build-acl-2.2.52.drv-0/acl-2.2.52/test'
>> *** malformed-restore.test ***
>> Unescaped left brace in regex is illegal here in regex; marked by <--
>HERE in m/%{ <-- HERE (\w+)}/ at run line 73.
>> make[1]: *** [Makefile:39: malformed-restore.test] Error 255
>> make[1]: Leaving directory
>'/tmp/guix-build-acl-2.2.52.drv-0/acl-2.2.52/test'
>
>This looks like the new regex syntax issue introduced on the last Perl
>update we made, no? Is it really aarch64-specific?
>
>Ludo’.
next prev parent reply other threads:[~2017-11-07 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 20:33 Let's build 'core-updates'! Marius Bakke
2017-11-02 21:29 ` Efraim Flashner
2017-11-03 12:20 ` Leo Famulari
2017-11-06 11:03 ` Efraim Flashner
2017-11-07 9:54 ` Ludovic Courtès
2017-11-07 11:05 ` Efraim Flashner
2017-11-07 12:59 ` Leo Famulari [this message]
2017-11-09 10:09 ` Ludovic Courtès
2017-11-06 8:56 ` Ludovic Courtès
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=9DFCCDF5-5F5F-4352-B68F-72C5CED46DC7@famulari.name \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@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).