all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 53214@debbugs.gnu.org
Cc: "Vagrant Cascadian" <vagrant@debian.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Leo Famulari" <leo@famulari.name>
Subject: bug#53214: Release 1.4.0 progress
Date: Sat, 29 Jan 2022 22:00:18 -0300	[thread overview]
Message-ID: <58790588.DlEEdIX8SL@popigai> (raw)
In-Reply-To: <87y22yqdhe.fsf@ponder>

Hello,

Em sábado, 29 de janeiro de 2022, às 21:22:21 -03, Vagrant Cascadian 
escreveu:
> On 2022-01-29, Leo Famulari wrote:
> > The build farm is having trouble building Guix for i686-linux. In fact,
> > it hasn't successfully completed the 'guix' job in weeks:
> > 
> > https://issues.guix.gnu.org/53463
> > 
> > And building the guix package does not work on aarch64, also for weeks:
> > 
> > https://issues.guix.gnu.org/52943
> 
> It does work on my aarch64 machine as of
> 1ef7a03a148cf5f83ab1820444f6bd50d8e732d1 and more recently
> f8bfb2d85682dcabe56a4b1b0f25d566a0abbd2b, but not sure why it's not
> building on the build farm...

A couple of weeks ago guixp9 wasn’t doing powerpc64le builds either.
I did a “guix pull && guix upgrade” (which upgraded the version of Cuirass 
installed) and restarted the Cuirass worker then things got back on track 
again. I don’t know why...

-- 
Thanks,
Thiago






  reply	other threads:[~2022-01-30  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 17:32 bug#53214: Release 1.4.0 progress Ludovic Courtès
2022-01-26  4:20 ` Leo Famulari
2022-01-29 21:11   ` Leo Famulari
2022-01-30  0:22     ` Vagrant Cascadian
2022-01-30  1:00       ` Thiago Jung Bauermann via Bug reports for GNU Guix [this message]
2022-02-01  8:34     ` Ludovic Courtès
2022-02-03 17:46 ` Leo Famulari

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=58790588.DlEEdIX8SL@popigai \
    --to=bug-guix@gnu.org \
    --cc=53214@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    --cc=vagrant@debian.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 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.