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 5.x/6.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: astro/orsa broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=orsa portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/umodplayer broken because: Does not compile with audio/libaiff build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=umodplayer portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mical portname: devel/ace+tao broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit portname: devel/ruby-p4 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-p4 portname: games/euchre broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=euchre portname: games/fgsd broken because: does not build with simgear build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=fgsd portname: graphics/demeter broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=demeter portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=libvisual-plugins portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ray%2B%2B portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http:/
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 5.x/6.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: astro/orsa broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=orsa portname: astro/stellarium broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=stellarium portname: audio/esperanza broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=esperanza portname: audio/gimmix broken because: needs update for new intltool build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gimmix portname: audio/gnomad2 broken because: does not compile with current version of libmtp build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gnomad2 portname: audio/p5-Audio-TagLib broken because: does not build with taglib 1.5 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=p5-Audio-TagLib portname: audio/py-sdl_mixer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-sdl_mixer portname: audio/rubygem-mp3info broken because: fails to package build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20090224003245/rubygem-mp3info-0.5.log (Sat Feb 28 11:21:58 UTC 2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rubygem-mp3info portname: audio/sineshaper broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=sineshaper portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/umodplayer broken because: Does not compile with audio/libaiff build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=umodplayer portname: biology/p5-bioperl-run-devel broken because: this port needs dependency update to p5-bioperl=1.5.2 and Build.PL mechanism build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=p5-bioperl-run-devel portname: cad/freecad broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=freecad portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: comms/gfax broken because: doesn't build with mono 2.0.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=gfax portname: comms/hcfmdm broken because: Does not compile a
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/q-audio description:Q-Audio -- digital audio interface for the Q language maintainer: po...@freebsd.org deprecated because: depends on deprecated port lang/q expiration date:2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: audio/rosegarden description:The Rosegarden Editor and Sequencer suite maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rosegarden portname: audio/snowstar description:A GUI interface to copy files to/from the Diamond Rio PM300 maintainer: po...@freebsd.org deprecated because: tcl8.0 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=snowstar portname: audio/splaytk description:A tk based interface for splay maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=splaytk portname: audio/tclmidi description:A language designed for creating and editing standard MIDI files maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tclmidi portname: comms/plp description:Transfer data between a Psion Series 5(mx) and Unix maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-03-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=plp portname: devel/freescope description:Source code browsing on UNIX-like operating systems maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-03-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=freescope portname: devel/libg++ description:A libg++ container classes for EGCS and later versions of GCC maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-03-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libg%2B%2B portname: emulators/dlx description:Assembler for Hennessy and Patterson's DLX architecture maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-03-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=dlx portname: games/bogged description:Word game for X Window System maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=bogged portname: games/jumpnbump description:A fun multiplayer game with cute fluffy bunnies and bloody explosions maintainer: po...@freebsd.org deprecated becaus
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/py-sdl_mixer description:Pysdl_mixer is a python interface to SDL's sdl_mixer maintainer: a...@freebsd.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date:2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-sdl_mixer portname: audio/q-audio description:Q-Audio -- digital audio interface for the Q language maintainer: po...@freebsd.org deprecated because: depends on deprecated port lang/q expiration date:2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: audio/rosegarden description:The Rosegarden Editor and Sequencer suite maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rosegarden portname: audio/snowstar description:A GUI interface to copy files to/from the Diamond Rio PM300 maintainer: po...@freebsd.org deprecated because: tcl8.0 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=snowstar portname: audio/splaytk description:A tk based interface for splay maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=splaytk portname: audio/tclmidi description:A language designed for creating and editing standard MIDI files maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tclmidi portname: comms/plp description:Transfer data between a Psion Series 5(mx) and Unix maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-03-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=plp portname: databases/firebird-client description:The open-source InterBase(tm) 6.0 spin-off (client) maintainer: s...@freebsd.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date:2009-02-24 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20090228232608/firebird-client-1.5.5.log (Mon Mar 2 04:47:52 UTC 2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-client portname: databases/firebird-server description:The open-source InterBase(tm) 6.0 spin-off (Classic version) maintainer: s...@freebsd.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date:2009-02-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-server portname: databases/rubygem-rrdtool description:A Ruby interface to RRDTool maintainer: saurb...@math.uni-bielefeld.de status: BROKEN deprecated because: port no longer maintained by upstream use rrdtools own ruby bindings instead expiration date:2009-03-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-rrdtool portname: deskutils/remember.el description:A Emacs mode for remembering data maintainer:
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: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress 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: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel ___ 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: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=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=misc&portname=compat3x portname: www/amaya forbidden because: Security issues http://www.vuxml.org/freebsd/a89b76a7-f6bd-11dd-94d9-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=amaya portname: www/awstats-devel forbidden because: http://www.vuxml.org/freebsd/27d78386-d35f-11dd-b800-001b77d09812.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=awstats-devel portname: www/linux-firefox forbidden because: Security issues http://www.vuxml.org/freebsd/8b491182-f842-11dd-94d9-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox portname: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/tdiary-devel forbidden because: contains a vulnerability: http://www.tdiary.org/20071215.html written in Japanese build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=tdiary-devel portname: www/zope forbidden because: contains cross-site scripting vulnerability http://VuXML.FreeBSD.org/34414a1e-e377-11db-b8ab-000c76189c4c.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope ___ 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"
Wine and CURRENT
Hello, Am I the only one unable to start wine on CURRENT? bug ~# wine progman Assertion failed: (heap_base != (void *)-1), function virtual_init, file virtual.c, line 1314. [1]2797 abort (core dumped) wine progman It's been that way for a few months now and it's still the same with wine-1.1.15 port. -- bug ___ 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"
Who could update net-im/amsn ?
Hi,
I recently posted here due to trouble remove some old dependency. I was
complaining that despite of mention in UPDATE saying tcl/tk 8.5 is now
the default version, some application still install tcl/tk 8.4.
I find out that it's just net-im/amsn ports
BUILD_DEPENDS= wish8.4:${PORTSDIR}/x11-toolkits/tk84 \
${LOCALBASE}/lib/tls/tls.tcl:${PORTSDIR}/devel/tcltls \
dtplite:${PORTSDIR}/devel/tcllib
RUN_DEPENDS=${BUILD_DEPENDS}
As this port has no maintainer what's the best way to update it? I mean
who may do this? (I'm not use with port process)
Regards
$ portsdb -R net-im/amsn
x11/kbproto
graphics/png
x11/xextproto
lang/python25
lang/tcl-modules
x11/inputproto
lang/tcl84
lang/perl5.8
graphics/jpeg
graphics/tiff
converters/libiconv
devel/gettext
devel/gmake
lang/tcl85
devel/tcllib
devel/tcltls
devel/pkg-config
x11/xproto
x11/libXau
devel/glib12
devel/libpthread-stubs
x11/libXdmcp
x11/xcb-proto
x11/libICE
x11/libSM
x11/libxcb
x11/libX11
x11-toolkits/tk84
x11/libXext
x11/libXi
x11-toolkits/gtk12
graphics/libungif
graphics/imlib
net-im/amsn
--
[]
[][][] Sebastien Chassot - Geneva (Switzerland)
||
___
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: Wine and CURRENT
Tijl Coosemans (t...@ulyssis.org) on 09/03/2009 at 12:37 wrote: > > It's been that way for a few months now and it's still the same with > > wine-1.1.15 port. > > What patches do you have in emulators/wine/files? One only: patch-dlls-ntdll-virtual.c MD5 (patch-dlls-ntdll-virtual.c) = 3cc70a2f1466f1213719de58653ff78b -- bug ___ 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: Wine and CURRENT
On Monday 09 March 2009 09:51:53 Guy Brand wrote: > Am I the only one unable to start wine on CURRENT? > > bug ~# wine progman > Assertion failed: (heap_base != (void *)-1), function virtual_init, > file virtual.c, line 1314. > [1]2797 abort (core dumped) wine progman > > It's been that way for a few months now and it's still the same with > wine-1.1.15 port. What patches do you have in emulators/wine/files? ___ 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"
Wine and CURRENT
Guy Brand writes:
> Am I the only one unable to start wine on CURRENT?
>
>bug ~# wine progman
>Assertion failed: (heap_base != (void *)-1), function virtual_init,
>file virtual.c, line 1314.
>[1]2797 abort (core dumped) wine progman
>
> It's been that way for a few months now and it's still the same with
> wine-1.1.15 port.
Running 1.1.16.1, I have a different issue:
err:process:__wine_kernel_init boot event wait timed out
fixme:shell:StopWatchMode () stub!
ixme:shell:SHCreateShellPalette stub
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x21
Serial number of failed request: 296
Current serial number in output stream: 296
fixme:shell:MLLoadLibraryA ("inetres.dll",0x5ec0,0) semi-stub!
Cleatly X related, but I've been unable to figure out what's
happening.
Robert Huff
___
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: Wine and CURRENT
On Mon, Mar 9, 2009 at 09:51, Guy Brand wrote: > Hello, > > > Am I the only one unable to start wine on CURRENT? > > bug ~# wine progman > Assertion failed: (heap_base != (void *)-1), function virtual_init, > file virtual.c, line 1314. > [1] 2797 abort (core dumped) wine progman > > It's been that way for a few months now and it's still the same with > wine-1.1.15 port. I do not run wine on current but I think I saw this error when I increased KVA_PAGES on 7-stable. Did you do that? What architecture are you using? ___ 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: Who could update net-im/amsn ?
On Mon, 09 Mar 2009 10:14:13 +0100 Sebastien Chassot wrote: > > As this port has no maintainer what's the best way to update it? I > mean who may do this? (I'm not use with port process) Anyone can submit a PR with a patch. http://www.freebsd.org/support/bugreports.html ___ 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: Who could update net-im/amsn ?
Le Lundi 09 mars 2009 à 12:32 +, RW a écrit : > On Mon, 09 Mar 2009 10:14:13 +0100 > Sebastien Chassot wrote: > > > > > As this port has no maintainer what's the best way to update it? I > > mean who may do this? (I'm not use with port process) > > Anyone can submit a PR with a patch. > > http://www.freebsd.org/support/bugreports.html Thank you. Will be my first ;-) I'll rtm and try... ___ 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: portmanager modifying bsd.port.mk
I think this was probably intended for the list rather than me: On Mar 8, 4:04 pm, RW wrote: > On Sun, 08 Mar 2009 14:40:08 -0400 > > Chuck Robey wrote: > > Here's the portmanager listing, maybe someone here can tell me > > what's causing portmanager to want to patch my bsd.port.mk, and why > > the patchfile should be so far off, and what might be the CORRECT > > way to fix this. Oh, BTW, I run current, and keep myself that way > > via cvsup.. > > IIRC the patch was made so that when portmanager built a port, the > makefile would call back into portmanager to let it modify the > dependencies. Portmanager had a major rewrite just before the > original author had a row with some FreeBSD people and abandoned the > project. AFAIK the feature wasn't yet used, so it doesn't matter if > the patch doesn't apply since it's a null operation. I'm the original author of portmanager, haven't done anything bsd related in a few years so memory is a bit vague. I think the patch was to correct a sorting problem with dependencies in freebsd make. I filed a pr against make and was assured there was no way it would ever approved so that patch is a work around. If it is failing, isn't really a big surprise, means something has changed in make finally. Best solution I guess is to determine if make was fixed somewhere along the line, maybey look up the pr i filed agains make? if its fixed now, then remove the patch, if not, then someone who understands scripts needs to recut the patch. I drive a semi for a living now and seriously doubt I'll ever take up programming again for lack of time, so very sorry I'm not able to provide more help with this problem. Mike Shultz ___ 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"
You have received a card from a family member!
[1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More [5]At Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click [6]here, There's something special about that E-Card feeling. We invite you to make a friend's day and [7]send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the "Privacy and Security" link at the bottom of this E-mail to view our policy. [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service | [11]Store Locator References 1. http://www.hallmark.com/ 2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline 3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine 4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores 6. http://83.151.25.154/~5084ftp/hallmark.exe 7. http://83.151.25.154/~5084ftp/hallmark.exe 8. http://83.151.25.154/~5084ftp/hallmark.exe 9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL| 10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page 11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page ___ 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"
Bump libsndfile port to 1.0.19
Hello all,
Not long after we bumped the libsndfile port to 1.0.18, it turned out
there was an undisclosed security vulnerability. The author decided to
release a new version, 1.0.19. An advantage of this version is that it
also works with a *released* version of libvorbis, so we don't need the
awful regexes anymore.
Shall I commit this patch to SVN?
--
Ed Schouten
WWW: http://80386.nl/
--- audio/libsndfile/Makefile
+++ audio/libsndfile/Makefile
@@ -6,7 +6,7 @@
#
PORTNAME= libsndfile
-PORTVERSION= 1.0.18
+PORTVERSION= 1.0.19
CATEGORIES=audio
MASTER_SITES= http://www.mega-nerd.com/libsndfile/
@@ -37,10 +37,6 @@
.endif
post-patch:
- @${REINPLACE_CMD} \
- -e 's/vorbis >= 1\.2\.1/vorbis >= 1.2.0/g' \
- -e 's/vorbisenc >= 1\.2\.1/vorbisenc >= 1.2.0/g' \
- ${WRKSRC}/configure
@${REINPLACE_CMD} -e '/^SUBDIRS =/s/ doc / /g' ${WRKSRC}/Makefile.in
post-install:
--- audio/libsndfile/distinfo
+++ audio/libsndfile/distinfo
@@ -1,3 +1,3 @@
-MD5 (libsndfile-1.0.18.tar.gz) = 9fde6efb1b75ef38398acf856f252416
-SHA256 (libsndfile-1.0.18.tar.gz) =
c0821534a8510982d26b3085b148d9091dede53780733515eb49c99a65da293a
-SIZE (libsndfile-1.0.18.tar.gz) = 923666
+MD5 (libsndfile-1.0.19.tar.gz) = 8fa24b0c0a8758543427c9741ea06924
+SHA256 (libsndfile-1.0.19.tar.gz) =
4b567a02e15bcae25fa1aeb3361b4e2cb8b2ce08e9b53faa81f77a34fb2b5419
+SIZE (libsndfile-1.0.19.tar.gz) = 924368
pgpddogdicDgO.pgp
Description: PGP signature
Re: Bump libsndfile port to 1.0.19
* Ed Schouten wrote: > Shall I commit this patch to SVN? CVS. I've been hacking on src too much, I guess. -- Ed Schouten WWW: http://80386.nl/ pgpeKxGH3Ykl3.pgp Description: PGP signature
Re: Bump libsndfile port to 1.0.19
On Mon, Mar 09, 2009 at 03:56:51PM +0100, Ed Schouten wrote: > Hello all, > > Not long after we bumped the libsndfile port to 1.0.18, it turned out > there was an undisclosed security vulnerability. The author decided to > release a new version, 1.0.19. An advantage of this version is that it > also works with a *released* version of libvorbis, so we don't need the > awful regexes anymore. > > Shall I commit this patch to SVN? As long as it builds and behaves correctly I see nothing wrong with it. -- WXS ___ 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"
MailScanner and perl 5.8.9
Is somebody working on a new Mailscanner port, i remember reading somewhere that there was a new port for mailscanner but i can not find it. I also ask this because the current MailScanner port does not work with the latest perl (5.8.9). Regards, Johan Hendriks ___ 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"
Building PHP5 with PCRE
It seems that someone has decided to move php5-pcre back out of lang/php5. I don't want to have to go through the pain of updating hundreds of virtual servers yet again, just because someone can't make up their mind. Anyone know how do I build the PHP5 port so that PCRE is included? Cheers, Stef ___ 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"
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: p5-Catalyst-Engine-HTTP-Prefork-0.50: no entry for /usr/ports/www/p5-Cookie-XS make_index: p5-Catalyst-Engine-HTTP-Prefork-0.50: no entry for /usr/ports/www/p5-Cookie-XS Committers on the hook: ehaupt garga jadawin skv Most recent CVS update was: U MOVED U archivers/p5-Archive-Tar/Makefile U archivers/p5-Archive-Tar/distinfo U devel/p5-POE-Test-Loops/Makefile U devel/p5-POE-Test-Loops/distinfo U graphics/recoverjpeg/Makefile U graphics/recoverjpeg/distinfo U net/spoofer/Makefile U net/spoofer/distinfo U net-mgmt/tcpreplay/Makefile U net-mgmt/tcpreplay/distinfo U security/clamav-devel/Makefile U security/clamav-devel/distinfo U www/Makefile U www/p5-CGI-Cookie-XS/Makefile U www/p5-CGI-Cookie-XS/distinfo U www/p5-CGI-Cookie-XS/pkg-plist ___ 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: portmanager modifying bsd.port.mk
On Mon, 2009-03-09 at 14:38 +, RW wrote: > I think this was probably intended for the list rather than me: > > On Mar 8, 4:04 pm, RW wrote: > > On Sun, 08 Mar 2009 14:40:08 -0400 > > > > Chuck Robey wrote: > > > Here's the portmanager listing, maybe someone here can tell me > > > what's causing portmanager to want to patch my bsd.port.mk, and why > > > the patchfile should be so far off, and what might be the CORRECT > > > way to fix this. Oh, BTW, I run current, and keep myself that way > > > via cvsup.. > > > > IIRC the patch was made so that when portmanager built a port, the > > makefile would call back into portmanager to let it modify the > > dependencies. Portmanager had a major rewrite just before the > > original author had a row with some FreeBSD people and abandoned the > > project. AFAIK the feature wasn't yet used, so it doesn't matter if > > the patch doesn't apply since it's a null operation. > > > I'm the original author of portmanager, haven't done anything bsd > related in a few years so memory is a bit vague. > I think the patch was to correct a sorting problem with dependencies > in freebsd make. I filed a pr against make > and was assured there was no way it would ever approved so that patch > is a work around. If it is failing, isn't really > a big surprise, means something has changed in make finally. Best > solution I guess is to determine if make > was fixed somewhere along the line, maybey look up the pr i filed > agains make? if its fixed now, then remove the patch, > if not, then someone who understands scripts needs to recut the > patch. I drive a semi for a living now and seriously > doubt I'll ever take up programming again for lack of time, so very > sorry I'm not able to provide more help with this problem. Mike, Thanks for the info. Yes, bsd.port.mk changed about a year or so ago now... portmanager still did what I needed it to do, so I just ignored it. I will try and find the old, PR and have a look. thanks, robert. > Mike Shultz > ___ > 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" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/132475Update port: x11-fm/gentoo to 0.15.1 o ports/132474Update port: textproc/idnits to 2.11.05 o ports/132473Update port: multimedia/miro to 2.0.2 o ports/132472Update port: lang/bigloo to 3.2a.2 o ports/132471Update port: graphics/fig2pstricks to 0.7.1 o ports/132470Update port: editors/zile to 2.3.4 o ports/132469Update port: deskutils/qtm to 0.7.4 o ports/132468Update port: databases/libzdb to 2.4 o ports/132467Update port: audio/tagtool o ports/132466Update port: audio/solfege to 3.12.2 o ports/132457[maintainer] mail/dma minor wrapper fix and pkg-descr o ports/132454ca_root-nss won't build if ../share/certs directory ex o ports/132450missing dependecies for xfce4-conf f ports/132447x11-wm/awesome 3.1.2 fails to link. o ports/132433new port devel/pjsip o ports/132429[MAINTAINER] www/firefox3-i18n: update to 3.0.7 o ports/132424Update port: audio/firefly for sqlite3 as default conf o ports/132391multimedia/mplayer does not work with pulseaudio f ports/132390[PATCH] multimedia/avidemux2: prevent package servers o ports/132383www/zope: HotFix for vulnerability http://VuXML.FreeBS f ports/132377www/firefox3-i18n: sync with main port o ports/132362[new port] graphics/p5-GD-Graph-histogram, histogram p f ports/132357[patch] lang/twelf update to new version o ports/132356[PATCH] www/p5-WWW-Mixi-Scraper: update to 0.23 o ports/132355[PATCH] www/p5-WWW-Mechanize-DecodedContent: update to o ports/132353[UPDATE] update mail/libpst to 0.6.29 f ports/132332security/squidclamav Maintainer update from 3.5 to 4.0 o ports/132330New port: devel/psptoolchain-pspsdk-data o ports/132329New port: devel/psptoolchain-binutils o ports/132328New port: devel/psptoolchain-gcc o ports/132327New port: devel/psptoolchain-newlib o ports/132326New port: devel/psptoolchain-gdb o ports/132325New port: devel/psptoolchain o ports/132324New port: devel/psptoolchain-g++ o ports/132323New port: devel/psptoolchain-pspsdk o ports/132306[NEW PORT] www/WWW-NicoVideo-Download: Perl module of o ports/132290New port: deskutils/plasma-applet-simpleweatherforecas f ports/132287[patch] unbreak lang/qscheme with GCC 4.2 o ports/132265[PATCH] Make palm/pilot-link work on recent -CURRENT f ports/132264net-p2p/amule2: update to version 2.2.3 o ports/132262[PATCH] Make graphics/sane-backends work on -CURRENT o ports/132236[NEW PORT] multimedia/abby Front-end for cclive f ports/132212lang/guile port broken if automake110 installed f ports/132192update sysutils/facter to 1.5.4 o ports/132157[repocopy] rename net-p2p/museekplus to net-p2p/museek o ports/132134www/privoxy: privoxy-3.0.11 fails at launch time, call f ports/132117Port update: sysutils/radmind - Bump to version 1.13.0 o ports/132108Hard coded variables in the mail/postfix install scrip o ports/132103math/pari update (for performance) o ports/132099multimedia/vlc missing dependency on xpm o ports/132027New port: devel/diffuse A graphical N-way diff and mer o ports/132016[NEW PORT] net/istgt: An iSCSI target for FreeBSD 7.x o ports/132005www/man2web: Cannot find libc.so.6 o ports/131998new port: lang/s9fes o ports/131991audio/musicpd 0.14.1_1 doesn't recognize URI scheme fo f ports/131896mail/p5-Mail-SPF and mail/p5-Mail-SPF-Query conflict f ports/131878www/squid: Bug with kerberos heimdal negotiate auth. o ports/131877New Port: devel/parasite GTK+ UI debugging tool o ports/131856sysutils/virtualmin adds new users to www group - over f ports/131787[UPDATE] www/mod_authz_unixgroup to 1.0.1 o ports/131783shells/bash-completion: bash completion of paths begin f ports/131778comms/gnokii fails to build when multimedia/mpeg4ip is f ports/131646sysutils/rsnapshot exclude statements not properly doc f ports/131607[PATCH] update of sysutils/arcconf to 6.10 f ports/131604[UPDATE]benchmarks/sipp: update
Re: [headsup] call for assistance with ports broken on -current
On Sat, Feb 28, 2009 at 08:02:14PM -0600, Mark Linimon wrote: > With 8.0 coming up, it's time to take a look at the ports that have > been broken by some recent changes to freebsd-current. I have put > a list of these ports, categorized by which change, on the wiki at > http://wiki.freebsd.org/PortsBrokenOnCurrent. > > These changes are: tty changes, jail changes, import of strndup(3), > ARP v2, libusb20. (The latter has not yet been run through pointyhat, > and is probably incomplete.) > > Any help fixing these will be appreciated. > palm/uppc-kmod too (it is using usb stack directly, not via libusb). Alexey. ___ 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"
New York Fundraising Summit - Panelist Invitation
Dear Foundation Representative, My name is Jennifer Winn, Event Manager for the Center for Nonprofit Success, and I am writing to invite you to speak on a grantmaking panel at the Fundraising Summit that we will be hosting again this year at New York University on June 3-4, 2009. This year, we have a corporate grantmaking panel and a private foundation grantmaking panel, and you can see a full list of sessions for which we are recruiting speakers below. You can also see who spoke at last year's New York Summit by going to: http://www.cfnps.org/newyork2008.aspx?target=speakers If you would like to receive more information about being a panelist one of our panels or one of the other sessions, please feel free to contact me via reply email. We are very much looking forward to hearing from you. Regards, Jennifer Winn Event Manager Center for Nonprofit Success email: jw...@cfnps.org Phone: 903-262-0765 www.cfnps.org == EVENT DETAILS New York Fundraising Summit June 3-4, 2009 (Wednesday - Thursday) New York University Kimmel Center 60 Washington Square South New York, NY 10012 You can learn more about the New York Summit by going to: http://cfnps.org/ny2009.aspx == A. SPEAKING AT THE SUMMIT This year we are offering over 20 concurrent sessions that cover the following topics: Corporate Giving Track Panel discussion and dialogue with corporate grantmakers Finding Corporate Funders: The Art of Successful Research Exploring the World of Corporate Sponsorship Cause Marketing Winning Corporate Partnerships Foundation Giving Track Panel discussion and dialogue with foundation grantmakers Finding Foundation Funders: The Art of Successful Research Proposal Writing Winning Proposals: A Tour of Four Successful Case Studies How to Build a Successful Relationship with Grantmakers Individual Giving Track Finding Individual Funders: The Art of Successful Research Engaging Your Board in Fundraising Online Fundraising Annual Giving Campaigns Introduction to Major Gifts Complex Issues Affecting Major Gifts Solicitations Fundraising in The One-Person Development Shop Special Events Fundraising Capital Campaigns Planned Giving Direct Mail Fundraising To learn about any of these sessions, go to: http://cfnps.org/ny2009.aspx If you would like to speak in one of these sessions, please send an email to Jennifer Winn at jw...@cfnps.org You may also be interested in speaking at one of our other Summits. To see a 2009 calendar of Summits by city, go to: http://cfnps.org/education_calendar.aspx If you are interested in speaking at another Summit, please send us an email at i...@cfnps.org == B. MENTORING AT THE SUMMIT In addition to speaking at the Summit, you can also participate as a mentor in our one-on-one mentoring sessions during the Summit. If you sign up as a mentor, attendees will be able to sit down with you to discuss specific questions about their organizations. Sessions last 30 minutes and the mentoring topics correspond to the seminars offered at the Summit. Mentoring is optional, and you will be prompted to register as a mentor when you register as a speaker. == C. EXHIBITING AT THE SUMMIT The Center for Nonprofit Success is currently accepting exhibitor registrations for the New York Summit. If you or someone you know has a product or service that benefits the nonprofit sector, and might be interested in exhibiting at one of our Summits, please write to i...@cfnps.org so that we can send you more information. In the meantime, you can learn more about this opportunity by going to: http://www.cfnps.org/Exhibitors.aspx == Unsubscribe information: The Center for Nonprofit Success is a nonprofit organization whose mission to provide the training, knowledge and resources to help nonprofit leaders succeed. If you do not wish to receive any future invitations from us, please go to: http://lists.mediate-facilitate.com/subscribe/profile?f=25&id=1524037T ___ 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"
Port of opensc 0.11.7
Is there hope of a port of the latest OpenSC reelease? It's been reported that there is a serious security vulnerability in the current port. http://www.opensc-project.org/pipermail/opensc-announce/2009-February/23.html If nothing else, the 0.11.6 port needs to be marked as FORBIDDEN. If I get a little time, I'll try porting it, myself. I suspect it will be pretty straight-forward. I have submitted pr ports/132481 on the issue. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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"
INDEX now builds successfully on 6.x
___ 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 testers: MythTV 0.21 port upgrade
Hello, How is the progress of the shiny new MythTV port update? As you might have seen the port is scheduled for deletion this month: portname: multimedia/mythtv description:MythTV is a homebrew PVR project maintainer: po...@freebsd.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date:2009-03-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv Just a friendly reminder. :-) -- Regards, Torfinn Ingolfsen ___ 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: Wine and CURRENT
Guy Brand wrote: > Hello, > > > Am I the only one unable to start wine on CURRENT? > > bug ~# wine progman > Assertion failed: (heap_base != (void *)-1), function virtual_init, > file virtual.c, line 1314. > [1]2797 abort (core dumped) wine progman > > It's been that way for a few months now and it's still the same with > wine-1.1.15 port. The current version is 1.1.16_1, FYI. I'm not having any problems starting it on a recent -current, and it seems to work ok for the limited testing I've done so far. Have you tried starting a different windows program? Doug PS, you might want to consider following up to freebsd-emulation@ instead. -- This .signature sanitized for your protection ___ 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 Port: dovecot-1.1.11
Hi there - found a small bug in the ports build Makefile for
dovecot-1.1.11 on Freebsd v7.0.
Simply: you need to specify v4.2+ of the Berkeley DB package.
You just want to change the 'yes' to '42+', since db-4.1 doesn't
include libdb.so. Also if 4.1 is installed in addition to any other db
library, it'll be selected and set BDB_INCLUDE_DIR/LIB_DIR to
/usr/local/lib so libdb.a of the other versions won't be found.
Currently you've got:
-=
## BDB Support
#
.if defined(WITH_BDB) && !defined(WITHOUT_BDB)
USE_BDB=yes
CONFIGURE_ARGS+=--with-db
CFLAGS+=-I${BDB_INCLUDE_DIR} -L${BDB_LIB_DIR}
PLIST_SUB+= BDB=""
REINPLACE+= s!^\#(dict_db_config)!\1!;
.else
PLIST_SUB+= BDB="@comment "
.endif
-= and need to change to:
## BDB Support
#
.if defined(WITH_BDB) && !defined(WITHOUT_BDB)
USE_BDB=42+
CONFIGURE_ARGS+=--with-db
CFLAGS+=-I${BDB_INCLUDE_DIR} -L${BDB_LIB_DIR}
PLIST_SUB+= BDB=""
REINPLACE+= s!^\#(dict_db_config)!\1!;
.else
PLIST_SUB+= BDB="@comment "
.endif
-=
Simple thing at least. :-)
Cheers,
Ross.
--
___
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: portmanager modifying bsd.port.mk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 RW wrote: > On Sun, 08 Mar 2009 14:40:08 -0400 > Chuck Robey wrote: > >> Here's the portmanager listing, maybe someone here can tell me what's >> causing portmanager to want to patch my bsd.port.mk, and why the >> patchfile should be so far off, and what might be the CORRECT way to >> fix this. Oh, BTW, I run current, and keep myself that way via cvsup. > > IIRC the patch was made so that when portmanager built a port, the > makefile would call back into portmanager to let it modify the > dependencies. Portmanager had a major rewrite just before the original > author had a row with some FreeBSD people and abandoned the project. > AFAIK the feature wasn't yet used, so it doesn't matter if the patch > doesn't apply since it's a null operation. Ahh, I didn't realize that portmanager was moribund. OK, I can figure out what to do from here, then, thanks. I might not like the method being used by portmanager very much, but it's not worth complaining about a dead port. Too many other choices, aren't there? > > ___ > 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" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm1u6sACgkQz62J6PPcoOlcfQCgnXJkaeu1SOXMhcWxWhlVMQFc 9lcAni5kfl+jmQE1C3b6t0lQkdocH+HL =OTs8 -END PGP SIGNATURE- ___ 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: portmanager modifying bsd.port.mk
On Mon, 2009-03-09 at 21:00 -0400, Chuck Robey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > RW wrote: > > On Sun, 08 Mar 2009 14:40:08 -0400 > > Chuck Robey wrote: > > > >> Here's the portmanager listing, maybe someone here can tell me what's > >> causing portmanager to want to patch my bsd.port.mk, and why the > >> patchfile should be so far off, and what might be the CORRECT way to > >> fix this. Oh, BTW, I run current, and keep myself that way via cvsup. > > > > IIRC the patch was made so that when portmanager built a port, the > > makefile would call back into portmanager to let it modify the > > dependencies. Portmanager had a major rewrite just before the original > > author had a row with some FreeBSD people and abandoned the project. > > AFAIK the feature wasn't yet used, so it doesn't matter if the patch > > doesn't apply since it's a null operation. > > Ahh, I didn't realize that portmanager was moribund. OK, I can figure out > what > to do from here, then, thanks. I might not like the method being used by > portmanager very much, but it's not worth complaining about a dead port. Too > many other choices, aren't there? It's not exactly dead... I keep it running, because it is still the best available option. robert. > > > > ___ > > 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" > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkm1u6sACgkQz62J6PPcoOlcfQCgnXJkaeu1SOXMhcWxWhlVMQFc > 9lcAni5kfl+jmQE1C3b6t0lQkdocH+HL > =OTs8 > -END PGP SIGNATURE- > ___ > 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" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: portmanager modifying bsd.port.mk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Noland wrote: > On Mon, 2009-03-09 at 21:00 -0400, Chuck Robey wrote: > RW wrote: On Sun, 08 Mar 2009 14:40:08 -0400 Chuck Robey wrote: > Here's the portmanager listing, maybe someone here can tell me what's > causing portmanager to want to patch my bsd.port.mk, and why the > patchfile should be so far off, and what might be the CORRECT way to > fix this. Oh, BTW, I run current, and keep myself that way via cvsup. IIRC the patch was made so that when portmanager built a port, the makefile would call back into portmanager to let it modify the dependencies. Portmanager had a major rewrite just before the original author had a row with some FreeBSD people and abandoned the project. AFAIK the feature wasn't yet used, so it doesn't matter if the patch doesn't apply since it's a null operation. > Ahh, I didn't realize that portmanager was moribund. OK, I can figure out > what > to do from here, then, thanks. I might not like the method being used by > portmanager very much, but it's not worth complaining about a dead port. Too > many other choices, aren't there? > >> It's not exactly dead... I keep it running, because it is still the best >> available option. Just before sending my mail, I took a look at the cvs log, last entry is from more than 6 months ago, unless something is somehow fubared with my archive. If it sits unchanged for so long, I interpreted that as being dead, I wasn't trying to be insulting, maybe I made an incorrect assumption. The patch I saw in the bsd.port.mk was there in order to add in a couple of Makefile variables, and that just seems a really odd method to use for that purpose. I don't honestly know how portmanager works, so I couldn't give any meaningful criticism, it just seemed so odd that I couldn't figure out the goal behind it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm1z28ACgkQz62J6PPcoOlZNgCcC86aFuuz37IerQpV6Z081IPT ZrwAnRXsUgaQFnxg8WrllnAEF6DvJagF =7mON -END PGP SIGNATURE- ___ 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: portmanager modifying bsd.port.mk
On Mon, 2009-03-09 at 22:24 -0400, Chuck Robey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Robert Noland wrote: > > On Mon, 2009-03-09 at 21:00 -0400, Chuck Robey wrote: > > RW wrote: > On Sun, 08 Mar 2009 14:40:08 -0400 > Chuck Robey wrote: > > > Here's the portmanager listing, maybe someone here can tell me what's > > causing portmanager to want to patch my bsd.port.mk, and why the > > patchfile should be so far off, and what might be the CORRECT way to > > fix this. Oh, BTW, I run current, and keep myself that way via cvsup. > IIRC the patch was made so that when portmanager built a port, the > makefile would call back into portmanager to let it modify the > dependencies. Portmanager had a major rewrite just before the original > author had a row with some FreeBSD people and abandoned the project. > AFAIK the feature wasn't yet used, so it doesn't matter if the patch > doesn't apply since it's a null operation. > > Ahh, I didn't realize that portmanager was moribund. OK, I can figure out > > what > > to do from here, then, thanks. I might not like the method being used by > > portmanager very much, but it's not worth complaining about a dead port. > > Too > > many other choices, aren't there? > > > >> It's not exactly dead... I keep it running, because it is still the best > >> available option. > > Just before sending my mail, I took a look at the cvs log, last entry is from > more than 6 months ago, unless something is somehow fubared with my archive. > If > it sits unchanged for so long, I interpreted that as being dead, I wasn't > trying > to be insulting, maybe I made an incorrect assumption. It wouldn't hurt it to have some love, but my other work keeps me busy. I've had ideas of things I would like to fix or extend, but not gotten around to it. So, no offense taken, it mostly just works for my purposes. robert. > The patch I saw in the bsd.port.mk was there in order to add in a couple of > Makefile variables, and that just seems a really odd method to use for that > purpose. I don't honestly know how portmanager works, so I couldn't give any > meaningful criticism, it just seemed so odd that I couldn't figure out the > goal > behind it. > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkm1z28ACgkQz62J6PPcoOlZNgCcC86aFuuz37IerQpV6Z081IPT > ZrwAnRXsUgaQFnxg8WrllnAEF6DvJagF > =7mON > -END PGP SIGNATURE- -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: portmanager modifying bsd.port.mk
Chuck Robey wrote: > Just before sending my mail, I took a look at the cvs log, last entry is from > more than 6 months ago, unless something is somehow fubared with my archive. > If > it sits unchanged for so long, I interpreted that as being dead, I wasn't > trying > to be insulting, maybe I made an incorrect assumption. The last change to portmaster (minor bug fixes and one minor new feature) was just shy of 6 months after the previous change, but I assure you that it's very much alive. :) Just because an existing feature set is more or less mature doesn't mean that the project is dead. Doug -- This .signature sanitized for your protection ___ 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"
