python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread James Chang
Der Sir, When I build python26 from FreeBSD ports, it shown me the following ERROR messages: <-root->make depend all ===> Vulnerability check disabled, database not found ===> Found saved configuration for python26-2.6.2

Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread David Southwell
> > Der Sir, > > > > When I build python26 from FreeBSD ports, it shown me the > > following ERROR messages: > > > > > > <-root->make depend all > > ===> Vulnerability check disabled, database not found > > ===> Found save

Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread David Southwell
> > Der Sir, > > > > When I build python26 from FreeBSD ports, it shown me the > > following ERROR messages: > > > > > > <-root->make depend all > > ===> Vulnerability check disabled, database not found > > ===> Found save

Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread David Southwell
> Der Sir, > > When I build python26 from FreeBSD ports, it shown me the > following ERROR messages: > > > <-root->make depend all > ===> Vulnerability check disabled, database not found > ===> Found saved configuration

Re: ports/138835: Python compile failure

2009-09-15 Thread David Southwell
> Synopsis: Python compile failure > > State-Changed-From-To: open->closed > State-Changed-By: miwi > State-Changed-When: Tue Sep 15 08:16:58 UTC 2009 > State-Changed-Why: > Sorry I can't confirm this error: > > [10:17] r...@miwi /usr/home/miwi/dev/ports/lang/python26# make patch > ===> Found sa

Premature closure of PRs

2009-09-15 Thread David Southwell
I want to understand why bug reports get closed prematurely and without any discussion with the original person submitting the report. For example I submitted PR today in connection with a bug I originally reported to both the ports and the python lists last week. When there was no immediate f

Re: Premature closure of PRs

2009-09-15 Thread David Southwell
> I want to understand why bug reports get closed prematurely and without any > discussion with the original person submitting the report. > > For example I submitted PR today in connection with a bug I originally > reported to both the ports and the python lists last week. When there was > no im

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread edwin
Synopsis: lang/python26 compile failure Responsible-Changed-From-To: freebsd-ports-bugs->python Responsible-Changed-By: edwin Responsible-Changed-When: Tue Sep 15 09:30:19 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cg

Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread David Southwell
> > > Der Sir, > > > > > > When I build python26 from FreeBSD ports, it shown me the > > > following ERROR messages: > > > > > > > > > <-root->make depend all > > > ===> Vulnerability check disabled, database not found > >

Re: [HEADSUP]: Ports feature freeze now enforced

2009-09-15 Thread David Southwell
> As an experiment, there will not be a complete ports freeze ahead of the > release of 8.0. To ensure that the tree is kept in a stable condition, > we do need to have more discipline about the feature freeze we are > currently using. To achieve this, I have added a new tag to the commit > log F

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread David Southwell
The following reply was made to PR ports/138837; it has been noted by GNATS. From: David Southwell To: bug-follo...@freebsd.org, da...@vizion2000.net Cc: Subject: Re: ports/138837: lang/python26 compile failure Date: Tue, 15 Sep 2009 11:07:36 +0100 Re: ports/138835: Python compile failure N

Re: ports/138835: Python compile failure

2009-09-15 Thread David Southwell
> David sorry but stop your agressive blaming here, > first you come not without any more infos only it failed > secound we are all humons and do sometimes mistakes so, > now show me your 'make showconfig" and "uname -a" > > Thx! > > On Tue, Sep 15, 2009 at 11:05:27AM +0100, David Southwell wrote

Re: ports/138835: Python compile failure

2009-09-15 Thread Martin Wilke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David sorry but stop your agressive blaming here, first you come not without any more infos only it failed secound we are all humons and do sometimes mistakes so, now show me your 'make showconfig" and "uname -a" Thx! On Tue, Sep 15, 2009 at 11:05

Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree

2009-09-15 Thread Kenyon Ralph
On 2009-09-15T10:08:52+0100, David Southwell wrote: > > I want to understand why bug reports get closed prematurely and without any > > discussion with the original person submitting the report. ... > > Yrs frustrated > > David Southwell > ps the PR link is: > http://www.freebsd.org/cgi/query-pr

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread edwin
Synopsis: lang/python26 SEM option problem Responsible-Changed-From-To: freebsd-ports-bugs->python Responsible-Changed-By: edwin Responsible-Changed-When: Tue Sep 15 11:30:44 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr

