pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/53560: devel/py-pluggy does not build for PYTHON_VERSION>27

On Tue, Aug 28, 2018 at 03:23:50PM +0200, Frédéric Fauberteau wrote:
Le 2018-08-28 14:50, Benny Siegert a écrit :
> The following reply was made to PR pkg/53560; it has been noted by
> From: Benny Siegert <>
> To:
> Cc:,,
> Subject: Re: pkg/53560: devel/py-pluggy does not build for
> Date: Tue, 28 Aug 2018 14:46:45 +0200
>  It looks like the build is fetching some packages that are considered
>  missing. This is a sign that there is one or more dependencies that
>  are missing from the package Makefile, or perhaps they are at the
>  wrong version.

'python2.7 build' works fine while 'python3.6 build'
throws an error about failure of certificate verification. I don't think it is a problem of missing dependency in Makefile since the egg framework seems to fetch these setup requirements in a .egg/ directory. It sounds to me like
a problem of ssl fetching with python3.X.

The core of the problem is the missing setuptools_scm functionality.


I totally agree with that. Actually, py-setuptools_scm should be fetched by the script from the framework and should not be added as a dependency (even a build dependency) of py-pluggy.

After some tests, I can produce the same error with 'python3.6 -c "import urllib.request;urllib.request.urlopen('')"':
Traceback (most recent call last):
File "/home/triaxx/pkg/lib/python3.6/urllib/", line 1318, in do_open
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)

I fix this error by installing mozilla-rootcerts

FMHO, the framework should manage the installation of root certificates to avoid errors when dependencies are fetched from ssl website: But I am not really sure how to do that.


Home | Main Index | Thread Index | Old Index