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 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 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 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: FreeBSD ports Problem Reports for ports you maintain

lini...@freebsd.org writes: Hello, PR number: 87397 PR title: [patch] incorrect use of PAPERSIZE make variable in some ports category: print portname: lpr-wrapper submitter: ga...@zahemszky.hu arrival date: 2005-10-13 20:40:18 PR

Re: FreeBSD ports which are currently marked broken

On 21/06/2010 08:31, lini...@freebsd.org wrote: portname: x11-drivers/input-wacom broken because: build failed build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-driversportname=input-wacom

Call for testers: sysutils/3dm

I need testers for an update to the sysutils/3dm port. If you want to help test the patch, begin by downloading it from here: http://vivi.cat.pdx.edu/3dm2/sysutils_3dm.patch.txt You can apply the patch by issuing the command: cd /usr/ports/sysutils/3dm patch /path/to/sysutils_3dm.patch.txt

Now OK (Re: cvs commit: ports/ftp/hsftp Makefile)

ftp/hsftp, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck

Re: Who to bug to commit some ports ?

Hello, I recently submitted some PRs for updates and new ports and would like to know whom to ask for them to be committed. Yes, I know, I can try to bug some ports committers using e-mail 8-), but if possible, I would like to avoid this 8-) It's approx. 8 days later, and the ports are still

Re: Who to bug to commit some ports ?

Hi! - java/dbvis, update to new dbvis version http://www.freebsd.org/cgi/query-pr.cgi?pr=147493 I grabbed this one and will try to get to it this week. There is a newer of dbvis version available (7.1). Should I update my patch or how is this supposed to be handled ? -- p...@opsec.eu

Re: Who to bug to commit some ports ?

On Mon, Jun 21, 2010 at 04:07:35PM +0200, Kurt Jaeger wrote: There is a newer of dbvis version available (7.1). Should I update my patch or how is this supposed to be handled ? That's the preferred way, yes. And for your other question, there are currently 1211 PRs in the queue, of which 98

Re: Unable to update/build security/gpa

On 06/20/10 09:30, Jason E. Hale wrote: On Sunday, June 20, 2010 06:55:52 you wrote: FreeBSD-PRERELEASE 8.1 amd64 Since the release of libassuan-2.0.0, I have not been able to update or reinstall security/GPA. All of the other ports appear to build fine. Jerry, I'm sorry to hear that you're

Re: lang/perl5.10 doesn't build with gcc 4.5.1

On 06/20/10 03:56, Ashish SHUKLA wrote: Try adding '-lssp_nonshared' to the LDFLAGS. Thanks for the suggestion, but that didn't help. What did help is the attached patch, which doesn't fix, but does avoid the problem with trying to find libssp. With that patch the resulting perl passed all

mail/thunderbird3 does not build with gcc 4.5.1

Howdy, On to the next victim. :) In my ongoing campaign to build my ports with gcc 4.5.1 thunderbird was the next to fall. Full log is at http://people.freebsd.org/~dougb/tbird.txt Doug -- ... and that's just a little bit of history repeating. --