GNU bug report logs - #37989
python2-numpy v1.17.3 fails to build

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37989 in the body.
You can then email your comments to 37989 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Josh Holland <josh <at> inv.alid.pw>
To: "bug-guix\@gnu.org" <bug-guix <at> gnu.org>
Subject: python2-numpy v0.17.3 fails to build
Date: Wed, 30 Oct 2019 11:45:50 +0000

Hi,

It seems that the update of python-numpy to 1.17.3 in
8e5fbd5dda93e137ff527cabe25989b28ab9e1c0 has broken the build of the
corresponding Python 2 package, both on my local machine and on the CI
server: http://ci.guix.gnu.org/build/1893145/details.

The log in Cuirass is incomplete, but the error in my build is the
following:

starting phase `build'
running "python setup.py" with command "build" and parameters ()
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "setup.py", line 31, in <module>
    raise RuntimeError("Python version >= 3.5 required.")
RuntimeError: Python version >= 3.5 required.
command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1

Indeed, despite the assertion on
https://numpy.org/doc/1.17/user/building.html that Python 2.7 or 3.4 are
sufficient, the setup.py script explicitly checks that Python is at
least 3.5; see the upstream commit badf2901:

https://github.com/numpy/numpy/commit/badf2901ea040aa89dbb3c19e53c6b1b692cb489

Lots of packages including libreoffice transitively depend on
python2-numpy, so this needs some sort of resolution — perhaps simply
pinning python2-numpy to a previous version?  However, Python 2 will not
be maintained after the end of 2019, and I'm not sure if there is an
overall Guix-wide migration plan for python2-* packages.

--
Josh Holland

Message #10 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: bug-guix <at> gnu.org
Subject: Re: bug#37989: python2-numpy v0.17.3 fails to build
Date: Wed, 30 Oct 2019 14:23:41 +0100

Hi Josh,
> Lots of packages including libreoffice transitively depend on
> python2-numpy, so this needs some sort of resolution — perhaps simply
> pinning python2-numpy to a previous version?

That would be my preferred solution - pin python2-numpy to the last 
NumPy version that supports Python 2, which is most likely 1.16.

> However, Python 2 will not
> be maintained after the end of 2019, and I'm not sure if there is an
> overall Guix-wide migration plan for python2-* packages.

Not that I know, but no matter how this will be handled, Guix is the 
perfect platform for people still depending on Python 2 because they can 
always install packages from an earlier release. Which is a good reason 
to end Python 2 support in Guix by an as up to date package set as possible.


Cheers.

  Konrad.

Message #15 received at 37989-done <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Josh Holland <josh <at> inv.alid.pw>, 37989-done <at> debbugs.gnu.org
Subject: Re: bug#37989: python2-numpy v0.17.3 fails to build
Date: Wed, 30 Oct 2019 14:33:43 +0100

[Message part 1 (text/plain, inline)]

Josh Holland <josh <at> inv.alid.pw> writes:

> Hi,
>
> It seems that the update of python-numpy to 1.17.3 in
> 8e5fbd5dda93e137ff527cabe25989b28ab9e1c0 has broken the build of the
> corresponding Python 2 package, both on my local machine and on the CI
> server: http://ci.guix.gnu.org/build/1893145/details.

Fixed in adb396eae3524d9b82294aaf5cc87a615515b04d, thanks!

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.