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

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

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

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

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,

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,

Re: security/gorilla is broken by lang/itcl update

Hi, J. Porter Clark, 07.07.10, 04:37h CEST: A recent revision of lang/itcl has apparently broken security/gorilla, which now pops up a window which says: The Password Gorilla requires the [incr Tcl] add-on to Tcl. Please install the [incr Tcl] package. I've tried reinstalling

Re: Virtualbox consuming wcpu

-Original Message- From: freebsd-ports-requ...@freebsd.org Reply-to: freebsd-ports@freebsd.org To: freebsd-ports@freebsd.org Subject: freebsd-ports Digest, Vol 372, Issue 3 Date: Wed, 7 Jul 2010 06:30:02 + (UTC) I recently upgraded to the new port version of virtualbox - 3.2.6. After

Re: audio/squeezeboxserver still broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/06/10 19:57, Brooks Davis wrote: On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote: Emanuel Haupt writes: George Hartzell hartz...@alerce.com wrote: Emanuel Haupt writes: Hi The current

Re: devel/subversion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 andrew clarke wrote: On Wed 2010-07-07 02:06:39 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: Can anyone confirm that subversion fails to build with www/neon28 and requires www/neon29? This is not mentioned in UPDATING. Building

FreeBSD 8 SSP challenge? [cacti-spine === Script configure failed unexpectedly]

At the request of the maintainer, I am opening this up to the wider audience here on po...@. Trying to get cacti-spine to build on FreeBSD 8 and getting stuck. checking whether we are using Solaris privileges... no checking for mysql_init in -lmysqlclient_r... yes checking for mysql_thread_init

Re: devel/subversion

On Wed, Jul 7, 2010 at 10:02 AM, Greg Larkin glar...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 andrew clarke wrote: On Wed 2010-07-07 02:06:39 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote: Can anyone confirm that subversion fails to build with www/neon28 and

Re: audio/squeezeboxserver still broken

Brooks Davis writes: On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote: Emanuel Haupt writes: George Hartzell hartz...@alerce.com wrote: Emanuel Haupt writes: Hi The current audio/squeezeboxserver port is still broken for me. I just

Re: audio/squeezeboxserver still broken

George Hartzell writes: Brooks Davis writes: On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote: Emanuel Haupt writes: George Hartzell hartz...@alerce.com wrote: Emanuel Haupt writes: Hi The current audio/squeezeboxserver port

Request for removal of ports maintainership

Hi, I'm currently removing things from my tasklist that I don't have time to work on, or pay attention to, and I have a handful of ports that I should be removed from the maintainership for: archivers/py-lzma archivers/py-tarfile comms/py-serial devel/py-ctypes devel/py-nose devel/py-plex

Re: Request for removal of ports maintainership

done. ___ 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

portmaster --packages-if-newer but forcing some ports to compile from source

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 is there a way to force portmaster to always build a particular port from source? Perhaps something like the existence of a file: /var/db/pkg/*/PM_ALWAYS_USE_PORT I am using portmaster -aDB --packages-if-newer in a regular basis to update

Re: portmaster --packages-if-newer but forcing some ports to compile from source

On Wed, Jul 7, 2010 at 7:36 PM, Manuel Chaviano ma...@computer.org wrote: is there a way to force portmaster to always build a particular port from source? Perhaps something like the existence of a file:        /var/db/pkg/*/PM_ALWAYS_USE_PORT I am using portmaster -aDB --packages-if-newer