GNU bug report logs - #46132
[bug] build of /gnu/store/~-python2-setuptools-52.0.0.drv failed

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 46132 in the body.
You can then email your comments to 46132 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: "K I" <gitlabcanada <at> runbox.com>
To: "bug-guix" <bug-guix <at> gnu.org>
Subject: [bug] build of /gnu/store/~-python2-setuptools-52.0.0.drv failed
Date: Wed, 27 Jan 2021 08:47:31 -0700 (MST)

starting phase `patch-source-shebangs'
patch-shebang: ./docs/conf.py: warning: no binary for interpreter `python3' found in $PATH
patch-shebang: ./pkg_resources/_vendor/appdirs.py: changing `/usr/bin/env python' to `/gnu/store/ln0jd0k32xbr2jyha1sdaynllkazgmsi-python2-2.7.17/bin/python'
patch-shebang: ./setup.py: changing `/usr/bin/env python' to `/gnu/store/ln0jd0k32xbr2jyha1sdaynllkazgmsi-python2-2.7.17/bin/python'
phase `patch-source-shebangs' succeeded after 0.0 seconds
starting phase `patch-generated-file-shebangs'
phase `patch-generated-file-shebangs' succeeded after 0.0 seconds
starting phase `build'
running "python setup.py" with command "build" and parameters ()
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "setuptools/__init__.py", line 16, in <module>
    import setuptools.version
  File "setuptools/version.py", line 1, in <module>
    import pkg_resources
  File "pkg_resources/__init__.py", line 1367
    raise SyntaxError(e) from e
                            ^
SyntaxError: invalid syntax
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

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: K I <gitlabcanada <at> runbox.com>, 46132 <at> debbugs.gnu.org
Subject: Re: bug#46132: [bug] build of
 /gnu/store/~-python2-setuptools-52.0.0.drv failed
Date: Thu, 28 Jan 2021 02:09:22 +0100

Hi,

On Wed, 27 Jan 2021 at 08:47, "K I" <gitlabcanada <at> runbox.com> wrote:

>   File "pkg_resources/__init__.py", line 1367
>     raise SyntaxError(e) from e
>                             ^
> SyntaxError: invalid syntax
> 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

It is expected because Setuptools removed the compatibility with Python 2,
see the ChangeLog:

--8<---------------cut here---------------start------------->8---
v47.0.0

28 May 2020
Breaking Changes

    #2094: Setuptools now actively crashes under Python 2. Python 3.5 or later is required. Users of Python 2 should use setuptools<45.
--8<---------------cut here---------------end--------------->8---

<https://setuptools.readthedocs.io/en/latest/history.html>
<https://github.com/pypa/setuptools/issues/2094>


The question is: do we remove ’python2-setuptools’ since it is defined
by the usual ’package-with-python2’?

--8<---------------cut here---------------start------------->8---
(define-public python2-setuptools
  (package-with-python2 python-setuptools))
--8<---------------cut here---------------end--------------->8---

Or do we define python2-setuptools with the version v46.4.0?  Which,
IMHO does not make sense since Python 2 is end of life since one year.


All the best,
simon

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: K I <gitlabcanada <at> runbox.com>
Cc: 46132 <at> debbugs.gnu.org
Subject: Re: bug#46132: [bug] build of
 /gnu/store/~-python2-setuptools-52.0.0.drv failed
Date: Thu, 11 Mar 2021 01:22:22 +0100

Hi,

