unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>, 30390@debbugs.gnu.org
Subject: [bug#30390] [PATCH 0/3] Update cmake.
Date: Sat, 24 Feb 2018 16:16:19 +0100	[thread overview]
Message-ID: <87371qa058.fsf@fastmail.com> (raw)
In-Reply-To: <20180224130849.8886-1-arunisaac@systemreboot.net>

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

Arun Isaac <arunisaac@systemreboot.net> writes:

> Test 92 of tar 1.30 fails on my system. I had to disable tar tests to get my
> cmake to build. I am not entirely sure if the test failure has got something
> to do with insufficient memory on my system. So, I'd like somebody to
> reproduce the problem before patching it.

That test fails on one of my build nodes with 64GB RAM as well.

There is a bug report about it upstream:
<https://lists.gnu.org/archive/html/bug-tar/2017-12/msg00026.html>.

However, the suggested fix does not work for me (I think it requires
running autoreconf, but haven't tried that yet).

> I'm a little confused now. Shouldn't I rebase the core-updates branch against
> master in order to have rhash? Wouldn't this disrupt the evaluation of
> core-updates on the build farm? Sorry I'm not very clear about how we handle
> core-updates.

We don't rebase 'live' branches.  The best way is to merge master, or
you could cherry-pick the patches.  I can merge it later if you're not
comfortable doing it :-)

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

  parent reply	other threads:[~2018-02-24 15:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 12:13 [bug#30390] [PATCH 0/3] Update cmake to 3.10.2 Arun Isaac
2018-02-08 12:17 ` [bug#30390] [PATCH 1/3] gnu: Add rhash Arun Isaac
2018-02-08 12:17   ` [bug#30390] [PATCH 2/3] gnu: libuv: Update to 1.19.1 Arun Isaac
2018-02-20 17:46     ` Marius Bakke
2018-02-08 12:17   ` [bug#30390] [PATCH 3/3] gnu: cmake: Update to 3.10.2 Arun Isaac
2018-02-20 17:54     ` Marius Bakke
2018-02-20 17:44   ` [bug#30390] [PATCH 1/3] gnu: Add rhash Marius Bakke
2018-02-22 14:42     ` Arun Isaac
2018-02-22 14:48       ` Marius Bakke
2018-02-24 13:08 ` [bug#30390] [PATCH 0/3] Update cmake Arun Isaac
2018-02-24 13:08   ` [bug#30390] [PATCH 1/3] gnu: sqlite: Fix source URI Arun Isaac
2018-02-24 13:08   ` [bug#30390] [PATCH 2/3] gnu: cmake: Update to 3.10.2 Arun Isaac
2018-02-24 13:08   ` [bug#30390] [PATCH 3/3] gnu: cmake: Re-indent Arun Isaac
2018-02-24 15:16   ` Marius Bakke [this message]
2018-02-24 19:06     ` [bug#30390] [PATCH 0/3] Update cmake Arun Isaac
2018-02-24 21:17       ` Marius Bakke
2018-02-27 17:20     ` Ludovic Courtès
2018-02-24 15:19   ` Marius Bakke
2018-03-20 10:41     ` Marius Bakke
2018-03-21 21:38       ` Arun Isaac
2018-03-23  6:25         ` bug#30390: " Arun Isaac

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=87371qa058.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=30390@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).