all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>,
	60931@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: [bug#60931] [PATCH] gnu: pari-gp: Update to 2.15.2.
Date: Sun, 22 Jan 2023 17:07:11 +0100	[thread overview]
Message-ID: <864jsi1rkg.fsf@gmail.com> (raw)
In-Reply-To: <Y8fbkCWrmB3toYx8@jurong>

Hi Andreas,

On Wed, 18 Jan 2023 at 12:44, Andreas Enge <andreas@enge.fr> wrote:
> * gnu/packages/algebra.scm (pari-gp): Update to 2.15.2.
> ---
>  gnu/packages/algebra.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Following this discussion [1] about commit policy, you can see the
result of the QA for this update here:

    https://qa.guix.gnu.org/issue/60931

where the patch has been built on several architectures and the
dependants too.

Well, there is two failures [2] for i686-linux.  But it is not
introduced by this patch, somehow it is related to Bordeaux.  For
example, ’giac’ fails:

https://data.guix.gnu.org/repository/1/branch/master/package/giac/output-history?output=out&system=i686-linux&target=none

but passes on Berlin:

https://ci.guix.gnu.org/build/303080/details

What is intriguing is the difference of derivation hashes between the 2
build farms.

Chris, an idea?

Aside, it appears to me that enough green are around for pushing. :-)


Cheers,
simon


2: https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=238f965c331990459a69cbc713ca951ad40e6044&target_commit=07ea16b0399444855b90d566e7a1c7c038142b4a&system=i686-linux&target=none




  reply	other threads:[~2023-01-22 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 11:44 [bug#60931] [PATCH] gnu: pari-gp: Update to 2.15.2 Andreas Enge
2023-01-22 16:07 ` Simon Tournier [this message]
2023-01-22 17:07 ` bug#60931: Close Andreas Enge

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864jsi1rkg.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=60931@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=mail@cbaines.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.