From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Thursday 18th: ‘core-updates-frozen’ sprint!
Date: Mon, 22 Nov 2021 14:19:55 +0100 [thread overview]
Message-ID: <87v90knx8k.fsf@gnu.org> (raw)
In-Reply-To: <87bl2fitwl.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 19 Nov 2021 23:43:29 +0000")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> … there’s probably more.
>
> I noticed that we’re still using PYTHONPATH in a bunch of places, even
> though we should now be using GUIX_PYTHONPATH. I’ve been slowly
> hacking away at the remaining offenders.
I see you fixed a bunch of them, yay!
> That said, it’s amazing how much progress we made in so little time!
> I’ll continue to prioritize core-updates-frozen for the next few days.
Yes, let’s do that. I’ve fixed things I’ll probably never ever use,
like trytond. A call to everyone though: make sure your favorite
packages work because you can’t necessarily count on others to test it
and fix it. :-)
I’ve noticed Python packages still failing so if you rely on Python,
better be safe than sorry.
>>> Nov. 23th will mark Guix’s 9th birthday. Wouldn’t it be great to
>>> have
>>> that branch finally merged in ‘master’ by then?
>>
>> Sounds doable, let’s keep up the good work!
>
> I hope we can make it!
Yup, let’s see!
Ludo’.
next prev parent reply other threads:[~2021-11-22 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:46 Thursday 18th: ‘core-updates-frozen’ sprint! Ludovic Courtès
2021-11-17 12:06 ` Ricardo Wurmus
2021-11-19 15:01 ` Ludovic Courtès
2021-11-19 23:43 ` Ricardo Wurmus
2021-11-22 13:19 ` Ludovic Courtès [this message]
2021-11-22 13:36 ` zimoun
2021-11-22 20:13 ` Maxim Cournoyer
2021-11-24 11:07 ` zimoun
2021-11-25 2:13 ` ‘core-updates-frozen’: julia status zimoun
2021-11-25 23:49 ` ‘core-updates-frozen’: julia status update zimoun
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=87v90knx8k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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.