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

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

Re: porting dash (the shell)

Eitan Adler wrote: if gcc -DBSD=1 -DSMALL -DSHELL -DGLOB_BROKEN -DFNMATCH_BROKEN -DIFS_BROKEN -D__COPYRIGHT\(x\)= -D__RCSID\(x\)= -D_DIAGASSERT\(x\)= -I. -I. -I.. -include ../config.h -g -O2 -Wall -MT exec.o -MD -MP -MF ".deps/exec.Tpo" \ -c -o exec.o `test -f 'exec.c' || echo './'`e

Re: porting dash (the shell)

Boris Kochergin wrote: > Eitan Adler wrote: >> if gcc -DBSD=1 -DSMALL -DSHELL -DGLOB_BROKEN -DFNMATCH_BROKEN >> -DIFS_BROKEN -D__COPYRIGHT\(x\)= -D__RCSID\(x\)= -D_DIAGASSERT\(x\)= -I. >> -I. -I.. -include ../config.h -g -O2 -Wall -MT exec.o -MD -MP -MF >> ".deps/exec.Tpo" \ >> -c -o e

porting dash (the shell)

if gcc -DBSD=1 -DSMALL -DSHELL -DGLOB_BROKEN -DFNMATCH_BROKEN -DIFS_BROKEN -D__COPYRIGHT\(x\)= -D__RCSID\(x\)= -D_DIAGASSERT\(x\)= -I. -I. -I.. -include ../config.h -g -O2 -Wall -MT exec.o -MD -MP -MF ".deps/exec.Tpo" \ -c -o exec.o `test -f 'exec.c' || echo './'`exec.c; \ then

Re: Automatically generate symlinks for virtual categories.

Newest version's Makefile is attached. -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen # New ports collection makefile for: symlink # Date created:Fri Jun 05 2009 # Whom:Eitan Adler # # $FreeBSD$ # PORTNAME=

Re: [Call For Testing] VirtualBox for FreeBSD!

Good evening everyone. Earlier today, I finished a VBox build on a fresh system. After the build succeeded, I 'kldload /boot/modules/vboxdrv.ko' which caused a panic. The machine runs a GENERIC kernel with KDB and KDB_UNATTENDED added -- no other changes. -- The machine -- FreeBSD orion 7.2-STA

Re: Ports with duplicate LATEST_LINKS

On Fri, 5 Jun 2009 14:40:09 GMT Erwin Lansing mentioned: > Dear port maintainers, > > The following list includes ports maintained by you that have duplicate > LATEST_LINK values. They should either be modified to use a unique > LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriti

Ports with duplicate LATEST_LINKS

Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Re: MAKE_JOBS_UNSAFE (some more ports)

On Sat, 6 Jun 2009 18:05:14 +0200 David Naylor wrote: > P.S. Is anyone interested in a list of ports that do not compile > under tmpfs? Me. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd

Re: emulators/kqemu-kmod-devel: Exec format error

Thus spake Juergen Lock [Sat, 6 Jun 2009 19:11:13 +0200 (CEST)]: : >kqemu-kmod-devel is failing to load for me: : > : >- : ># kldload kqemu : >kldload: can't load kqemu: Exec format error : ># : >- : : Weird. Anything in dmesg? Agreed. And nope, nothing in dmesg. : >It's been about a

Re: emulators/kqemu-kmod-devel: Exec format error

In article <20090604211814.d065d4a7.dge...@afflictions.org> you write: >kqemu-kmod-devel is failing to load for me: > >- ># kldload kqemu >kldload: can't load kqemu: Exec format error ># >- > Weird. Anything in dmesg? >It's been about a month since I last used qemu, and my kernel is -CUR

Re: MAKE_JOBS_UNSAFE (some more ports)

On Thursday 21 May 2009 13:56:46 Pav Lucistnik wrote: > On Thu, 21 May 2009 12:05:22 +0200, David Naylor wrote > > > The following ports failed to build on my system (with a quad core) > > and FORCE_MAKE_JOBS set. They did success to build once I added > > MAKE_JOBS_UNSAFE=yes to their Makefile's

Re: request for exp-run, comments: eliminate USE_X_PREFIX

