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

[Frédéric Fauberteau <triaxx%NetBSD.org@localhost>]

> 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
> > > GNATS.
> > >
> > > From: Benny Siegert <bsiegert%gmail.com@localhost>
> > > To: gnats-bugs%netbsd.org@localhost
> > > Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
> > > pkgsrc-bugs%netbsd.org@localhost
> > > Subject: Re: pkg/53560: devel/py-pluggy does not build for
> > > PYTHON_VERSION>27
> > > 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 setup.py build' works fine while 'python3.6 setup.py 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.
>
> Joerg

I totally agree with that. Actually, py-setuptools_scm should be fetched 
by the setup.py script from the egg.mk 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('https://pypi.org/simple/setuptools-scm/')"':
Traceback (most recent call last):
  File "/home/triaxx/pkg/lib/python3.6/urllib/request.py", 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 egg.mk framework should manage the installation of root 
certificates to avoid errors when dependencies are fetched from ssl 
website: https://access.redhat.com/articles/2039753. But I am not really 
sure how to do that.

Fred