From: Nicolas Goaziou via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
guix-devel@gnu.org, lars@6xq.net, marius@gnu.org,
me@bonfacemunyoki.com, tanguy@bioneland.org, jgart@dismail.de
Subject: Re: Status of python-team 2024-11-21
Date: Fri, 22 Nov 2024 10:39:55 +0100 [thread overview]
Message-ID: <87o727k3o4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <Zz8nmzwy3uR1w5BV@jurong> (Andreas Enge's message of "Thu, 21 Nov 2024 13:29:15 +0100")
Hello,
Andreas Enge <andreas@enge.fr> writes:
> Am Thu, Nov 21, 2024 at 12:03:26PM +0000 schrieb Sharlatan Hellseher:
>> I've rebased and pushed all of my changes updating python-numpy,
>> python-mypy and python-pandas with fixture of some packages linked for
>> python-pandas.
>> I might need some hands of help to check the changes. Particular
>> texlive-hyphen-complete is failing which linked to cmake (not sure how)
>> which affect 13232 dependent packages
>
> CC-ing the modular texlive expert for this, in case he overlooks it on
> guix-devel. Maybe just a transient failure?
I don't know how texlive-hyphen-complete relates to cmake either.
texlive-hyphen-complete depends on Ruby.
Anyway, what is the build error (or where can I find it)?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2024-11-22 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 12:03 Status of python-team 2024-11-21 Sharlatan Hellseher
2024-11-21 12:29 ` Andreas Enge
2024-11-22 9:39 ` Nicolas Goaziou via Development of GNU Guix and the GNU System distribution. [this message]
2024-11-22 9:50 ` Andreas Enge
2024-11-22 12:16 ` Nicolas Graves
2024-11-22 11:03 ` Andreas Enge
2024-11-22 11:10 ` Andreas Enge
2024-11-22 11:48 ` Ricardo Wurmus
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=87o727k3o4.fsf@nicolasgoaziou.fr \
--to=guix-devel@gnu.org \
--cc=andreas@enge.fr \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@nicolasgoaziou.fr \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.