unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: 30390@debbugs.gnu.org
Subject: [bug#30390] [PATCH 0/3] Update cmake.
Date: Sat, 24 Feb 2018 18:38:46 +0530	[thread overview]
Message-ID: <20180224130849.8886-1-arunisaac@systemreboot.net> (raw)
In-Reply-To: <20180208121323.14840-1-arunisaac@systemreboot.net>

I have added rhash and pushed it to master. Unfortunately, it became two
commits, instead of just one, due to my sloppiness.

All other changes you mentioned are done. Please find below the new patches.

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.

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.

Arun Isaac (3):
  gnu: sqlite: Fix source URI.
  gnu: cmake: Update to 3.10.2.
  gnu: cmake: Re-indent.

 gnu/local.mk                               |   1 -
 gnu/packages/cmake.scm                     | 154 ++++++++++++++++-------------
 gnu/packages/databases.scm                 |   2 +-
 gnu/packages/patches/cmake-fix-tests.patch | 120 ----------------------
 4 files changed, 85 insertions(+), 192 deletions(-)
 delete mode 100644 gnu/packages/patches/cmake-fix-tests.patch

-- 
2.15.1

  parent reply	other threads:[~2018-02-24 13:10 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 ` Arun Isaac [this message]
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   ` [bug#30390] [PATCH 0/3] Update cmake Marius Bakke
2018-02-24 19:06     ` 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=20180224130849.8886-1-arunisaac@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=30390@debbugs.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).