From: Nicolas Goaziou via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merging r-team branch
Date: Sun, 07 Jul 2024 10:53:58 +0200 [thread overview]
Message-ID: <878qydvazd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87v81hslzs.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 07 Jul 2024 09:24:23 +0200")
Hello,
Ricardo Wurmus <rekado@elephly.net> writes:
> the r-team branch has been built successfully. It contains updates to R
> and both CRAN and Bioconductor packages.
>
> It is the last in the queue of branches to be merged:
>
> core-updates #70456
> tex-team #70915
> python-team #71408
> kde-team #71614
> rust-team #71703
> r-team #71901
>
> It touches very few packages that are not related to R. The exception
> is apache-arrow.
>
> I know that while the python-team branch is farther up the queue it is
> not actually ready to be merged, pushing up kde-team, rust-team, and
> r-team. What is the status of the other branches in the queue?
The tex-team branch is included in core-updates and currently being
built by the bordeaux farm. So it can be ignored.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2024-07-07 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 7:24 merging r-team branch Ricardo Wurmus
2024-07-07 7:49 ` Zheng Junjie
[not found] ` <87ikx6hl52.fsf@qq.com>
2024-07-15 12:53 ` Z572
2024-07-07 8:53 ` Nicolas Goaziou via Development of GNU Guix and the GNU System distribution. [this message]
2024-07-07 9:36 ` Andreas Enge
2024-07-07 17:04 ` Efraim Flashner
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=878qydvazd.fsf@nicolasgoaziou.fr \
--to=guix-devel@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--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 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).