all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.4 (or 2.0): process and schedule ?
Date: Sat, 08 Jan 2022 18:21:58 -0800	[thread overview]
Message-ID: <87mtk5eji1.fsf@gmail.com> (raw)
In-Reply-To: <877dbdrn38.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 06 Jan 2022 08:49:15 -0500")

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

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello Chris,
>
> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>
>>> About the current status, I'm nearing on pushing a version-1.4.0 branch
>>> which is based on master with a few more (core-ish) updates.  There's
>>> still a few days ahead of that, so if you manage to get many of this
>>> kind of problems fixed & merged in master they can easily be included in
>>> the next release.
>>
>> There is a problem that currently prevents "guix pull" from succeeding
>> for powerpc64le-linux on master.  I'd like to resolve it before the
>> release if possible.  The problem is here, including a patch to fix it:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52940
>>
>> [...]
>
> Since the version-1.4.0 branch I've been polishing locally still hasn't
> been published nor built, there's still time to apply the patch without
> any consideration for world rebuilds to that branch (at this point we
> want the changes to be low risk ones though, but that sounds like one).

With Ludo's feedback, I was able to fix 52940 without rebuilding the
world in commit 195bb1fb9d55d8e5187d669c63a3cde747fc5f64 on master.  Can
you try merging master into your version-1.4.0 branch?

At this point in time, I'm unaware of any issues that would be
show-stoppers for for powerpc64le-linux.  As a reminder, issues
important to powerpc64le-linux can be seen by searching for issues
tagged with the "guix" user's powerpc64le-linux Debbugs usertag:

https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?tag=powerpc64le-linux;users=guix

I'll keep my eye out for other potential powerpc64le-linux issues and
see what I can do to help in the days/weeks to come.

Now that the "guix" package is building successfully again on master, I
can finally build up-to-date versions of cuirass and
guix-build-coordinator.  Although it isn't directly related to the
release, I think I will resume my efforts to add a new powerpc64le-linux
node to the build farm.

-- 
Chris

PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836

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

  reply	other threads:[~2022-01-09  2:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15  8:37 Release process and schedule ? zimoun
2021-12-17 10:03 ` Release v1.4 (or 2.0): " zimoun
2021-12-20  2:12   ` Maxim Cournoyer
2021-12-20  3:43     ` raingloom
2021-12-20  9:04     ` zimoun
2021-12-20  9:14       ` zimoun
2021-12-20 21:24       ` Ludovic Courtès
2021-12-20 22:54         ` zimoun
2021-12-20 18:12     ` Bengt Richter
2021-12-21 20:48     ` Vagrant Cascadian
2021-12-21 21:20       ` Vagrant Cascadian
2022-01-03 14:31         ` Ludovic Courtès
2022-01-03 16:32           ` Vagrant Cascadian
2021-12-27  3:46       ` Maxim Cournoyer
2022-01-03 14:33         ` Ludovic Courtès
2022-01-04 16:24           ` Maxim Cournoyer
2022-01-04 19:32         ` Chris Marusich
2022-01-06 13:49           ` Maxim Cournoyer
2022-01-09  2:21             ` Chris Marusich [this message]
2022-01-18  5:05               ` Maxim Cournoyer
2022-01-18 13:20                 ` Ludovic Courtès
2022-01-15 19:26         ` Vagrant Cascadian

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=87mtk5eji1.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --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.