unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann via Guix-patches via <guix-patches@gnu.org>
To: othacehe@gnu.org, 49659@debbugs.gnu.org
Cc: ludo@gnu.org, maximedevos@telenet.be
Subject: [bug#49659] [PATCH core-updates] gnu: guile: Fix failing tests on i686-linux.
Date: Sun, 25 Jul 2021 20:52:28 -0300	[thread overview]
Message-ID: <5701551.jmBiHemN7o@popigai> (raw)
In-Reply-To: <8735s5cs9q.fsf@gnu.org>

Hello,

Em sexta-feira, 23 de julho de 2021, às 06:07:45 -03, Ludovic Courtès 
escreveu:
> Hi,
> 
> Mathieu Othacehe <othacehe@gnu.org> skribis:
> >> I tweaked the commit log and pushed as
> >> fccc0275091af10a46471c68df525d19f446af9e.
> >> 
> >> Looks like we should be able to move forward with this branch now,
> >> thank you!
> > 
> > Thanks for taking care of that Maxime & Ludo :). Should we create a
> > core-updates-frozen branch that Cuirass would build for the "all"
> > subset? I can take care of that if so.
> 
> There are “two last things” to check IMO:
> 
>   1. Make sure powerpc64le-linux is in a good state.  Can we get it
>      built? (We discussed adding a worker on the OSUOSL machine but I
>      think we eventually dropped the ball.)
> 
>   2. <https://issues.guix.gnu.org/49597> will trigger rebuilds.  I was
>      waiting before applying it so we get several people looking into
>      it; Maxime had valid criticism, I’m interested in hearing from
>      others too.  :-)
> 
> Once we’re OK on these two fronts, let’s branch ‘core-updates-frozen’
> and unleash our package-fixing superpowers!

Perhaps libdrm and Mesa could be updated before the freeze as suggested by 
John Kehayias¹?

Or could/should that be done on a branch apart from core-updates? Not sure 
if that’s what Ricardo’s suggestion about creating a new branch means.

-- 
Thanks,
Thiago

¹ https://lists.gnu.org/archive/html/guix-devel/2021-07/msg00105.html







      parent reply	other threads:[~2021-07-25 23:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 11:27 [bug#49659] [PATCH core-updates] gnu: guile: Fix failing tests on i686-linux Maxime Devos
2021-07-20 13:55 ` Ludovic Courtès
2021-07-20 16:55   ` Maxime Devos
2021-07-20 20:51     ` Ludovic Courtès
2021-07-20 18:22   ` Efraim Flashner
2021-07-20 21:34 ` [bug#49659] [PATCH v2\ core-updates v2] " Maxime Devos
2021-07-21 13:49   ` bug#49659: [PATCH core-updates] " Ludovic Courtès
2021-07-21 14:50     ` [bug#49659] " Mathieu Othacehe
2021-07-23  9:07       ` Ludovic Courtès
2021-07-23  9:27         ` Maxime Devos
2021-07-25 23:52         ` Thiago Jung Bauermann via Guix-patches via [this message]

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=5701551.jmBiHemN7o@popigai \
    --to=guix-patches@gnu.org \
    --cc=49659@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=othacehe@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).