Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Sep 2015 10:33:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 203331] Installation failure of some ports named */py-* if Python's default version is set to 3.4
Message-ID:  <bug-203331-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203331

            Bug ID: 203331
           Summary: Installation failure of some ports named */py-* if
                    Python's default version is set to 3.4
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr@FreeBSD.org
          Reporter: raviqqe@gmail.com
                CC: freebsd-ports-bugs@FreeBSD.org

# Symptom

About devel/py-pytz, devel/py-babel and devel/py-six ports,
if `DEFAULT_VERSIONS= python=3.4` is specified in /etc/make.conf
or on command line, `make` compilation succeeds but `make install` fails
with error messages like the below;

```
===>  Installing for py34-pytz-2015.4,1
===>   py34-pytz-2015.4,1 depends on package: py34-setuptools34>0 - found
===>   py34-pytz-2015.4,1 depends on file: /usr/local/bin/python3.4 - found
===>   Registering installation for py34-pytz-2015.4,1
pkg-static: Plist error, directory listed as a file:
lib/python3.4/site-packages/pytz-2015.4-py3.4.egg-info
*** Error code 74

Stop.
make[1]: stopped in /usr/ports/devel/py-pytz
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/py-pytz
```

# My Makeshift

Remove the entries of `lib/python3.4/site-packages/pytz-2015.4-py3.4.egg-info`
from /usr/ports/devel/py-tz/work/.PLIST.mktmp and .PLIST.pymodtmp.
Then, run `make install`.

But, I don't know whether this is the proper way.

# My Guess

The files seems to be generated by the mk scripts, such as
/usr/ports/Mk/bsd.port.mk and /usr/ports/Mk/Uses/python.mk (these may be all),
so the mk scripts should, I guess, be fixed.

Additionally, I did not test all ports named */py-*
and this problem can appear on some others of them.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203331-13>