From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: python3-daemon fails to build
Date: Sat, 15 May 2021 14:13:33 +0200 [thread overview]
Message-ID: <e7510dba-4b2f-42f8-0a1b-0f5a39e82fa1@ipfire.org> (raw)
In-Reply-To: <e5ea07cb-797b-6dea-4df4-20c3d987699e@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3497 bytes --]
Hi All,
On 15/05/2021 13:03, Adolf Belka wrote:
> Hi All,
>
> On 14/05/2021 20:42, Peter Müller wrote:
>> Hello development folks,
>>
>> just thought you might want to know:
>>
>>> python-docutils (0.12) [ DONE ]
>>> python3-daemon (2.1.1) [ 8 ][ FAIL ]
>>>
>>> Traceback (most recent call last):
>>> File "/usr/lib/python3.8/site-packages/setuptools/installer.py", line 128, in fetch_build_egg
>>> subprocess.check_call(cmd)
>>> File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
>>> raise CalledProcessError(retcode, cmd)
>>> subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpldy8j00v', '--quiet', 'docutils']' returned non-zero exit status 1.
>>> The above exception was the direct cause of the following exception:
>>> Traceback (most recent call last):
>>> File "setup.py", line 51, in <module>
>>> setup(
>>> File "/usr/lib/python3.8/site-packages/setuptools/__init__.py", line 164, in setup
>>> _install_setup_requires(attrs)
>>> File "/usr/lib/python3.8/site-packages/setuptools/__init__.py", line 159, in _install_setup_requires
>>> dist.fetch_build_eggs(dist.setup_requires)
>>> File "/usr/lib/python3.8/site-packages/setuptools/dist.py", line 699, in fetch_build_eggs
>>> resolved_dists = pkg_resources.working_set.resolve(
>>> File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 779, in resolve
>>> dist = best[req.key] = env.best_match(
>>> File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1064, in best_match
>>> return self.obtain(req, installer)
>>> File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1076, in obtain
>>> return installer(requirement)
>>> File "/usr/lib/python3.8/site-packages/setuptools/dist.py", line 758, in fetch_build_egg
>>> return fetch_build_egg(self, req)
>>> File "/usr/lib/python3.8/site-packages/setuptools/installer.py", line 130, in fetch_build_egg
>>> raise DistutilsError(str(e)) from e
>>> distutils.errors.DistutilsError: Command '['/usr/bin/python3', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpldy8j00v', '--quiet', 'docutils']' returned non-zero exit status 1.
>>> make: *** [python3-daemon:73: /usr/src/log/python-daemon-2.1.1] Error 1
>>>
>>> ERROR: Building python3-daemon [ FAIL ]
>>> Check /home/pmu/ipfire-2.x/log/_build.ipfire.log for errors if applicable [ FAIL ]
>> Looks like python3-daemon depends on python3-docutils, but I am not quite sure...
>
> Yes it looks so. python-daemon had python-docutils just before it in make.sh
>
> python-daemon was changed to python3-daemon using python3 build and it now looks for a python3 version of docutils but that is not built till later in make.sh.
>
> I am running a build now where I have put a python3 version of docutils just before python3-daemon and will see how that builds and let you know.
>
The python3-daemon build has run successfully with python3-docutils just before it. When the build finishes I will submit a patch.
Regards,
Adolf.
> Regards,
>
> Adolf.
>
>
>> Thanks, and best regards,
>> Peter Müller
prev parent reply other threads:[~2021-05-15 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 18:42 Peter Müller
2021-05-15 11:03 ` Adolf Belka
2021-05-15 12:13 ` Adolf Belka [this message]
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=e7510dba-4b2f-42f8-0a1b-0f5a39e82fa1@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox