FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers 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 gcc3.4, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). 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. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. 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 4.x/5.x/6.x 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/festival+OGI broken because: Touches filesystem prior to make install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=festival%2BOGI portname: audio/spiralloops broken because: Does not compile (bad C++ code) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=spiralloops portname: biology/molden broken because: Size mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.2006072612/molden-4.4_1.log (Sep 5 03:36:28 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=molden portname: chinese/gbfs broken because: fails to patch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbfs portname: chinese/iiimf-le-chewing broken because: fails to install (dependency problem) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-chewing portname: chinese/xemacs broken because: Does not build even with fix for -lxpg4 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=xemacs portname: comms/pstngw broken because: Does not compile on FreeBSD >= 5.x build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.5.2006022503/pstngw-1.2.2_1.log (Mar 14 01:12:02 UTC 2006) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2006071303/pstngw-1.2.2_1.log (Sep 2 10:14:26 GMT 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=pstngw portname: databases/glom broken because: needs an update to 1.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=glom portname: databases/p5-GDBM broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.5.2006022503/p5-GDBM-1.00.log (Mar 15 01:21:42 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-GDBM portname: deskutils/offix-trash broken because: Does not compile (bad C++ code) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=offix-trash portname: deskutils/taskjuggler broken because: fails to install build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.5.2006022503/taskjuggler-2.2.0.log (Jun 7 15:41:21 UTC 2006) http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2006070603/taskjuggler-2.2.0.log (Jul 16 19:53:27 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=taskjuggler por
Ports freeze for 6.2 starts October 10
Hi, In preparation for the 6.2 release, the ports tree will be frozen from October 10. No commits will be allowed without explicit portmgr approval. We hope we can keep the freeze short and go into slush after one week. The tree will be completely unfrozen after the release is announced. For the full schedule, see the release schedule http://www.freebsd.org/releases/6.2R/schedule.html (updated after the next rebuild). As always, only commit that fix existing breakage will be allowed during the freeze and we encourage everyone will help fix as many ports as possible for this release. For more information about what kinds of commits are allowed during which period, please see the portmgr policies webpage at http://www.freebsd.org/portmgr/policies_committing.html On behalf of portmgr, -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_///[EMAIL PROTECTED] And it makes you cry.<) (>[EMAIL PROTECTED] pgpP6VHLg7QX2.pgp Description: PGP signature
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of 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 the port, including errors seen on the build farm, is included below. portname: games/gtetrinet forbidden because: Remote code execution: http://vuxml.FreeBSD.org/0b79743b-3ab7-11db-81e1-000e0c2e438a.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=gtetrinet portname: graphics/zgv forbidden because: http://vuxml.freebsd.org/a813a219-d2d4-11da-a672-000e0c2e438a.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=zgv 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=misc&portname=compat3x portname: multimedia/win32-codecs forbidden because: Remote code execution: http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=win32-codecs portname: www/awstats forbidden because: Command Injection Vulnerability build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=awstats portname: www/linux-beonex forbidden because: Security issues. From http://www.beonex.com/ 'The currently available Beonex Communicator 0.8 builds have several known security bugs' build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-beonex If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dependency problem with databases/gdl2
Dear Port Maintainer,
There seems to be a problem with the dependencies of the databases/gdl2
port:
happy-idiot-talk:...ports/databases/gdl2:% make -V BUILD_DEPENDS | perl -pe 's/
/\n/g'
/usr/local/lib/libcallback.a:/usr/ports/devel/ffcall
/usr/local/lib/gcc-4.1.2/libobjc.so:/usr/ports/lang/gcc41
/usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh:/usr/ports/devel/gnustep-make
/usr/local/GNUstep/System/Library/Libraries/libgnustep-base.so:/usr/ports/lang/gnustep-base
/usr/local/GNUstep/System/Library/Libraries/libGorm.so:/usr/ports/
<-**
gmake:/usr/ports/devel/gmake
The dependency on libGorm.so cannot point to '/usr/ports/' as the port to
intall to fulfill itself. I guess that's meant to say
/usr/ports/devel/gorm This patch looks to my untutored eye as if it might
provide the necessary fix:
happy-idiot-talk:...ports/databases/gdl2:% diff -u Makefile{.save,}
--- Makefile.save Sun Sep 17 10:38:33 2006
+++ MakefileSun Sep 17 10:38:52 2006
@@ -29,7 +29,7 @@
# USE_LDCONFIG=yes
INSTALL_SHLIBS=yes
MAKEFILE= GNUmakefile
-SLIDESHOWKIT_PORT?=devel/gorm
+GORM_PORT?=devel/gorm
USE_PGSQL= yes
.include
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
INDEX build failed for 4.x
INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: gdl2-0.10.1: no entry for /usr/ports make_index: gdl2-0.10.1: no entry for /usr/ports Committers on the hook: ale alexbl clsung dinoex marcus miwi nobutaka sem stefan thierry ume Most recent CVS update was: U databases/Makefile U databases/gdl2/Makefile U databases/gdl2/distinfo U databases/gdl2/pkg-descr U databases/gdl2/pkg-plist U devel/boehm-gc/Makefile U devel/mico/Makefile U devel/mico/files/patch-orb-ssl.cc U devel/rubygem-rtags/pkg-plist U emulators/Makefile U emulators/dtcyber/Makefile U emulators/dtcyber/distinfo U emulators/dtcyber/pkg-descr U emulators/dtcyber/files/patch-types.h U emulators/dtcyber/files/patch-window_x11.c U emulators/dtcyber/files/pkg-message.in U games/Makefile U games/stepbill/Makefile U games/stepbill/distinfo U games/stepbill/pkg-descr U games/stepbill/pkg-plist U graphics/inkscape/Makefile U graphics/inkscape/distinfo U graphics/inkscape/pkg-plist U mail/dbmail-devel/files/patch-dm_md5.c U net/dante/files/patch-configure U net/mpich2/Makefile U net/p5-Net-Analysis/Makefile U security/cryptlib/Makefile U security/cryptlib/distinfo U security/cyrus-sasl2/Makefile U security/cyrus-sasl2-saslauthd/Makefile U textproc/rubygem-ferret/Makefile U textproc/rubygem-ferret/distinfo U www/xpi-pdf_download/Makefile U www/xpi-pdf_download/distinfo U x11/e17-module-language/Makefile U x11/e17-module-language/pkg-plist U x11/e17-module-language/files/patch-configure ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: dkfilter-0.10_1
Dear Charles,
Thank you for reporting the problem.
On Sat, 16 Sep 2006 18:17:16 -0700
Charles Mujie <[EMAIL PROTECTED]> wrote:
> I have a question on dkfilter-0.10_1. I've managed to install the port
> successfully and everything is running fine. However when I enable
> dkfilter_out_enable="YES" in the /etc/rc.conf file it stops at line 52
> "logger -t ${name} `cat ${tmpfile}`". I have to do a control-D to
> continue the boot process. I was wandering if anyone has reported this
> problem before.
Unfortunately, no one has reported this problem.
However, I found that the same problem occured on my FreeBSD machine.
I found a work around to avoid this problem.
The work around is change the time in line 51 from 1 to 10 or something.
I suppose that some kind of racing condition occurs between daemon
command in line 48 and cat command in line 52.
I also found that the same problem occurs even in dkfilter_in.
This might also avoided with the work around above.
I also made a patch, which is attached to this email.
With the patch, dkfilter_out script will spin wait until a size of
a temporary file becomes larger than 0, instead of just wating 1
secound. This patch fixed the problem on my FreeBSD machine.
If the patch solves your problem, please let me know.
I will sendpr this.
Thank you,
Yoshisato YANAGISAWA.
--
---
Yoshisato YANAGISAWA <[EMAIL PROTECTED]>
Dept. of Mathematical and Computing Sciences,
Graduate School of Information Science and Engineering,
Tokyo Institute of Technology.
/* If you are an *BSD user, let's join http://bsdstats.org/ */
dkfilter.patch
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dependency problem with databases/gdl2
Matthew Seaman wrote:
> The dependency on libGorm.so cannot point to '/usr/ports/' as the port to
> intall to fulfill itself. I guess that's meant to say
> /usr/ports/devel/gorm This patch looks to my untutored eye as if it might
> provide the necessary fix:
>
> happy-idiot-talk:...ports/databases/gdl2:% diff -u Makefile{.save,}
> --- Makefile.save Sun Sep 17 10:38:33 2006
> +++ MakefileSun Sep 17 10:38:52 2006
> @@ -29,7 +29,7 @@
> # USE_LDCONFIG=yes
> INSTALL_SHLIBS=yes
> MAKEFILE= GNUmakefile
> -SLIDESHOWKIT_PORT?=devel/gorm
> +GORM_PORT?=devel/gorm
> USE_PGSQL= yes
>
> .include
>
Looks good. I'll commit it after checking the port build.
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX build failed for 4.x
INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: gdl2-0.10.1: no entry for /usr/ports make_index: gdl2-0.10.1: no entry for /usr/ports Committers on the hook: ale alexbl clsung dinoex linimon marcus miwi nobutaka rafan sem stefan thierry ume Most recent CVS update was: U LEGAL U databases/flamerobin/Makefile U databases/flamerobin/distinfo U www/urchin5/Makefile ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX now builds successfully on 4.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: dkfilter-0.10_1
Yanagisawa-san,
I did some more troubleshooting of my own last night I found out that by
increasing the sleep time to 5 secs or more the problem doesn't occur. I
agree with you analysis that there is some kind of race condition
between line 48 and 52.
Thanks for the patch you e-mail me. I've applied the patch and rebooted
a couple of times and it looks fine.
Thanks again.
/cm
Yoshisato YANAGISAWA wrote:
>Dear Charles,
>
>Thank you for reporting the problem.
>
>On Sat, 16 Sep 2006 18:17:16 -0700
>Charles Mujie <[EMAIL PROTECTED]> wrote:
>
>
>
>>I have a question on dkfilter-0.10_1. I've managed to install the port
>>successfully and everything is running fine. However when I enable
>>dkfilter_out_enable="YES" in the /etc/rc.conf file it stops at line 52
>>"logger -t ${name} `cat ${tmpfile}`". I have to do a control-D to
>>continue the boot process. I was wandering if anyone has reported this
>>problem before.
>>
>>
>
>Unfortunately, no one has reported this problem.
>However, I found that the same problem occured on my FreeBSD machine.
>
>I found a work around to avoid this problem.
>The work around is change the time in line 51 from 1 to 10 or something.
>I suppose that some kind of racing condition occurs between daemon
>command in line 48 and cat command in line 52.
>I also found that the same problem occurs even in dkfilter_in.
>This might also avoided with the work around above.
>
>I also made a patch, which is attached to this email.
>With the patch, dkfilter_out script will spin wait until a size of
>a temporary file becomes larger than 0, instead of just wating 1
>secound. This patch fixed the problem on my FreeBSD machine.
>If the patch solves your problem, please let me know.
>I will sendpr this.
>
>Thank you,
>Yoshisato YANAGISAWA.
>
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports freeze for 6.2 starts October 10
Erwin Lansing wrote: In preparation for the 6.2 release, the ports tree will be frozen from October 10. [...] Just wondering if there's a chance of seeing Gnome 2.16 committed before the freeze (I'm asking this since apparently it's already in the marcuscom repo). Not that I care much about Gnome (I'm using xfce after all), but I'm interested in the new GTK and Evolution versions. - Rainer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports freeze for 6.2 starts October 10
On Sun, Sep 17, 2006 at 08:45:56PM -0300, Rainer Alves wrote: > Erwin Lansing wrote: > >In preparation for the 6.2 release, the ports tree will be frozen from > >October 10. > >[...] > > Just wondering if there's a chance of seeing Gnome 2.16 committed before > the freeze (I'm asking this since apparently it's already in the > marcuscom repo). Not that I care much about Gnome (I'm using xfce after > all), but I'm interested in the new GTK and Evolution versions. I'd be interested to know about the GNOME team's plans for this, myself. Kris pgpHGCqBEoP9w.pgp Description: PGP signature
Re: Ports freeze for 6.2 starts October 10
On Sun, 17 Sep 2006 23:52:01 -0500, Kris Kennaway <[EMAIL PROTECTED]> wrote: On Sun, Sep 17, 2006 at 08:45:56PM -0300, Rainer Alves wrote: Erwin Lansing wrote: >In preparation for the 6.2 release, the ports tree will be frozen from >October 10. >[...] Just wondering if there's a chance of seeing Gnome 2.16 committed before the freeze (I'm asking this since apparently it's already in the marcuscom repo). Not that I care much about Gnome (I'm using xfce after all), but I'm interested in the new GTK and Evolution versions. I'd be interested to know about the GNOME team's plans for this, myself. http://www.freebsd.org/gnome/newsflash.html#event2006September17:0 good nite, (off to bed) Mezz Kris -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports freeze for 6.2 starts October 10
On Mon, Sep 18, 2006 at 12:32:18AM -0500, Jeremy Messenger wrote: > On Sun, 17 Sep 2006 23:52:01 -0500, Kris Kennaway <[EMAIL PROTECTED]> > wrote: > > >On Sun, Sep 17, 2006 at 08:45:56PM -0300, Rainer Alves wrote: > >>Erwin Lansing wrote: > >>>In preparation for the 6.2 release, the ports tree will be frozen from > >>>October 10. > >>>[...] > >> > >>Just wondering if there's a chance of seeing Gnome 2.16 committed before > >>the freeze (I'm asking this since apparently it's already in the > >>marcuscom repo). Not that I care much about Gnome (I'm using xfce after > >>all), but I'm interested in the new GTK and Evolution versions. > > > >I'd be interested to know about the GNOME team's plans for this, > >myself. > > http://www.freebsd.org/gnome/newsflash.html#event2006September17:0 Thanks. Kris pgpEbdZ5S0YzO.pgp Description: PGP signature
Re: Ports freeze for 6.2 starts October 10
On Mon, 2006-09-18 at 01:44 -0400, Kris Kennaway wrote: > On Mon, Sep 18, 2006 at 12:32:18AM -0500, Jeremy Messenger wrote: > > On Sun, 17 Sep 2006 23:52:01 -0500, Kris Kennaway <[EMAIL PROTECTED]> > > wrote: > > > > >On Sun, Sep 17, 2006 at 08:45:56PM -0300, Rainer Alves wrote: > > >>Erwin Lansing wrote: > > >>>In preparation for the 6.2 release, the ports tree will be frozen from > > >>>October 10. > > >>>[...] > > >> > > >>Just wondering if there's a chance of seeing Gnome 2.16 committed before > > >>the freeze (I'm asking this since apparently it's already in the > > >>marcuscom repo). Not that I care much about Gnome (I'm using xfce after > > >>all), but I'm interested in the new GTK and Evolution versions. > > > > > >I'd be interested to know about the GNOME team's plans for this, > > >myself. > > > > http://www.freebsd.org/gnome/newsflash.html#event2006September17:0 > > Thanks. I based this off of the SDL conversation. The GNOME 2.16 merge will be _much_ more involved since the PREFIX move will touch a lot of ports. We were thinking of a full pointyhat regression. I'm all for a pre-freeze commit if you think it's doable, but know that I will be traveling in the UK for two weeks starting on the 23rd, so at least I will be spotty when it comes to helping out with breakage. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