Re: ports/138835: Python compile failure

2009-09-15 Thread Martin Wilke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Sep 15, 2009 at 11:28:17AM +0100, David Southwell wrote: > > 1. There has been no blaming only politelly asking question which in the > circumstances seem appropriate. > 2. output of uname -a is included in my reports both ion the PRs and the

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread miwi
Synopsis: lang/python26 SEM option problem State-Changed-From-To: open->feedback State-Changed-By: miwi State-Changed-When: Tue Sep 15 13:13:01 UTC 2009 State-Changed-Why: Please test following patch: http://tmp.chruetertee.ch/python26-sem-hack.patch http://www.freebsd.org/cgi/query-pr.cgi?pr

Re: ports/138843: [maintainer] www/py-amf update to 0.5

2009-09-15 Thread edwin
Synopsis: [maintainer] www/py-amf update to 0.5 Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python Responsible-Changed-By: edwin Responsible-Changed-When: Tue Sep 15 13:30:25 UTC 2009 Responsible-Changed-Why: freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool) http:

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread Kamil Deryński
2009/9/15 : > Synopsis: lang/python26 SEM option problem > > State-Changed-From-To: open->feedback > State-Changed-By: miwi > State-Changed-When: Tue Sep 15 13:13:01 UTC 2009 > State-Changed-Why: > > Please test following patch: > > http://tmp.chruetertee.ch/python26-sem-hack.patch > > > http://ww

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread Martin Wilke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Sep 15, 2009 at 03:51:59PM +0200, Kamil Dery??ski wrote: > 2009/9/15 : > > Synopsis: lang/python26 SEM option problem > > > > State-Changed-From-To: open->feedback > > State-Changed-By: miwi > > State-Changed-When: Tue Sep 15 13:13:01 UTC 2009

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread Kamil Deryński
2009/9/15 Martin Wilke : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, Sep 15, 2009 at 03:51:59PM +0200, Kamil Dery??ski wrote: >> 2009/9/15  : >> > Synopsis: lang/python26 SEM option problem >> > >> > State-Changed-From-To: open->feedback >> > State-Changed-By: miwi >> > State-Chan

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread Martin Wilke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Really sorry but I can't confirm your problem: http://nopaste.unixfreunde.de/3815 - - Martin On Tue, Sep 15, 2009 at 05:33:51PM +0200, Kamil Dery??ski wrote: > 2009/9/15 Martin Wilke : > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread David Southwell
I agree the bug is solely related to the semaphores option. It compiles fine with sem turned off on my 7.2-p3 intel quad core system. I have tried the patches with the sem option on but that does not solve that compile failure. David ___ freebsd-python

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread David Southwell
The following reply was made to PR ports/138837; it has been noted by GNATS. From: David Southwell To: bug-follo...@freebsd.org, da...@vizion2000.net Cc: freebsd-po...@freebsd.org, freebsd-python@freebsd.org, freebsd-ports-b...@freebsd.org, Martin Wilke Subject: Re: ports/138837: lang/python

Re: ports/138839: lang/python26 SEM option problem

2009-09-15 Thread Kamil Deryński
2009/9/15 Martin Wilke : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Really sorry but I can't confirm your problem: > > http://nopaste.unixfreunde.de/3815 Ok, I am sorry, it works. I don't know exacly what kind of problem cause this error. Please try compile it without Gnu PTH, do you ha

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread Martin Wilke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Sep 15, 2009 at 06:17:19PM +0100, David Southwell wrote: > I agree the bug is solely related to the semaphores option. It compiles fine > with sem turned off on my 7.2-p3 intel quad core system. I have tried the > patches with the sem option

Re: ports/138853: New Port: x11-toolkits/py-traitsGui

2009-09-15 Thread edwin
Synopsis: New Port: x11-toolkits/py-traitsGui Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python Responsible-Changed-By: edwin Responsible-Changed-When: Tue Sep 15 18:00:31 UTC 2009 Responsible-Changed-Why: freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool) http://

Re: ports/138837: lang/python26 compile failure

2009-09-15 Thread miwi
Synopsis: lang/python26 compile failure State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Tue Sep 15 21:45:27 UTC 2009 State-Changed-Why: please update your portstree a fix was committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=138837 _