FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: lang/python26 description:Interpreted object-oriented programming language maintainer: pyt...@freebsd.org deprecated because: This port will reach it's EoL upstream soon, please migrate to lang/python27 expiration date:2013-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=python26 portname: lang/python31 description:Interpreted object-oriented programming language maintainer: pyt...@freebsd.org deprecated because: This port will reach it's EoL upstream soon, please migrate to lang/python33 expiration date:2014-06-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=python31 If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD. ___ 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: Python and SIGINT, SIGTERM.
On, Mon Aug 26, 2013, Jonathan Chen wrote: > Hi, > > I'm currently trying to use FreeBSD as my main python development O/S, > and I'm noticing some oddness when I'm working with OpenERP. If I > start the server from command line, a ^C to stop the server is rarely > honoured. Similarly, when working with Eclipse + PyDev, a request to > terminate a running instance will leave the process still actively > running. In most cases, only a SIGKILL will work. > > I do not see this sort of behaviour when I'm using Ubuntu. Is this a > problem with OpenERP, or does the problem lie with our python port? Do you use the same version of OpenERP on both systems with the same patches and build flags or a specific (probably prebuilt) build for each of them? If it is the latter case, can you ensure that OpenERP does not catch the signals in order to shut down more gracefully? Cheers Marcus pgpyBLYFYGBvr.pgp Description: PGP signature
Port Request
I have been attempting for a little while now to make a port out of this: http://code.google.com/p/apsw/ Unfortunately, I am ignorant of the python ports in freebsd. I need to get this port built in order to update deskutils/calibre to the latest 1.x branch as that is a new requirement. I'm attaching what I have so far and would appreciate any help on it. (yes, I know I didn't make it far.) The failure actually has nothing to do with the port but is with the basic building of the program. [tethys]:/home/rnejdl/Downloads/apsw/apsw-3.8.0.2-r1> python setup.py build running build running build_ext SQLite: Using system sqlite include/libraries building 'apsw' extension creating build creating build/temp.freebsd-9.2-PRERELEASE-amd64-2.7 creating build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src cc -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -march=nocona -DNDEBUG -O2 -pipe -fno-strict-aliasing -march=nocona -fPIC -DEXPERIMENTAL=1 -DNDEBUG=1 -DAPSW_FORK_CHECKER=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isrc -I/usr/local/include/python2.7 -c src/apsw.c -o build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src/apsw.o src/apsw.c:58:21: error: sqlite3.h: No such file or directory src/apsw.c:62:2: error: #error Your SQLite version is too old. It must be at least 3.8.0 In file included from src/apsw.c:128: src/exceptions.c:24: error: expected declaration specifiers or '...' before 'sqlite3' How do I get setup.py to find sqlite3.h at /usr/local/include/sqlite3.h ? Rusty Nejdl ___ 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: Port Request
On, Sat Sep 07, 2013, Rusty Nejdl wrote:
[...]
> [tethys]:/home/rnejdl/Downloads/apsw/apsw-3.8.0.2-r1> python setup.py
> build
> running build
> running build_ext
> SQLite: Using system sqlite include/libraries
> building 'apsw' extension
> creating build
> creating build/temp.freebsd-9.2-PRERELEASE-amd64-2.7
> creating build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src
> cc -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -march=nocona
> -DNDEBUG -O2 -pipe -fno-strict-aliasing -march=nocona -fPIC
> -DEXPERIMENTAL=1 -DNDEBUG=1 -DAPSW_FORK_CHECKER=1
> -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isrc -I/usr/local/include/python2.7 -c
> src/apsw.c -o build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src/apsw.o
> src/apsw.c:58:21: error: sqlite3.h: No such file or directory
> src/apsw.c:62:2: error: #error Your SQLite version is too old. It must
> be at least 3.8.0
> In file included from src/apsw.c:128:
> src/exceptions.c:24: error: expected declaration specifiers or '...'
> before 'sqlite3'
>
> How do I get setup.py to find sqlite3.h at /usr/local/include/sqlite3.h
> ?
By passing in the correct CFLAGS. By default C extensions to Python just
include the relevant Python CFLAGS. Since you need the sqlite headers,
which are located in /usr/local/include, execute the following (bourne
shell):
# CFLAGS=-I/usr/local/include python setup.py build
And since I guess that apsw links to libsqlite3, also pass the
LDFLAGS=-L/usr/local/lib:
# CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib python setup.py build
For your port Makefile that'd mean that you should set
CFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
Cheers
Marcus
pgpHGKKLRTEMh.pgp
Description: PGP signature
Re: Port Request
On 2013-09-07 14:39, Marcus von Appen wrote:
> On, Sat Sep 07, 2013, Rusty Nejdl wrote:
>
> [...]
>
>> [tethys]:/home/rnejdl/Downloads/apsw/apsw-3.8.0.2-r1> python setup.py build
>> running build running build_ext SQLite: Using system sqlite
>> include/libraries building 'apsw' extension creating build creating
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7 creating
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src cc -fno-strict-aliasing -O2
>> -pipe -fno-strict-aliasing -march=nocona -DNDEBUG -O2 -pipe
>> -fno-strict-aliasing -march=nocona -fPIC -DEXPERIMENTAL=1 -DNDEBUG=1
>> -DAPSW_FORK_CHECKER=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isrc
>> -I/usr/local/include/python2.7 -c src/apsw.c -o
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src/apsw.o src/apsw.c:58:21:
>> error: sqlite3.h: No such file or directory src/apsw.c:62:2: error: #error
>> Your SQLite version is too old. It must be at least 3.8.0 In file included
>> from src/apsw.c:128: src/exceptions.c:24: error: expected declaration
>> specifiers or '...' before 'sqlite3' How do I get setup.py to find sqlite3.h
>> at /usr/local/include/sqlite3.h ?
>
> By passing in the correct CFLAGS. By default C extensions to Python just
> include the relevant Python CFLAGS. Since you need the sqlite headers,
> which are located in /usr/local/include, execute the following (bourne
> shell):
>
> # CFLAGS=-I/usr/local/include python setup.py build
>
> And since I guess that apsw links to libsqlite3, also pass the
> LDFLAGS=-L/usr/local/lib:
>
> # CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib python setup.py build
>
> For your port Makefile that'd mean that you should set
>
> CFLAGS+= -I${LOCALBASE}/include
> LDFLAGS+= -L${LOCALBASE}/lib
>
> Cheers
> Marcus
Marcus,
Nicely done and that fixed it so it compiles now. Now, the last part I
am stuck on is that the package has an underscore in it:
Writing
/usr/local/lib/python2.7/site-packages/apsw-3.8.0.2_r1-py2.7.egg-info
which kills me on deinstall:
On 2013-09-07 14:39, Marcus von Appen wrote:
> On, Sat Sep 07, 2013, Rusty Nejdl wrote:
>
> [...]
>
>> [tethys]:/home/rnejdl/Downloads/apsw/apsw-3.8.0.2-r1> python setup.py build
>> running build running build_ext SQLite: Using system sqlite
>> include/libraries building 'apsw' extension creating build creating
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7 creating
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src cc -fno-strict-aliasing -O2
>> -pipe -fno-strict-aliasing -march=nocona -DNDEBUG -O2 -pipe
>> -fno-strict-aliasing -march=nocona -fPIC -DEXPERIMENTAL=1 -DNDEBUG=1
>> -DAPSW_FORK_CHECKER=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isrc
>> -I/usr/local/include/python2.7 -c src/apsw.c -o
>> build/temp.freebsd-9.2-PRERELEASE-amd64-2.7/src/apsw.o src/apsw.c:58:21:
>> error: sqlite3.h: No such file or directory src/apsw.c:62:2: error: #error
>> Your SQLite version is too old. It must be at least 3.8.0 In file included
>> from src/apsw.c:128: src/exceptions.c:24: error: expected declaration
>> specifiers or '...' before 'sqlite3' How do I get setup.py to find sqlite3.h
>> at /usr/local/include/sqlite3.h ?
>
> By passing in the correct CFLAGS. By default C extensions to Python just
> include the relevant Python CFLAGS. Since you need the sqlite headers,
> which are located in /usr/local/include, execute the following (bourne
> shell):
>
> # CFLAGS=-I/usr/local/include python setup.py build
>
> And since I guess that apsw links to libsqlite3, also pass the
> LDFLAGS=-L/usr/local/lib:
>
> # CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib python setup.py build
>
> For your port Makefile that'd mean that you should set
>
> CFLAGS+= -I${LOCALBASE}/include
> LDFLAGS+= -L${LOCALBASE}/lib
>
> Cheers
> Marcus
Marcus,
Nicely done and that fixed it so it compiles now. Now, the last part I
am stuck on is that the package has an underscore in it:
Writing
/usr/local/lib/python2.7/site-packages/apsw-3.8.0.2_r1-py2.7.egg-info
which kills me on deinstall:
pkg_delete: file
'/usr/local/lib/python2.7/site-packages/apsw-3.8.0.2-py2.7.egg-info'
doesn't exist
On other ports I've always had to create a pkg-plist but the python
infrastructure seems to handle all of that automatically. I've looked
around and can't find how to work around this.
Thanks in advance yet again!
Rusty Nejdl
___
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: Port Request
[...]
> Nicely done and that fixed it so it compiles now. Now, the last part I
> am stuck on is that the package has an underscore in it:
>
> Writing
> /usr/local/lib/python2.7/site-packages/apsw-3.8.0.2_r1-py2.7.egg-info
>
> which kills me on deinstall:
>
> pkg_delete: file
> '/usr/local/lib/python2.7/site-packages/apsw-3.8.0.2-py2.7.egg-info'
> doesn't exist
You can change the name of the egg-info file via the PYDISTUTILS_EGGINFO
variable. Something like the following might do the trick for you:
PYDISTUTILS_EGGINFO=${PORTNAME}-${PORTVERSION}_r1-py${PYTHON_VER}...
However, the egg-info consists of multiple parts, so you might go an
easier route by setting PYDISTUTILS_PKGVERSION to something like:
PYDISTUTILS_PKGVERSION= ${PORTVERSION}_r1
and leave the _EGGINFO variable alone. Check /usr/ports/Mk/bsd.python.mk
for further details about how the egg info file name is built, The
documentation on the knobs is fairly good.
Cheers
Marcus
pgpHUuQH_SDbk.pgp
Description: PGP signature
Re: ports/181925: Update port: www/py-selenium Upgrade to 2.35.0
Synopsis: Update port: www/py-selenium Upgrade to 2.35.0 Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python Responsible-Changed-By: edwin Responsible-Changed-When: Sun Sep 8 02:00:15 UTC 2013 Responsible-Changed-Why: freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=181925 ___ 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/181926: maintainer update: sysutils/py-salt
Synopsis: maintainer update: sysutils/py-salt Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python Responsible-Changed-By: edwin Responsible-Changed-When: Sun Sep 8 02:20:13 UTC 2013 Responsible-Changed-Why: freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=181926 ___ 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/181926: maintainer update: sysutils/py-salt
Synopsis: maintainer update: sysutils/py-salt Responsible-Changed-From-To: freebsd-python->culot Responsible-Changed-By: culot Responsible-Changed-When: Sun Sep 8 06:46:11 UTC 2013 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=181926 ___ 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/181925: Update port: www/py-selenium Upgrade to 2.35.0
Synopsis: Update port: www/py-selenium Upgrade to 2.35.0 Responsible-Changed-From-To: freebsd-python->culot Responsible-Changed-By: culot Responsible-Changed-When: Sun Sep 8 06:46:36 UTC 2013 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=181925 ___ 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"
