INDEX build failed for 8.x

2013-03-10 Thread indexbuild
INDEX build failed with errors: Generating INDEX-8 - please wait.."/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 20: warning: duplicate script for target "check-pbimanager" ignored "/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 45: warning: duplicate script for target "pbi-generate" ig

INDEX now builds successfully on 8.x

2013-03-10 Thread indexbuild
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-10 Thread O. Hartmann
On FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 I receive the error message below when trying to update installed port openldap24-sasl-client: ===> Cleaning for openldap-sasl-client-2.4.33_1 ===>>> Waiting on fetch & checksum for net/openldap24-sasl-client <<<=== ===> openldap-

FreeBSD ports you maintain which are out of date

2013-03-10 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: FreeBSD Port: pftop-0.7_1

2013-03-10 Thread Fabian Keil
Fabian Keil wrote: > Thomas Kinsey wrote: > > > I've noticed that rule numbers do not display in pftop, and further that > > this > > (http://openbsd.7691.n7.nabble.com/pftop-Rule-number-shown-as-quot-0-quot-or-quot-quot-td122537.html) > > seems to resolve the issue. > > > > Not being fluen

Re: VirtualBox broken by recent commit -248084

2013-03-10 Thread Chris Rees
On 10 Mar 2013 07:07, "AN" wrote: > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > Virtualbox was broken by this commit: > http://svnweb.freebsd.org/base?view=revision&revision=248084 > > ===>

Re: VirtualBox broken by recent commit -248084

2013-03-10 Thread Sergio de Almeida Lenzi
Em Dom, 2013-03-10 às 15:43 +, Chris Rees escreveu: > On 10 Mar 2013 07:07, "AN" wrote: > > > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > > > Virtualbox was broken by this commit: > >

Re: VirtualBox broken by recent commit -248084

2013-03-10 Thread AN
On Sun, 10 Mar 2013, Chris Rees wrote: On 10 Mar 2013 07:07, "AN" wrote: > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > Virtualbox was broken by this commit: > http://svnweb.freebsd.or

Re: nvidia-driver broken by recent commit - 248084

2013-03-10 Thread Brandon Gooch
On Sun, Mar 10, 2013 at 1:17 AM, AN wrote: > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > /usr/ports/x11/nvidia-driver is broken, probably by this commit: > http://svnweb.freebsd.org/base?vi

Re: VirtualBox broken by recent commit -248084

2013-03-10 Thread AN
On Sun, 10 Mar 2013, Sergio de Almeida Lenzi wrote: Em Dom, 2013-03-10 as 15:43 +, Chris Rees escreveu: On 10 Mar 2013 07:07, "AN" wrote: > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64

Re: nvidia-driver broken by recent commit - 248084

2013-03-10 Thread AN
On Sun, 10 Mar 2013, Brandon Gooch wrote: On Sun, Mar 10, 2013 at 1:17 AM, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 /usr/ports/x11/nvidia-driver is broken, probably by this com

Re: Re: [RFC] lang/pypy

2013-03-10 Thread David Naylor
On Sunday, 10 March 2013 00:37:15 poyop...@puripuri.plala.or.jp wrote: > Hi, good work, David. Hi Kuro > It compiles, packages and works flawlessly here for replacement of 1.9 > so far for a week. Great, thanks. Good to know :-) > On my compile box, amd64/Athlon64 5050e 2.6GHz 2 core/8GB, > m

Warnings from "make index"

2013-03-10 Thread Peter Jeremy
For the past several days, I've been getting the following. I haven't yet tracked down the commit that caused it. Generating INDEX-8 - please wait.."/usr/ports/Mk/bsd.pbi.mk", line 20: warning: duplicate script for target "check-pbimanager" ignored "/usr/ports/Mk/bsd.pbi.mk", line 45: warning: d

Re: Warnings from "make index"

2013-03-10 Thread Chris Rees
On 10 March 2013 19:22, Peter Jeremy wrote: > For the past several days, I've been getting the following. I haven't > yet tracked down the commit that caused it. > > Generating INDEX-8 - please wait.."/usr/ports/Mk/bsd.pbi.mk", line 20: > warning: duplicate script for target "check-pbimanager" i

CFT mplayer and mencoder snapshot

2013-03-10 Thread Thomas Zander
Hi folks, I have prepared a recent snapshot of mplayer and mencoder. The port itself has changed quite a bit, therefore testing and reporting (and patches if necessary) are greatly appreciated. The port tarballs can be found here: https://bsdistfiles.googlecode.com/files/m20130310.tar.xz Main cha

Re: [RFC] lang/pypy

2013-03-10 Thread poyopoyo
Hi David, At Sun, 10 Mar 2013 21:18:12 +0300, David Naylor wrote: > > however my translation processes under -DPYPY_IGNORE_MEMORY take 2GB > > for normal binary and 2.5GB for sandboxed one so they aggregate 4.5GB > > to run parallel. > > This is good news. Could you please detail how you measur

20130308 UPDATING: folks, libgee

2013-03-10 Thread Lowell Gilbert
I am mildly confused by the UPDATING warning on the repocopies for net-im/folks and devel/libgee. Is the intention that *everybody* should be using the repocopied versions? Will there be a point in the future where we switch back to the base ports? ___ fr

Re: Warnings from "make index"

2013-03-10 Thread Chris Rees
On 10 March 2013 19:49, Chris Rees wrote: > On 10 March 2013 19:22, Peter Jeremy wrote: >> For the past several days, I've been getting the following. I haven't >> yet tracked down the commit that caused it. >> >> Generating INDEX-8 - please wait.."/usr/ports/Mk/bsd.pbi.mk", line 20: >> warning

Installing empathy-2.32.2_3...warning: undefined reference

2013-03-10 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Making install in src gmake[1]: Entering directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake install-am gmake[2]: Entering directory

Re: Installing empathy-2.32.2_3...warning: undefined reference

2013-03-10 Thread Koop Mast
On 10-3-2013 22:29, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Thanks for the report, this is already known. Sadly I haven't managed to find a solution for this :/ -Koop Making inst

x11-toolkits/pango update to 1.30 fails to build

2013-03-10 Thread gtodd
Posting this for the benefit of search engines and seekers. Following the most recent ports update to pango (svn 313633) I was unable to get it to build properly until I rebuilt cairo with this bit flipped: WITH GLIB "Enable GObject Functions Feature" A bunch of interdependent ports (glib gt

Re: Warnings from "make index"

2013-03-10 Thread Bryan Drewery
On 3/10/2013 2:49 PM, Chris Rees wrote: > On 10 March 2013 19:22, Peter Jeremy wrote: >> For the past several days, I've been getting the following. I haven't >> yet tracked down the commit that caused it. >> >> Generating INDEX-8 - please wait.."/usr/ports/Mk/bsd.pbi.mk", line 20: >> warning: d

Re: lang/ruby19: ruby-1.9.3.392, 1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-10 Thread Steve Wills
> > I try to compile port lang/ruby19 and I always get on a FreeBSD > 9.1-STABLE box the following error message, which is obviously triggered > by some port auditing - but I do not find the "knob" to switch it off. > > Can someone give a hint, please? > This shouldn't be happening. Perhaps your