FreeBSD ports that you maintain which are currently scheduled for deletion

2013-06-07 Thread linimon
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: ports/179413: databases/py-sqlite3: running config *** Signal 10

2013-06-07 Thread edwin
Synopsis: databases/py-sqlite3: running config *** Signal 10

Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python
Responsible-Changed-By: edwin
Responsible-Changed-When: Fri Jun 7 16:20:09 UTC 2013
Responsible-Changed-Why: 
Over to maintainer (via the GNATS Auto Assign Tool)

http://www.freebsd.org/cgi/query-pr.cgi?pr=179413
___
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/179413: databases/py-sqlite3: running config *** Signal 10

2013-06-07 Thread Florian Smeets
The following reply was made to PR ports/179413; it has been noted by GNATS.

From: Florian Smeets 
To: bug-follo...@freebsd.org, ohart...@zedat.fu-berlin.de
Cc:  
Subject: Re: ports/179413: databases/py-sqlite3: running config *** Signal
 10
Date: Fri, 07 Jun 2013 20:49:30 +0200

 This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 --enig2PPODJIKRRJRVWSTLMMNN
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 You need to apply the patch from
 http://lists.freebsd.org/pipermail/svn-src-all/2013-June/069561.html to
 python and reinstall it.
 
 That should fix the py-sqlite3 build.
 
 
 --enig2PPODJIKRRJRVWSTLMMNN
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -BEGIN PGP SIGNATURE-
 
 iEYEARECAAYFAlGyKzsACgkQapo8P8lCvwnLOACeIQvYP1fpUQYWakb4w30P+IXu
 AK0AoJ609nYfXsIn6KxtAtHTmcCrtUHs
 =XGna
 -END PGP SIGNATURE-
 
 --enig2PPODJIKRRJRVWSTLMMNN--
___
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"


Fwd: svn commit: r250991 - in head: contrib/jemalloc/include/jemalloc include lib/libc/stdlib/jemalloc

2013-06-07 Thread Chris Rees
Hi all,

I don't know how many of you were following this, but it looks fine to
me... any of you mind if I commit it?

Chris


-- Forwarded message --
From: Marcel Moolenaar 
Date: 3 June 2013 15:50
Subject: Re: svn commit: r250991 - in head:
contrib/jemalloc/include/jemalloc include lib/libc/stdlib/jemalloc
To: Dimitry Andric 
Cc: svn-src-h...@freebsd.org, svn-src-...@freebsd.org, Marcel
Moolenaar , src-committ...@freebsd.org



On Jun 3, 2013, at 6:25 AM, Dimitry Andric  wrote:

> On 2013-05-25 20:59, Marcel Moolenaar wrote:
>> Author: marcel
>> Date: Sat May 25 18:59:11 2013
>> New Revision: 250991
>> URL: http://svnweb.freebsd.org/changeset/base/250991
>>
>> Log:
>>   Make the malloc(3) family of functions weak and make their non-weak
>>   implementations visible for use by applications. The functions $F that
>>   are now weak symbols are:
>>  allocm, calloc, dallocm, free, malloc, malloc_usable_size,
>>  nallocm, posix_memalign, rallocm, realloc, sallocm
>>
>>   The non-weak implementations of $F are exported as __$F.
>
> Hi Marcel,
>
> This commit seems to lead to various problems in ports, and possibly
> other software.  For example, with Firefox I now always get a few
> messages like:
>
>  firefox in free(): warning: malloc() has never been called
>
> Another example is the devel/talloc port, which now dies with:

It looks like the python build is broken. The net effect is that _ctypes.so
has a strong definition of malloc, free, et al. This is not intentional,
but a side-effect of the what seems to be a bug in fficonfig.py.in (see
patch below). To elaborate:

_ctypes.so incorporates the libffi functionality for what I presume is
the basis for Python bindings. libffi includes dlmalloc.c, an open source
allocator. dlmalloc.c is incuded by closures.c and closures.c defines
USE_DL_PREFIX. On top of that closures.c makes all allocator functions
static. This, by design there's no problem. In short: dlmalloc.c never
gets compiler separately/independently.

The python build however compiles dlmalloc.c separately/independently.
As such, dlmalloc.c now defines and exports malloc et al and it also
get linked into _ctypes.so.

Once _ctypes.so gets dynamically loaded, things start to break.

Unfortunately, this means python needs to be recompiled from ports with
the following fix:

