Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
The following reply was made to PR ports/188431; it has been noted by GNATS. From: Johannes Meixner To: bug-follo...@freebsd.org Cc: Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files Date: Sat, 12 Apr 2014 13:27:10 +0300 --9zSXsLTf0vkW971A Content-Type: multipart/mixed; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've been able to reproduce it using the following steps: 1. poudriere testport -I -n -j -p -o devel/py-pip once that's done, enter the jail and execute 2. pip install --upgrade setuptools 3. cd /usr/ports/devel/py-pytz && make install clean=20 I've attached the logs to this step as proof. Could you please provide the output of=20 `ls -la /usr/local/lib/python2.7/site-packages`=20 as well as `pkg version -v` and `pip list` ? Thanks, -J --=20 Johannes Meixner Ports Committer --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=pytzlog ===> Installing for py27-pytz-2014.1.1,1 ===> py27-pytz-2014.1.1,1 depends on package: py27-setuptools27>0 - found ===> py27-pytz-2014.1.1,1 depends on file: /usr/local/bin/python2.7 - found ===> Checking if devel/py-pytz already installed ===> Registering installation for py27-pytz-2014.1.1,1 pkg-static: Plist error, directory listed as a file: lib/python2.7/site-packages/pytz-2014.1.1-py2.7.egg-info *** Error code 74 Stop. make: stopped in /usr/ports/devel/py-pytz --oyUTqETQ0mS9luUI-- --9zSXsLTf0vkW971A Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJTSRT+AAoJEPyeKTcbGw0LHPMH/inheg0P7PFnmfY29iIkXYtC 0ZG5ugIIfL8Skt+xzkDDXtLJaV7vu7SjTsTmoCx/ZiXXJVaM6GmZHQXmN99HbiDi dvOorFAS0DO+OLI059SLxBYVDVLu35dVyushn5/UuyfihaeTPTarSDusQNuBeH6+ Nqe2bltrFsdtWovtIRFCuTuVtuU1RlRwKp/MOP4fuCCNOMhW2qhBJTxrQamiWGze v3EpjzV+2KZaZYwlBXpAwrIZhj+nZ1WaN9P+qtCrTRrH5upXH7l8CGVJJDgLSoK2 O/ar78UrMYi8lJP6FMWFs3v4xcg4RkWKxyW0sarF6OxU6IsiDa+N7veHs10T7hc= =JwKA -END PGP SIGNATURE- --9zSXsLTf0vkW971A-- ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
The following reply was made to PR ports/188431; it has been noted by GNATS. From: William Grzybowski To: bug-follo...@freebsd.org, anti...@csh.rit.edu Cc: Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files Date: Sat, 12 Apr 2014 09:07:06 -0300 Hi, Well, of course it will break if you upgrade setuptools, our setuptools has a patch to handle a .PLIST issue with directories. -- William Grzybowski -- Curitiba/PR - Brasil ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
The following reply was made to PR ports/188431; it has been noted by GNATS. From: Kubilay Kocak To: bug-follo...@freebsd.org, anti...@csh.rit.edu Cc: William Grzybowski Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files Date: Sat, 12 Apr 2014 22:24:17 +1000 Kevin, Please note that you do *not* need to run the reproduction steps listed above, and only need to provide the output of the ls -la command above. We are interested in the contents of your Python 2.7 site-packages because we have a theory as to what the cause is based on isolation tests we have run on another users installation that is exhibiting similar symptoms ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
The following reply was made to PR ports/188431; it has been noted by GNATS.
From: "Kevin Thompson"
To: bug-follo...@freebsd.org, willia...@gmail.com, x...@freebsd.org,
koobs.free...@gmail.com
Cc:
Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST
files
Date: Sat, 12 Apr 2014 09:24:59 -0400
> Well, of course it will break if you upgrade setuptools, our
> setuptools has a patch to handle a .PLIST issue with directories.
Could you elaborate? I was trying to follow instructions from
/usr/ports/UPDATING:
> 20140307:
> AFFECTS: users of devel/py-setuptools dependent ports
> AUTHOR: sunp...@freebsd.org
> devel/py-setuptools is being used for every python ports (if
> USE_PYDISTUTILS
> defined) since r336553. Due to PKGORIGIN limitation, we cannot build
> one
> python port with python27 and the other with python33 since they
> require
> different setuptools versions which have same PKGORIGIN. With the
> addition
> of py-setuptools{27,32,33}, we could now have py27-foo and py33-bar
> coexist
> in one system.
> Note that this is only a short-term solution. It does not help if you
> need
> coexistence of one port with different python versions, e.g. py27-foo
> and
> py33-foo.
> Please rebuild all ports that depend on devel/py-setuptools and use
> devel/py-setuptools{27,32,33} instead.
> XX represents python version (27, 32 or 33) in the following steps.
> pkgng users:
> # pkg set -o devel/py-setuptools:devel/py-setuptoolsXX
> portmaster users:
> # portmaster -o devel/py-setuptoolsXX devel/py-setuptools
> # portmaster -r py\*setuptools
> portupgrade users:
> # portupgrade -o devel/py-setuptoolsXX -f devel/py-setuptools
> # portupgrade -fr devel/py-setuptools
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
The following reply was made to PR ports/188431; it has been noted by GNATS. From: "Kevin Thompson" To: bug-follo...@freebsd.org, willia...@gmail.com, x...@freebsd.org, koobs.free...@gmail.com Cc: Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files Date: Sat, 12 Apr 2014 09:37:02 -0400 > Please note that you do *not* need to run the reproduction steps listed > above, and only need to provide the output of the ls -la command above. > We are interested in the contents of your Python 2.7 site-packages > because we have a theory as to what the cause is based on isolation > tests we have run on another users installation that is exhibiting > similar symptoms Here you go: angst(/usr/local/lib/python2.7/site-packages) > ls -ltra total 3838 -rw-r--r-- 1 root wheel 1.7K Jun 11 2013 site.pyo -rw-r--r-- 1 root wheel 1.7K Jun 11 2013 site.pyc -r--r--r-- 1 root wheel 2.4K Jun 11 2013 site.py -rw-r--r-- 1 root wheel34B Jun 11 2013 setuptools.pth -rw-r--r-- 1 root wheel 144B Jun 11 2013 setuptools-0.6c11-py2.7.egg-info -rw-r--r-- 1 root wheel 215B Jun 11 2013 distribute.pth -rw-r--r-- 1 root wheel 849K Jun 11 2013 distribute-0.6.35-py2.7.egg drwxr-xr-x 4 root wheel 512B Jun 11 2013 Babel-0.9.6-py2.7.egg/ -rw-r--r-- 1 root wheel 6.4K Jun 13 2013 startfile.pyo -rw-r--r-- 1 root wheel 6.4K Jun 13 2013 startfile.pyc -rw-r--r-- 1 root wheel23K Jun 13 2013 ScanView.pyo -rw-r--r-- 1 root wheel23K Jun 13 2013 ScanView.pyc -rw-r--r-- 1 root wheel11K Jun 13 2013 Reporter.pyo -rw-r--r-- 1 root wheel11K Jun 13 2013 Reporter.pyc drwxr-xr-x 4 root wheel 512B Jul 1 2013 MarkupSafe-0.15-py2.7-freebsd-9.1-STABLE-amd64.egg/ drwxr-xr-x 2 root wheel 2.0K Aug 18 2013 BitQueue/ drwxr-xr-x 2 root wheel 1.0K Aug 18 2013 BitCrawler/ drwxr-xr-x 2 root wheel 1.5K Aug 18 2013 khashmir/ drwxr-xr-x 2 root wheel 4.0K Aug 18 2013 BitTorrent/ drwxr-xr-x 3 root wheel 2.0K Aug 18 2013 BitTornado/ -rw-r--r-- 1 root wheel 228B Aug 18 2013 BTQueue-0.1.3-py2.7.egg-info -rw-r--r-- 1 root wheel 580B Aug 18 2013 pyOpenSSL-0.13-py2.7.egg-info -rw-r--r-- 1 root wheel 126B Dec 13 11:31 easy_install.py -rw-r--r-- 1 root wheel22K Jan 6 10:54 six.py -r--r--r-- 1 root wheel 119B Mar 6 02:07 README drwxr-xr-x 2 root wheel 512B Apr 4 09:34 lit34/ -rw-r--r-- 1 root wheel96K Apr 10 08:26 pkg_resources.py -rw-r--r-- 1 root wheel 104K Apr 10 08:26 pkg_resources.pyc -rw-r--r-- 1 root wheel 321B Apr 10 08:26 easy_install.pyc -rw-r--r-- 1 root wheel 104K Apr 10 08:26 pkg_resources.pyo -rw-r--r-- 1 root wheel 321B Apr 10 08:26 easy_install.pyo drwxr-xr-x 2 root wheel 512B Apr 10 08:26 _markerlib/ drwxr-xr-x 2 root wheel 512B Apr 10 08:26 setuptools-2.0.1-py2.7.egg-info/ -r--r--r-- 1 root wheel 185B Apr 10 08:26 easy-install.pth.dist drwxr-xr-x 4 root wheel 1.5K Apr 10 08:39 setuptools/ drwxr-xr-x 2 root wheel 512B Apr 10 08:45 pytz-2014.1.1-py2.7.egg-info/ drwxr-xr-x 3 root wheel 512B Apr 10 08:50 pytz/ -rw-r--r-- 1 root wheel 239B Apr 10 09:00 easy-install.pth -rwxr-xr-x 1 root wheel92K Apr 10 12:01 _cffi_backend.so* drwxr-xr-x 2 root wheel 512B Apr 10 12:01 pycparser-2.10-py2.7.egg-info/ drwxr-xr-x 3 root wheel 1.0K Apr 10 12:02 pycparser/ drwxr-xr-x 2 root wheel 512B Apr 10 12:02 cffi-0.8.1-py2.7.egg-info/ drwxr-xr-x 2 root wheel 1.0K Apr 10 12:02 cffi/ -rw-r--r-- 1 root wheel22K Apr 10 12:02 six.pyo -rw-r--r-- 1 root wheel22K Apr 10 12:02 six.pyc drwxr-xr-x 2 root wheel 512B Apr 10 12:02 six-1.5.2-py2.7.egg-info/ drwxr-xr-x 2 root wheel 512B Apr 10 12:04 cryptography-0.2.2-py2.7.egg-info/ drwxr-xr-x 3 root wheel 512B Apr 10 12:11 cryptography/ drwxr-xr-x 2 root wheel 512B Apr 10 12:11 pyOpenSSL-0.14-py2.7.egg-info/ drwxr-xr-x 3 root wheel 512B Apr 10 12:11 OpenSSL/ drwxr-xr-x 32 root wheel14K Apr 10 12:12 ../ drwxr-xr-x 2 root wheel 512B Apr 10 13:22 docutils-0.11-py2.7.egg-info/ drwxr-xr-x 8 root wheel 1.0K Apr 10 13:22 docutils/ -rwxr-xr-x 1 root wheel 1.1K Apr 10 13:43 libxml2mod.la* -rw-r--r-- 1 root wheel 553K Apr 10 13:43 libxml2mod.a -r--r--r-- 1 root wheel 335K Apr 10 13:43 libxml2.py -r--r--r-- 1 root wheel15K Apr 10 13:43 drv_libxml2.py -rwxr-xr-x 1 root wheel 376K Apr 10 13:43 libxml2mod.so* -rw-r--r-- 1 root wheel 441K Apr 10 13:43 libxml2.pyo -rw-r--r-- 1 root wheel 441K Apr 10 13:43 libxml2.pyc -rw-r--r-- 1 root wheel11K Apr 10 13:43 drv_libxml2.pyo -rw-r--r-- 1 root wheel11K Apr 10 13:43 drv_libxml2.pyc drwxr-xr-x 26 root wheel 2.0K Apr 11 13:41 ./ angst(/usr/local/lib/python2.7/site-packages) > Here's a dump of pkg version -v for Johannes; I'd figure I'
Re: ports/188431: Every python 2.7 port is generating broken .PLIST files
Synopsis: Every python 2.7 port is generating broken .PLIST files Responsible-Changed-From-To: freebsd-python->xmj Responsible-Changed-By: xmj Responsible-Changed-When: Sat Apr 12 13:41:54 UTC 2014 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=188431 ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
pkg-static: Plist error, directory listed as a file: .egg-info
Over the past week, a number of users have reported the following error
when upgrading Python ports:
"pkg-static: Plist error, directory listed as a file:.egg-info"
This has been isolated as a symptom of:
a) A recent pkg version (1.2.7_1) which now generates an error
instead of silently creating a corrupt package
b) Python installations that contain *multiple* python packages that
provide the setuptools module (such as setuptools and distribute).
This (b) can either be the result of a manual install as root (via
easy_install or pip) outside of the scope of ports/packages, or due to
leftovers from previous upgrades.
The root cause is a version of setuptools is imported during the python
setup.py `install` stage, that does not contain a patch which removes
directory entries from --record output (a feature of setuptools).
Users should inspect their ${LOCALBASE}/lib/pythonX.Y/site-packages
directory, and remove any packages that reference old versions of
setuptools or distribute.
Some examples of entries that may be removed are:
1) distribute-0.6.35-py2.7.egg
2) setuptools-0.6c11-py2.7.egg
3) *Any* version of setuptools directly from PyPi via pip or easy_install
If you have any questions, or are unsure whether you can remove a
particular entry or not, either:
- Delete it, then reinstall devel/py-setuptoolsXY for good measure, OR
- Check with us on the mailing list or at #freebsd-python on freenode IRC
TLDR:
You want to be left with the version of setuptools from ports/packages
(currently 2.0.1) as the *only* installed Python package in site-packages/.
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188491: [patch] devel/py-setuptoolXY: fix PYTHON_VERSION
Synopsis: [patch] devel/py-setuptoolXY: fix PYTHON_VERSION Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 12 17:32:43 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=188491 ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: ports/188491: [patch] devel/py-setuptoolXY: fix PYTHON_VERSION
Synopsis: [patch] devel/py-setuptoolXY: fix PYTHON_VERSION Responsible-Changed-From-To: freebsd-python->sunpoet Responsible-Changed-By: sunpoet Responsible-Changed-When: Sat Apr 12 21:40:00 UTC 2014 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=188491 ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: Make python27 build as an unprivileged user
Antoine Brodin wrote at 11:57 +0200 on Apr 4, 2014: > On Fri, Apr 4, 2014 at 12:51 AM, Julio Merino wrote: > > On Thu, Apr 3, 2014 at 3:30 PM, Antoine Brodin wrote: > >> koobs' new python34 port (not committed yet) packages fine as non > >> root, so it seems doable. > > > > Sorry but I don't see how that's relevant. Python 3.4 is a much more > > modern package than 2.7 and many things may have changed in its build > > infrastructure. > > > > Yes, fixing the root cause is doable for sure, and I agree with you > > that, ideally, this should be properly fixed. But: I don't think it's > > worth our time considering that: 1) this is for the "old" 2.x branch > > and 2) some knowledgeable people have already tried and failed at > > doing so. > > > > As things currently are, the python27 package is broken when building > > from ports as non-root. (Which by the way is annoying for > > architectures without prebuilt packages; I have found this problem > > under powerpc64!) > > > > What I'm proposing is that we trivially workaround the problem by > > *temporarily* defining NEED_ROOT and later investigating the failure. > > Doing the former does not preclude the latter, but at least fixes the > > obvious bug. > > > > I don't want to put words on your mouth, but what I think you are > > proposing is that we leave the package broken for an arbitrary > > (possibly infinite) amount of time until someone decides to track and > > fix the root cause. If you are offering to investigate this relatively > > soon as the maintainer that's perfect though. > > > > So up to you really! If you do not agree with the workaround, I will > > at least file a PR for proper tracking. > > Try attached patch. > > Cheers, > > Antoine > Allow staging python27 as a regular user: > > - when compiling, don't compile the running command otherwise it fails to > compile modules imported by the running command > > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/getopt.pyc' > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/py_compile.pyc' > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/struct.pyc' > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/getopt.pyo' > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/py_compile.pyo' > Sorry [Errno 13] Permission denied: > '/wrkdirs/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/struct.pyo' > > - ranlib before installing read only > > Index: lang/python27/files/patch-Makefile.pre.in > === > --- lang/python27/files/patch-Makefile.pre.in(revision 350060) > +++ lang/python27/files/patch-Makefile.pre.in(working copy) > @@ -1,6 +1,6 @@ > ./Makefile.pre.in.orig 2013-04-06 18:02:34.0 +0400 > -+++ ./Makefile.pre.in 2013-04-07 22:30:19.0 +0400 > -@@ -281,9 +281,9 @@ > +--- ./Makefile.pre.in.orig 2013-11-10 07:36:41.0 + > ./Makefile.pre.in 2014-04-04 09:16:00.0 + > +@@ -285,9 +285,9 @@ > > ## > # AST > @@ -12,3 +12,28 @@ > AST_C= $(AST_C_DIR)/Python-ast.c > AST_ASDL= $(srcdir)/Parser/Python.asdl > > +@@ -1006,12 +1006,12 @@ > +$(DESTDIR)$(LIBDEST)/distutils/tests ; \ > +fi > +PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \ > +- $(PYTHON_FOR_BUILD) -Wi -tt $(DESTDIR)$(LIBDEST)/compileall.py \ > ++ $(PYTHON_FOR_BUILD) -B -Wi -tt > $(DESTDIR)$(LIBDEST)/compileall.py \ > +-d $(LIBDEST) -f \ > +-x 'bad_coding|badsyntax|site-packages|lib2to3/tests/data' \ > +$(DESTDIR)$(LIBDEST) > +PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \ > +- $(PYTHON_FOR_BUILD) -Wi -tt -O > $(DESTDIR)$(LIBDEST)/compileall.py \ > ++ $(PYTHON_FOR_BUILD) -B -Wi -tt -O > $(DESTDIR)$(LIBDEST)/compileall.py \ > +-d $(LIBDEST) -f \ > +-x 'bad_coding|badsyntax|site-packages|lib2to3/tests/data' \ > +$(DESTDIR)$(LIBDEST) > +@@ -1089,8 +1089,8 @@ > +if test "$(SO)" = .dll; then \ > +$(INSTALL_DATA) $(LDLIBRARY) $(DESTDIR)$(LIBPL) > ; \ > +else \ > ++ $(RANLIB) $(LIBRARY) ; \ > +$(INSTALL_DATA) $(LIBRARY) > $(DESTDIR)$(LIBPL)/$(LIBRARY) ; \ > +- $(RANLIB) $(DESTDIR)$(LIBPL)/$(LIBRARY) ; \ > +fi; \ > +else \ > +echo Skip install of $(LIBRARY) - use make > fra
