FreeBSD unmaintained ports which are currently marked broken

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

FreeBSD ports which are currently marked broken

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

FreeBSD unmaintained ports which are currently scheduled for deletion

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 ports which are currently scheduled for deletion

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 forbidden

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 ports which are currently marked forbidden

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

Re: anyone able to build jboss4 on amd64?

Hi, Vivek! Sorry for a long silence, I was AFK. On Thu, Aug 30, 2007 at 11:33:53AM -0400, Vivek Khera wrote: > On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote: > > >Which threading libraries do you use? I remember having similar problem with > >libthr.so enabled in libmap.conf. As soon as I

FreeBSD Port: pciids-20070801

___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: gnash 0.8.0

Dmitry Marakasov-2 wrote: > > Hi! > > Sorry for the long delay with gnash port update to 0.8.0. Many things > happened, but now I finally have some spare time. > > Here's preliminary version of 0.8.0 port. It (hopefully) builds and > it (more or less) supports many gnash build options such as

Re: textproc/p5-XML-LibXML Install Error

Hi! On Fri, Aug 31, 2007 at 11:10:08AM -0700, Cy Schubert wrote: > Has anyone seen this before. This is on the AMD64 platform running FreeBSD > AMD64 with most ports (the ones that would build that is) built for AMD64. > Perl 5.8.8 was built successfully for AMD64. This builds and installs when

blas: discrepancies in the downloaded file size and the size declared in distinfo

My system is a brand new hp laptop with intel dual core T5300 processor and hpbsd# uname -a FreeBSD hpbsd.vic 6.2-RELEASE-p6 FreeBSD 6.2-RELEASE-p6 #1: Wed Jul 18 22:53:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HP02 i386 Today's latest portsnap If I try to compile the blas librar

Re: ports/116078: bsd.port.mk - Handling of PREFIX doesn't work as documented

Pav, I took the freedom to put this onto the list for a broader participation. Gentlemen, it looks like the ports mechanism is incapable of building it's dependencies in some situations, especially if PREFIX is set. I've already filed a bug about this topic at

Re: ports tree out've sync

On Tue 2007-08-14 (17:47), Kris Kennaway wrote: > > similarly for portaudit: > > > > # portaudit -F > > auditfile.tbz 100% of 43 kB 1016 kBps > > portaudit: Database too old. > > Old database restored. > > portaudit: Download failed. > > That's bizarre because po

i2p from ports doesn't work

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've a problem installing/using i2p on FreeBSD 6.2#p7 and FreeBSD-CURRENT using jdk14 as well as jdk15: I have i2p_enable="YES" i2p_user="i2p" in /etc/rc.conf. As User i2p I did an "i2prouter install". When I now try to start i2p using /usr/lo

Re: ports/116078: bsd.port.mk - Handling of PREFIX doesn't work as documented

Markus Hitter wrote: Pav, I took the freedom to put this onto the list for a broader participation. Gentlemen, it looks like the ports mechanism is incapable of building it's dependencies in some situations, especially if PREFIX is set. I've already filed a bug about this topic at

Re: ports/116078: bsd.port.mk - Handling of PREFIX doesn't work as documented

Am 04.09.2007 um 17:08 schrieb Kris Kennaway: To reiterate: in most but not all configurations, users who set PREFIX to a nonstandard location should also set LOCALBASE to the same location. If any documentation needs to be corrected to clarify this, please redirect your PR as a documenta

Re: ports/116078: bsd.port.mk - Handling of PREFIX doesn't work as documented

Markus Hitter wrote: Am 04.09.2007 um 17:08 schrieb Kris Kennaway: To reiterate: in most but not all configurations, users who set PREFIX to a nonstandard location should also set LOCALBASE to the same location. If any documentation needs to be corrected to clarify this, please redirect you

Re: FreeBSD Port: ntop-3.3

On Thu, Aug 30, 2007 at 02:04:29PM +0200, [EMAIL PROTECTED] wrote: > Hi, > I'm using ntop 3.3 with FreeBSD 6.2-STABLE , I use it mostely to monitor > netflow flows from cisco routers. After a few seconds ntop stops answering > and the browser is in the state "waiting". > This repeats all the ti

Re: i2p from ports doesn't work

Will look at it later but try: ./runplain.sh intead of the rc file ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: gnash 0.8.0

On Tue, 4 Sep 2007, Atrox wrote: Dmitry Marakasov-2 wrote: Hi! Sorry for the long delay with gnash port update to 0.8.0. Many things happened, but now I finally have some spare time. Here's preliminary version of 0.8.0 port. It (hopefully) builds and it (more or less) supports many gnash b

Re: mysql51-server doesn't start

On 9/4/07, TooMany Secrets <[EMAIL PROTECTED]> wrote: > 2007/9/3, Benno <[EMAIL PROTECTED]>: > > > sudo /usr/local/etc/rc.d/mysql-server start > > Password: > > Starting mysql. > > > [: -eq: unexpected operator > > Excuse me (i'm not a guru or similar), but did you try to look at > mysql-server.sh

Re: i2p from ports doesn't work

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Thoenen wrote: > Will look at it later but try: > > ./runplain.sh intead of the rc file > This seems to work. There were 20 java processes running after the first launch, so I changed runplain.sh to produce some output in nohup.out: # cat noh

portupgrade exits immediately when stdin/out closed

I'm debugging a problem with portupgrade being used as part of an automated package handler within puppet (http://puppet.reductivelabs.com). The problem is that when the handler executes portupgrade as an external process from ruby, portupgrade hangs with a script process taking up 100% of the c

Re: ports system and umask

On Sun, Sep 02, 2007 at 06:49:51PM +0200, mato wrote: > Kris Kennaway wrote: > >martinko wrote: > >> > >>We have similar problems here -- default umask is set to 027 and > >>therefore one needs to always remember changing it to 022 prior > >>installing any ports or packages. > >>Been bitten many