[Bug 233718] math/py-matplotlib: Flavor @py36 does not install because of wrong PYTHON*_SITELIBDIR

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Dec 3 14:33:35 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233718

--- Comment #7 from Rainer Hurling <rhurlin at gwdg.de> ---
(In reply to Kubilay Kocak from comment #6)

>If there's a bug somewhere, whether in py-matplotlib or elsewhere (portmaster), 
>we want to isolate and identify the root cause(s).
I agree.

>The only odd thing I can observe in the attached logs is the last line of the last block:
>===>>> The following actions were performed:
>	Installation of lang/cython at py36 (py36-cython-0.29)
>	Installation of math/py-numpy at py36 (py36-numpy-1.15.1,1)
>	Installation of devel/py-cycler at py36 (py36-cycler-0.10.0)
>	Installation of devel/py-dateutil at py36 (py36-dateutil-2.7.3)
>	Installation of devel/py-pyparsing at py36 (py36-pyparsing-2.3.0)
>	Installation of www/py-tornado at py36 (py36-tornado-5.1.1)
>	Installation of math/py-matplotlib at py36 (py27-matplotlib-2.1.2_4) <---

>Every other reference to port origins and package names is foo at py36 and py36-foo
>respectively, with the only reference to py27 being the (resolved) package name 
>in the above line, which definitely appears incorrect.
Yup, as I tried to describe in comment #5, the math/py-matplotlib with flavor
@py36, in contrary to my initial report, builds and installs fine in both
cases.

'pkg info -o math/py-matplotlib' proofs this:
py27-matplotlib-2.1.2_4        math/py-matplotlib
py36-matplotlib-2.1.2_4        math/py-matplotlib

The only thing is, that there is no entry under /var/db/pkg in the first case
(py-matplotlib at py36 needs to install some deps first). That's why I think, that
portmaster could be the culprit.

>However, the logs don't seem to include the actual full logs of the 
>py-matplotlib(@py36) process so its difficult to say at what point that 
>issue first presents itself.
Hmm, I thought I already attached full logs and described, how they were
created. If these are not full logs, which way do you create them?

>On the PYTHONPREFIX_SITELIBDIR change proposal, both the PREFIX and non-PREFIX 
>versions of that variable include the correct Python version specific path, 
>use of PREFIX only makes the port PREFIX-overriden safe. I think this means 
>that its unlikely to be the cause, nor the solution.
If I am right with the above, there is no need to change from PYTHON_SITELIBDIR
to PYTHONPREFIX_SITELIBDIR. Even with PYTHONPREFIX_SITELIBDIR, the behaviour is
the same.

>What we need from here is:
>- Full log of py-matplotlib failing. Please un-quieten the @FIND command 
>  in the port before doing this, so we can confirm the full path/filenames 
>  that get operated on.
>- Test: Does the current port (without patch) fail under poudriere?
In the logs, I used FIND instead of @FIND already. The relevant line should be:
/usr/bin/find
/usr/ports/math/py-matplotlib/work-py36/stage/usr/local/lib/python3.6/site-packages/matplotlib
-name '*.so'  | /usr/bin/xargs /usr/bin/strip

On Poudriere, math/py-matplotlib at py36 builds fine (without patch).

Do you think, the missing entry for "py36-matplotlib-2.1.2_4" under /var/db/pkg
is something, the port itself (and not portmaster) is responsible for?

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list