unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Leo Famulari <leo@famulari.name>,
	Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: New python build system merged
Date: Wed, 30 Nov 2016 09:20:06 +0100	[thread overview]
Message-ID: <20161130092006.6228a04c@scratchpost.org> (raw)
In-Reply-To: <20161129211200.GA17078@jasmine>

Hi,

> There is still at least one new failure, borg. Are there more? If so, we
> should revert the changes until they are ready.

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.

However, Hartmut, I think that Build 1637640 is not even done building all the packages yet (1853 packages are pending; and some "python-" packages are in the queue), so it's anyone's guess which packages are affected.

As for the Python-requiring packages (which do or don't have "python" in the name), the failing ones I can spot are:
- borg (can't import borg) 
- calibre ("list index out of range" in setup.py)
- kicad (because of python2-wxpython failure "option --single-version-externally-managed not recognized")
- python2-wxpython ("option --single-version-externally-managed not recognized")
- python-sympy (testing fails because some tests that were supposed to fail passed instead)
- python-ipython (Can't find "docs/build/texinfo/ipython.info")
- python2-beautifulsoup4 (Tries to use "python3" in convert-py3k - why? After all it's supposed to use Python 2)

There are others.

On the other hand, many Python packages that failed building before now are working.
 
In any case I think the new Python build-system is an improvement and I can help fix some of those packages. Just don't merge when it's not even done building them yet :P

  reply	other threads:[~2016-11-30  8:20 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 [this message]
2016-11-30 15:02                 ` Hartmut Goebel
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=20161130092006.6228a04c@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --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).