On Sat, Jun 06, 2009 at 05:36:26PM +0200, Pav Lucistnik wrote: > > > Also I forgot to mention that this is better to be run on i386, as many > > ports depend on xview which is i386-only. > > i386 is operated by erwin@ so try talking to him. But I must warn you > that i386 run will take about a we

Re: request for exp-run, comments: eliminate USE_X_PREFIX

* Pav Lucistnik (p...@freebsd.org) wrote: > > Also I forgot to mention that this is better to be run on i386, as many > > ports depend on xview which is i386-only. > > i386 is operated by erwin@ so try talking to him. But I must warn you > that i386 run will take about a week, due to much older h

Re: request for exp-run, comments: eliminate USE_X_PREFIX

Dmitry Marakasov píše v so 06. 06. 2009 v 07:13 +0400: > * Pav Lucistnik (p...@freebsd.org) wrote: > > > The experimental run is nearly over, so far 15 failures found and sent > > in separate mails. > > > > Once you have next iteration of the patch, I'll be happy to run it > > again. > > Here's

Re: what does this mean?

On Sat, Jun 6, 2009 at 10:03 AM, dan hirsch wrote: > 1. > > Running the csup(1)< > http://www.freebsd.org/cgi/man.cgi?query=csup&sektion=1>command > later will download and apply all the recent changes to your Ports > Collection, except actually rebuilding the ports for your own system. > >

what does this mean?

1. Running the csup(1)command later will download and apply all the recent changes to your Ports Collection, except actually rebuilding the ports for your own system. -- regards, Dan Hirsch Linked-In: http://www.linkedin.com/in

Re: Benchmark

From: Scott Long Subject: Re: Benchmark [Re: [Call For Testing] VirtualBox for FreeBSD! take 4] Date: Sat, 06 Jun 2009 00:44:24 -0600 > Maho NAKATA wrote: >> I did a benchmark with Virtualbox: >> My environment: >> * Core 2 Quad, q6...@3ghz >> * Windows XP s...@host s...@vbox with GuestAddon >> *

Two VirtualBox processes and do not launch VirtualBox: kill one of them.

From: Yamagi Burmeister Subject: Re: Benchmark [Re: [Call For Testing] VirtualBox for FreeBSD! take 4] Date: Sat, 06 Jun 2009 09:20:42 +0200 > Hello, > >> Usually I cannot usually launch VirtualBox even by root. >> A workaround is that invoking and killing VirtualBox >> many times for me. After s

Re: MAKE_JOBS_UNSAFE (some more ports)

Hi David and * thanks for your patch, I verified and committed. Best, From: Ion-Mihai Tetcu Subject: Re: MAKE_JOBS_UNSAFE (some more ports) Date: Sat, 06 Jun 2009 02:39:42 +0300 > On Sat, 06 Jun 2009 08:26:01 +0900 (JST) > Maho NAKATA wrote: > >> From: Ion-Mihai Tetcu >> Subject: Re: MAKE_JOB

SOLVED: p5-HTML-Mason with broken dependency to p5-Exception-Class!

Nicolais wrote: > > I was wondering if anyone can find an updated status on p5-HTML-Mason, if > the maintainer is not replying to mails. > ... > The reason is, the new Exception::Class has already made it into the ports > tree at May 11th, and I'm holding back on updating this, since Mason < > 1

mysql 4->5 problem

going from mysql 4 to 5.1.34. server will not start. diag is 090606 8:56:28 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'host'; try to repair it 090606 08:56:28 mysqld_safe mysqld from pid file /var/db/mysql/psg.com.pid ended googling around gets me

Re: Benchmark [Re: [Call For Testing] VirtualBox for FreeBSD! take 4]

Hello, > Usually I cannot usually launch VirtualBox even by root. > A workaround is that invoking and killing VirtualBox > many times for me. After some tries I can launch... maybe this workaround helps (as user, not as root): 1. Launch VirtualBox. 2. If it fails open top(1) 3. In top(1) you shou

Re: Benchmark [Re: [Call For Testing] VirtualBox for FreeBSD! take 4]

Maho NAKATA wrote: I did a benchmark with Virtualbox: My environment: * Core 2 Quad, q6...@3ghz * Windows XP s...@host s...@vbox with GuestAddon * http://crystalmark.info/software/CrystalMark/ CrystalMark 2004R3 * Sapphire X1650 * VBOX is running on FBSD7.2-REL/amd64 using http://people.free