Index: files/patch-Modules-_ctypes-libffi-fficonfig.py.in
===
--- files/patch-Modules-_ctypes-libffi-fficonfig.py.in  (revision 0)
+++ files/patch-Modules-_ctypes-libffi-fficonfig.py.in  (working copy)
@@ -0,0 +1,10 @@
+--- Modules/_ctypes/libffi/fficonfig.py.in.orig2013-06-03
07:16:44.0 -0700
 Modules/_ctypes/libffi/fficonfig.py.in 2013-06-03
07:17:03.0 -0700
+@@ -1,7 +1,6 @@
+ ffi_sources = """
+ src/prep_cif.c
+ src/closures.c
+-src/dlmalloc.c
+ """.split()
+
+ ffi_platforms = {

This has been tested with python-2.7.5. I can't say anything about
other versions.

Do people concur that this is the right fix?

--
Marcel Moolenaar
mar...@xcllnt.net


___
svn-src-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
___
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/179419: [PATCH] editors/leo: Leo depends on databases/py-sqlite3

2013-06-07 Thread edwin
Synopsis: [PATCH] editors/leo: Leo depends on databases/py-sqlite3

Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python
Responsible-Changed-By: edwin
Responsible-Changed-When: Fri Jun 7 20:40:14 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=179419
___
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/179419: [PATCH] editors/leo: Leo depends on databases/py-sqlite3

2013-06-07 Thread Michael Gmelin
The following reply was made to PR ports/179419; it has been noted by GNATS.

From: Michael Gmelin 
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: ports/179419: [PATCH] editors/leo: Leo depends on
 databases/py-sqlite3
Date: Fri, 7 Jun 2013 22:57:22 +0200

 --MP_/ey5hXOWV4OP6DV5J7WSWe7i
 Content-Type: text/plain; charset=US-ASCII
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline
 
 The original patch contained diffs of a backup file, please find
 attached a clean version.
 
 -- 
 Michael Gmelin
 
 --MP_/ey5hXOWV4OP6DV5J7WSWe7i
 Content-Type: text/x-patch
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment; filename=leo-4.10_4.patch
 
 diff -ruN ../leo.orig/Makefile ./Makefile
 --- ../leo.orig/Makefile   2013-06-07 04:23:22.0 +0200
 +++ ./Makefile 2013-06-07 22:23:24.251573605 +0200
 @@ -1,9 +1,5 @@
 -# New ports collection makefile for:  leo
 -# Date created:   2002/11/17
 -# Whom:   Alan Eldridge 
 -#
 +# Created by: Alan Eldridge 
  # $FreeBSD: editors/leo/Makefile 311476 2013-02-03 18:16:54Z makc $
 -#
  
  PORTNAME= leo
  PORTVERSION=  4.10
 @@ -19,10 +15,11 @@
  LICENSE=  MIT
  LICENSE_FILE= ${WRKSRC}/LICENSE.TXT
  
 -RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}qt4-svg>=0:${PORTSDIR}/graphics/py-qt4-svg \
 +RUN_DEPENDS=  
${PYTHON_PKGNAMEPREFIX}qt4-svg>=0:${PORTSDIR}/graphics/py-qt4-svg \

${PYTHON_PKGNAMEPREFIX}docutils>=0:${PORTSDIR}/textproc/py-docutils \
silvercity>=0:${PORTSDIR}/textproc/silvercity \
${PYTHON_PKGNAMEPREFIX}Pmw>=0:${PORTSDIR}/x11-toolkits/py-Pmw \
 +  
${PYTHON_PKGNAMEPREFIX}sqlite3>=0:${PORTSDIR}/databases/py-sqlite3 \

${PYTHON_PKGNAMEPREFIX}qt4-gui>=0:${PORTSDIR}/x11-toolkits/py-qt4-gui
  
  OPTIONS_DEFINE=   PYENCHANT DOCS
 
 --MP_/ey5hXOWV4OP6DV5J7WSWe7i--
___
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: svn commit: r250991 - in head: contrib/jemalloc/include/jemalloc include lib/libc/stdlib/jemalloc

2013-06-07 Thread Marcel Moolenaar

On Jun 7, 2013, at 12:13 PM, Chris Rees  wrote:

> Hi all,
> 
> I don't know how many of you were following this, but it looks fine to
> me... any of you mind if I commit it?

I sent the patch to rm@ (Ruslan) (and CC'd miwi@). Please sync up with him.

BTW1: I didn't know there was a python@ alias. Good to know.
BTW2: I found that python32 and python33 need the same fix.

-- 
Marcel Moolenaar
mar...@xcllnt.net


___
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"