[update] graphics/py-soya3d

2011-12-09 Thread green dog
update to 0.15rc1 diff -ruN py-soya3d/Makefile py-soya3d.new/Makefile --- py-soya3d/Makefile 2010-04-28 01:58:27.0 +0400 +++ py-soya3d.new/Makefile 2011-11-25 14:26:36.0 +0400 @@ -6,12 +6,12 @@ # PORTNAME= soya3d -PORTVERSION= 0.14 -PORTREVISION= 5 +DISTVERSION=

pr# for 9->10 problem?

2011-12-09 Thread Robert Huff
There is a problem building various ports caused by the FreeBSD major version number going from 9 to 10 (specifically, from single to double digits). My morning brain has been unable to find this in the PR database; would some kind soul please help? Thanks,

-fstack-protector again (rpm4, BROKEN textproc/libextractor)

2011-12-09 Thread Juergen Lock
Hi! I got a report that textproc/libextractor was marked BROKEN on i386 which one of my ports uses, so with the help of swill's tb (I don't really use i386 myself here anymore so thanx for that :) I took a look. The failed libextractor log seem to be this one: http://pointyhat.freebsd.

Update tutorial about Centreon and FreeBSD

2011-12-09 Thread Luiz Gustavo
Hi Friends, I just posted on my blog an update installation of Centreon in FreeBSD is now available a complete tutorial and revised on versions 2.3.3 (last) in an environment with Centreon and FreeBSD 9.0-RC3 Check in: http://www.luizgustavo.pro.br/blog/2011/12/09/english-centreon-2-3-3-freebsd-9

Re: pr# for 9->10 problem?

2011-12-09 Thread Doug Barton
On 12/09/2011 09:06, Robert Huff wrote: > > There is a problem building various ports caused by the FreeBSD > major version number going from 9 to 10 (specifically, from single > to double digits). > My morning brain has been unable to find this in the PR > database; would some kind so

FreeBSD ports which are currently marked forbidden

2011-12-09 Thread linimon
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, inclu

FreeBSD unmaintained ports which are currently scheduled for deletion

2011-12-09 Thread linimon
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 th

FreeBSD unmaintained ports which are currently marked broken

2011-12-09 Thread linimon
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common probl

Re: pr# for 9->10 problem?

2011-12-09 Thread Robert Huff
Doug Barton writes: > >There is a problem building various ports caused by the FreeBSD > > major version number going from 9 to 10 (specifically, from single > > to double digits). > >My morning brain has been unable to find this in the PR > > database; would some kind soul please he

Re: pr# for 9->10 problem?

2011-12-09 Thread Doug Barton
On 12/09/2011 12:20, Robert Huff wrote: > > Doug Barton writes: > >> > There is a problem building various ports caused by the FreeBSD >> > major version number going from 9 to 10 (specifically, from single >> > to double digits). >> > My morning brain has been unable to find this in the

Re: again, ports that stop daemons

2011-12-09 Thread Baptiste Daroussin
On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: > on 02/12/2011 21:55 Baptiste Daroussin said the following: > > On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: > >> On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon wrote: > >>> > >>> Or that they simply quit doing that

Re: again, ports that stop daemons

2011-12-09 Thread Doug Barton
On 12/09/2011 13:18, Baptiste Daroussin wrote: > On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: >> on 02/12/2011 21:55 Baptiste Daroussin said the following: >>> On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon wrot

Re: kdelibs4 4.7.3 Build Fails FreeBSD 9-CURRENT

2011-12-09 Thread Aric Gregson
All installed and working. Needed to reinstall some packages first and then it went just fine. Thanks, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-uns

Re: kdelibs4 4.7.3 Build Fails FreeBSD 9-CURRENT

2011-12-09 Thread Ben Franklan
Had some similar issues with kdelibs4 4.7.3 on a fresh FreeBSD 9.0 RC2 amd64 system. I just did a 'make -j1' and it built fine. Ben Franklan > Trying to update from KDE 4.7.2 to 4.7.3 on FreeBSD 9.0-CURRENT #0: Tue > Jul 19 16:18:20 PDT 2011. I have run into the following error > repeatedly now an

Re: again, ports that stop daemons

2011-12-09 Thread Baptiste Daroussin
On Fri, Dec 09, 2011 at 01:25:25PM -0800, Doug Barton wrote: > On 12/09/2011 13:18, Baptiste Daroussin wrote: > > On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: > >> on 02/12/2011 21:55 Baptiste Daroussin said the following: > >>> On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ing

Clicking URLs with acroread8

2011-12-09 Thread Doug Barton
I receive PDF documents with URLs that I need to click, and so I would like to get that working in acroread8. I symlink'ed firefox into /compat/linux/usr/local/bin, and set the preferences in acroread accordingly. That got me from a "firefox not found" error to this, printed out in the terminal: l

astro/xephem: make readme failure

2011-12-09 Thread Conrad J. Sabatier
>Submitter-Id: current-users >Originator:Conrad J. Sabatier >Organization: >Confidential: no >Synopsis: astro/xephem: make readme failure >Severity: non-critical >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 9.0-PRERELEASE amd64 >Environme