From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Danny Milosavljevic <dannym@scratchpost.org>,
Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: New python build system merged
Date: Wed, 30 Nov 2016 16:02:52 +0100 [thread overview]
Message-ID: <4eb0fcd0-3dee-2744-9469-9208d397f3e7@crazy-compilers.com> (raw)
In-Reply-To: <20161130092006.6228a04c@scratchpost.org>
Am 30.11.2016 um 09:20 schrieb Danny Milosavljevic:
> I think it depends on how much work fixing them is. If it were just five minutes then I'd say leave it in master and fix the packages that failed.
>
> Otherwise revert.
I strongly against reverting this! We already have a backlog of several
python packages which are using "setuptools" as input. If reverting the
new python build system, we need to clean them all up later.
We need to go forward instead of reverting. Fixing up the build issues
should be easy since the changes are not fundamental.
> However, Hartmut, I think that Build 1637640 is not even done building all the packages yet (1853
I'm curious (I do not understand hydra yet), but AKAIU a "build" is
about a single package. And https://hydra.gnu.org/build/1637640 builds
calibre. There is no queue not other packages.
I assume you are talking about evaluation 109379
<https://hydra.gnu.org/eval/109379>, which the above build is part of.
This evaluation is outdated. I already fixed some of the errors you
listed, others did not occur on my system when trying to reproduce.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2016-11-30 15:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 12:49 Please set up hdyra-job for python-branch Hartmut Goebel
2016-11-26 4:48 ` Leo Famulari
2016-11-28 9:21 ` Hartmut Goebel
2016-11-28 13:40 ` Ludovic Courtès
2016-11-29 9:54 ` Hartmut Goebel
2016-11-29 14:27 ` Ludovic Courtès
2016-11-29 18:09 ` New python build system merged Hartmut Goebel
2016-11-29 21:12 ` Leo Famulari
2016-11-30 8:20 ` Danny Milosavljevic
2016-11-30 15:02 ` Hartmut Goebel [this message]
2016-11-30 16:59 ` Leo Famulari
2016-11-30 17:26 ` Leo Famulari
2016-11-30 17:30 ` Leo Famulari
2016-12-01 14:10 ` Ludovic Courtès
2016-11-30 17:30 ` Hartmut Goebel
2016-11-30 20:41 ` Leo Famulari
2016-12-01 14:13 ` Hydra replacement and all that Ludovic Courtès
2016-11-30 10:41 ` New python build system merged Leo Famulari
2016-11-29 23:46 ` ng0
2016-11-30 12:47 ` Ludovic Courtès
2016-11-30 13:58 ` ng0
2016-11-30 12:40 ` Ludovic Courtès
2016-12-05 19:30 ` Leo Famulari
2016-12-06 9:22 ` Ludovic Courtès
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=4eb0fcd0-3dee-2744-9469-9208d397f3e7@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).