On Thu, 28 Jan 2021 at 02:09, zimoun <zimon.toutoune <at> gmail.com> wrote:
> On Wed, 27 Jan 2021 at 08:47, "K I" <gitlabcanada <at> runbox.com> wrote:
>
>>   File "pkg_resources/__init__.py", line 1367
>>     raise SyntaxError(e) from e
>>                             ^
>> SyntaxError: invalid syntax
>> 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
>
> It is expected because Setuptools removed the compatibility with Python 2,
> see the ChangeLog:
>
> v47.0.0
>
> 28 May 2020
> Breaking Changes
>
>     #2094: Setuptools now actively crashes under Python 2. Python 3.5 or later is required. Users of Python 2 should use setuptools<45.
>
>
> <https://setuptools.readthedocs.io/en/latest/history.html>
> <https://github.com/pypa/setuptools/issues/2094>
>
>
> The question is: do we remove ’python2-setuptools’ since it is defined
> by the usual ’package-with-python2’?
>
> (define-public python2-setuptools
>   (package-with-python2 python-setuptools))
>
> Or do we define python2-setuptools with the version v46.4.0?  Which,
> IMHO does not make sense since Python 2 is end of life since one year.

Currently, python-setuptools is at version 52.0 and python2-setuptools
at version 41.0.1.  Both build fine.  The comment says:

--8<---------------cut here---------------start------------->8---
;; Newer versions of setuptools no longer support Python 2.
(define-public python2-setuptools
  (package
    (name "python2-setuptools")
    (version "41.0.1")
--8<---------------cut here---------------end--------------->8---

therefore, this part of the bug is done.  Let check the other part.


Cheers,
simon

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Christopher Howard <christopher <at> librehacker.com>
Cc: 46132 <at> debbugs.gnu.org, 46158 <at> debbugs.gnu.org
Subject: Re: bug#46158: qucs-s build failure: cairocffi python2 issue
Date: Thu, 11 Mar 2021 01:27:54 +0100

Hi,

On Thu, 28 Jan 2021 at 09:17, Christopher Howard <christopher <at> librehacker.com> wrote:
> When I try to install qucs-s, installation ultimately fails due to build failure of dependency
> python2-cairocffi-1.2.0. Apparently python2 is no longer allowed by cairocffi:

Indeed, python2-cairocffi is failing.  However qucs-s is available and
build fine with commit 6bed29b.

/gnu/store/2hl8gvma4hzq07m0xdrrncmr46nqwlpy-qucs-s-0.0.21

If it is fine with you, I inclined to close this bug.  WDYT?


All the best,
simon

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

From: Christopher Howard <christopher <at> librehacker.com>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 46132 <at> debbugs.gnu.org, 46158 <at> debbugs.gnu.org
Subject: Re: bug#46158: qucs-s build failure: cairocffi python2 issue
Date: Wed, 10 Mar 2021 15:48:01 -0900

I was able to build qucs a week or two ago, but didn't report it. I
think you can close this bug report. Thank you.

On Thu, 2021-03-11 at 01:27 +0100, zimoun wrote:
> Hi,
> 
> On Thu, 28 Jan 2021 at 09:17, Christopher Howard <
> christopher <at> librehacker.com> wrote:
> > When I try to install qucs-s, installation ultimately fails due to
> > build failure of dependency
> > python2-cairocffi-1.2.0. Apparently python2 is no longer allowed by
> > cairocffi:
> 
> Indeed, python2-cairocffi is failing.  However qucs-s is available
> and
> build fine with commit 6bed29b.
> 
> /gnu/store/2hl8gvma4hzq07m0xdrrncmr46nqwlpy-qucs-s-0.0.21
> 
> If it is fine with you, I inclined to close this bug.  WDYT?
> 
> 
> All the best,
> simon
-- 
Christopher Howard
phone: (907) 374-0257 (landline)
blog: https://librehacker.com
social: https://gnusocial.club/librehacker

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Christopher Howard <christopher <at> librehacker.com>
Cc: 46158-done <at> debbugs.gnu.org, 46132-done <at> debbugs.gnu.org
Subject: Re: bug#46158: qucs-s build failure: cairocffi python2 issue
Date: Thu, 11 Mar 2021 02:03:10 +0100

On Wed, 10 Mar 2021 at 15:48, Christopher Howard <christopher <at> librehacker.com> wrote:
> I was able to build qucs a week or two ago, but didn't report it. I
> think you can close this bug report. Thank you.

Thanks, so closing.

Previous Next

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