Re: Binary packages for releases and portupgrade
On Tue, Jan 5, 2010 at 11:45 PM, Doug Barton do...@freebsd.org wrote: Martin Cracauer wrote: Doug Barton wrote on Tue, Jan 05, 2010 at 01:58:57PM -0800: Are you saying there are binary packages for 8-stable? I thought I can only have them for -RELEASE? There have always been binary packages for the -stable branches. For example check out ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/. RELENG_8 will lift be out of binary ports, at least as far as portupgrade is concerned. Sorry, I don't understand that sentence. RELENG_8_0 will have emergency fixes AFAIK I'm sorry, that's not correct. RELENG_8_0 is a fixed point in time. The 8.0 -p1 security branch will be RELENG_8_1, etc. I do not agree on this one. RELENG_8_0 is the correct tag for following FreeBSD 8.0 with security fixes. RELENG_8_0_0_RELEASE on the other hand is fixed. RELENG_8_1 will be the branch for FreeBSD 8.1. -- chs, ___ 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
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 conflict with ports maintained by another person, please coordinate your efforts with them. Thanks, Erwin Annoying Reminder Guy III Lansing LATEST_LINK PORTNAME MAINTAINER == pear-Doctrinedatabases/pear-Doctrineglar...@freebsd.org pear-Doctrinedatabases/pear-Doctrine12 glar...@freebsd.org rsyslog sysutils/rsyslog4 cristianoro...@hotmail.com rsyslog sysutils/rsyslog5 cristianoro...@hotmail.com rsyslog-gnutls sysutils/rsyslog4-gnutls cristianoro...@hotmail.com rsyslog-gnutls sysutils/rsyslog5-gnutls cristianoro...@hotmail.com rsyslog-gssapi sysutils/rsyslog4-gssapi cristianoro...@hotmail.com rsyslog-gssapi sysutils/rsyslog5-gssapi cristianoro...@hotmail.com rsyslog-libdbi sysutils/rsyslog4-dbi cristianoro...@hotmail.com rsyslog-libdbi sysutils/rsyslog5-dbi cristianoro...@hotmail.com rsyslog-mysqlsysutils/rsyslog4-mysqlcristianoro...@hotmail.com rsyslog-mysqlsysutils/rsyslog5-mysqlcristianoro...@hotmail.com rsyslog-pgsqlsysutils/rsyslog4-pgsqlcristianoro...@hotmail.com rsyslog-pgsqlsysutils/rsyslog5-pgsqlcristianoro...@hotmail.com rsyslog-relp sysutils/rsyslog4-relp cristianoro...@hotmail.com rsyslog-relp sysutils/rsyslog5-relp cristianoro...@hotmail.com rsyslog-rfc3195 sysutils/rsyslog4-rfc3195 cristianoro...@hotmail.com rsyslog-rfc3195 sysutils/rsyslog5-rfc3195 cristianoro...@hotmail.com rsyslog-snmp sysutils/rsyslog4-snmp cristianoro...@hotmail.com rsyslog-snmp sysutils/rsyslog5-snmp cristianoro...@hotmail.com surf www/surf jig...@gmx.de surf math/surf po...@freebsd.org Total: 22 ports ___ 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
Re: port devel/gobject-introspection fails to build on sparc
On Tue, Jan 05, 2010 at 08:24:26PM -, Simon Griffiths wrote: Hello, -Original Message- From: owner-freebsd-spar...@freebsd.org [mailto:owner-freebsd- spar...@freebsd.org] On Behalf Of Anton Shterenlikht Sent: 18 December 2009 13:41 To: Andrew Belashov Cc: gn...@freebsd.org; freebsd-spar...@freebsd.org; freebsd- po...@freebsd.org Subject: Re: port devel/gobject-introspection fails to build on sparc On Fri, Dec 18, 2009 at 03:17:40PM +0300, Andrew Belashov wrote: ** ERROR:ginfo.c:337:g_base_info_get_name: code should not be reached gmake[3]: *** [foo-1.0.tgir] Abort trap: 6 (core dumped) gmake[3]: *** Deleting file `foo-1.0.tgir' gmake[3]: Leaving directory `/usr/ports/devel/gobject- introspection/work/gobject -introspection-0.6.6/tests/scanner' gmake[2]: *** [all-recursive] Error 1 -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 Did you find a way around this problem Anton? no, but I haven't tried too hard. I'm trying again right now and will report back. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
Re: Binary packages for releases and portupgrade
On Tue, 05 Jan 2010 14:45:05 -0800 Doug Barton do...@freebsd.org wrote: Martin Cracauer wrote: RELENG_8 will lift be out of binary ports, at least as far as portupgrade is concerned. Sorry, I don't understand that sentence. I would guess this should read will be left out of... Follows logically from his concern that there are no binary packages for -STABLE. --- Gary Jennejohn ___ 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
Re: Call for tester: VirtualBox 3.1.2 for FreeBSD (take 2)
On Mon, 2010-01-04 at 18:31 +0100, Beat Gaetzi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, First of all thanks a lot for all the valuable feedback. We have updated the ports Works without a problem here on FreeBSD 8.0-STABLE #0 r201431 i386 with Windows XP and Debian Lenny guests. Thank you very much for this work. -- Alexandre Kovalenko (Олександр Коваленко) ___ 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
Re: Binary packages for releases and portupgrade
Gary Jennejohn wrote on Wed, Jan 06, 2010 at 04:31:48PM +0100: On Tue, 05 Jan 2010 14:45:05 -0800 Doug Barton do...@freebsd.org wrote: Martin Cracauer wrote: RELENG_8 will lift be out of binary ports, at least as far as portupgrade is concerned. Sorry, I don't understand that sentence. I would guess this should read will be left out of... Follows logically from his concern that there are no binary packages for -STABLE. Right. I meant going -stable will lift me out of binary ports [support]. So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ 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
Re: Binary packages for releases and portupgrade
On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Greetings Uli. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ 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 | Peter Ulrich Kruppa | Wuppertal | Germany ___ 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
Re: Binary packages for releases and portupgrade
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Might be easier to just slam a Debian into a chroot. How do chroot and Linuxulator play together, anyway? Can I have a random-Linux in /compat/linux and then have a different one in /compat/linux/var/chroot/debian ? Alternatively I could just leave this poor notebook alone WRT building and run the same FreeBSD on one of my beefier machines to build binary packages and share the successes. Would probably involve two complete installations, one with a ports tree that only ever builds OO (and pulls in it's dependencies but nothing else). Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ 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
Re: Binary packages for releases and portupgrade
On Wed, 6 Jan 2010, Martin Cracauer wrote: Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Might be easier to just slam a Debian into a chroot. How do chroot and Linuxulator play together, anyway? Can I have a random-Linux in /compat/linux and then have a different one in /compat/linux/var/chroot/debian ? Alternatively I could just leave this poor notebook alone WRT building and run the same FreeBSD on one of my beefier machines to build binary packages and share the successes. Would probably involve two complete installations, one with a ports tree that only ever builds OO (and pulls in it's dependencies but nothing else). If you manage to install OOo in Linuxolator, please publish some kind of HOWTO... Today I started an experiment: I created a jail as a clean build enviroment for OOo. Yet it has installed 145 dependencies and not even started building OOo. Greetings Uli. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ | Peter Ulrich Kruppa | Wuppertal | Germany ___ 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
Re: Ports with duplicate LATEST_LINKS
Erwin Lansing wrote: 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 conflict with ports maintained by another person, please coordinate your efforts with them. I'll fix the rsyslog ports when I do o 2010/01/06 ports/142368 pgollucci [maintainer-update] - update sysutils/rsyslog5 to version 5.3.5 -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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
UIDs question
Hi,
I am new to building ports, however I have started to get the hang of
things.
I am not building any ports that I intend on submitting to FreeBSD, yet,
however maybe that isn't too far off :)
I've used a guide I found to create a local ports repository that is working
out wonderfully with the existing ports tree under /usr/ports
My tree is under /usr/ports/local, and I found a way to integrate a local
UIDs and GIDs file, by setting this variable in my Makefile:
UID_FILES:=${PORTSDIR}/local/UIDs
When I go to install my port it installs the user as expected, however it
fails on the ${INSTALL_PROGRAM} function. I understand this is just using
install with the appropriate flags. Obviously, the port doesn't install.
If I run it again, the user is already on the system, and the port installs
successfully.
I was wondering if there is a way to have the port install the user using
the native USERS or GROUPS directives in the do-install phase with the
INSTALL macros, or if there is a more suggested, or conventional, way of
doing this operation.
Thanks in advance!
Jason
___
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
Re: Binary packages for releases and portupgrade
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 09:43:21PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Might be easier to just slam a Debian into a chroot. How do chroot and Linuxulator play together, anyway? Can I have a random-Linux in /compat/linux and then have a different one in /compat/linux/var/chroot/debian ? Alternatively I could just leave this poor notebook alone WRT building and run the same FreeBSD on one of my beefier machines to build binary packages and share the successes. Would probably involve two complete installations, one with a ports tree that only ever builds OO (and pulls in it's dependencies but nothing else). If you manage to install OOo in Linuxolator, please publish some kind of HOWTO... If there is a serious question WRT it does run in the Linux emulator that would be easy enough to test, I can just NFS-mount one of my diskless Debians. Today I started an experiment: I created a jail as a clean build enviroment for OOo. Yet it has installed 145 dependencies and not even started building OOo. I expected nothing less. The Java requirement is particularly annoying on FreeBSD. And all that do get a Powerpoint clone with drunker mouse pointer syndrome written in tcl... Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ 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
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version of
Google's protocol buffers. Compiling protobuf from source is quite easy on
FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
___
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
Re: Binary packages for releases and portupgrade
On Wed, Jan 06, 2010 at 08:46:38PM +0100, Peter Ulrich Kruppa wrote: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. There are already some builds (english and german) at http://wiki.bsdforen.de/anwendungen/openoffice_aus_inoffiziellen_paketen They're updated on a unregularly basis. Cheers Lars pgp24RDPMrV4W.pgp Description: PGP signature
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 problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/audacious-crossfade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=audacious-crossfade portname: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: comms/asmodem broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=asmodem portname: comms/ltmdm broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=ltmdm portname: comms/yawmppp broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=yawmppp portname: databases/p5-sqlrelay broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20100103133538/p5-sqlrelay-0.41_2.log (_Dec_30_17:19:46_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=p5-sqlrelay portname: devel/ace+tao broken because: Does not compile on FreeBSD = 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ace%2Btao portname: devel/adabindx broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=adabindx portname: devel/agide broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=agide portname: devel/asis broken because: Does not build after gpl 2009 update to lang/gnat build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=asis portname: devel/callgrind broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview:
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 problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/audacious-crossfade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=audacious-crossfade portname: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/dino broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=dino portname: audio/ecamegapedal broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ecamegapedal portname: audio/ecawave broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ecawave portname: audio/emu10kx broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=emu10kx portname: audio/gmpc-mserver broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gmpc-mserver portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: biology/dotter broken because: checksum mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20091229173723/dotter-20021204.log.bz2 (_Nov_19_12:11:51_UTC_2009) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/dotter-20021204.log (_Aug_17_05:33:45_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: cad/alliance broken because: incomplete plist build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20100101212416/alliance-5.0.20090901_1.log.bz2 (_Dec_14_05:59:40_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: comms/asmodem broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=asmodem portname: comms/hcfmdm broken because: Does not compile at 7.x or higher build errors: none. overview:
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 the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/ccaudio description:C++ class framework for manipulating audio files maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 4 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/py-libmpdclient description:Python bindings for libmpdclient maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: chinese/gbk2uni description:TeX applet used to generate correct Chinese PDF bookmarks maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 6 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin description:IIIMF xcin language engine, a traditional Chinese input method maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: devel/adabindx description:An Ada-binding to the X Window System and *tif maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=adabindx portname: devel/agide description:A-A-P GUI IDE: a framework for software development maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 6 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=agide portname: devel/asis description:GNAT implementation of the Ada Semantic Interface Specification maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=asis portname: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: po...@freebsd.org status: BROKEN deprecated because: Included in devel/valgrind expiration date:2009-10-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind portname: devel/florist description:FSU implementation of POSIX.5, the POSIX Ada binding maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=florist portname: editors/xml2rfc-xxe description:An xml2rfc configuration for XMLMind XML Editor maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 4 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editorsportname=xml2rfc-xxe portname: graphics/gephex description:Software-based interactive video-effect system maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3
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 the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/ccaudio description:C++ class framework for manipulating audio files maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 4 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/dino description:A pattern-based MIDI sequencer maintainer: tr...@freebsd.org status: BROKEN deprecated because: has been broken for 7 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=dino portname: audio/py-libmpdclient description:Python bindings for libmpdclient maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: chinese/gbk2uni description:TeX applet used to generate correct Chinese PDF bookmarks maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 6 months expiration date:2010-01-08 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin description:IIIMF xcin language engine, a traditional Chinese input method maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: databases/mysql-connector-java50 description:MySQL Connector/J: JDBC interface for MySQL maintainer: m.sea...@infracaninophile.co.uk deprecated because: Old version: please use databases/mysql-connector-java instead expiration date:2010-02-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql-connector-java50 portname: databases/mysql60-client description:Multithreaded SQL database (client) maintainer: a...@freebsd.org deprecated because: The MySQL 6.0 development branch is deprecated and will be removed soon. Please consider using MySQL 5.5 instead. expiration date:2010-01-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql60-client portname: databases/mysql60-scripts description:Multithreaded SQL database (scripts) maintainer: a...@freebsd.org deprecated because: The MySQL 6.0 development branch is deprecated and will be removed soon. Please consider using MySQL 5.5 instead. expiration date:2010-01-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql60-scripts portname: databases/mysql60-server description:Multithreaded SQL database (server) maintainer: a...@freebsd.org deprecated because: The MySQL 6.0 development branch is deprecated and will be removed soon. Please consider using MySQL 5.5 instead. expiration date:2010-01-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql60-server portname: devel/adabindx description:An Ada-binding to the X Window System and *tif maintainer: po...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-08 build errors:
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, including errors seen on the build farm, is included below. portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=compat3x ___ 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
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, including errors seen on the build farm, is included below. portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=firefox ___ 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
