Re: FreeBSD Port: sysutils/daemontools
> > any idea? > > > > also having problems with dns/djbdns and sysutils/ucspi-tcp with > > similar 'not found' messages I get that all the time, has something to get with however ports pulls files (not sure what ftp app it uses for this). If you get this in the future, just pull it manually via wget, fetch, or a browser and mv it to ports/distfiles. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update java for Firefox-3.6.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I know that this will not be a popular suggestion; however, rather than > spending time bumping version numbers in FreeBSD, perhaps the > developers could invest some time in making... a modern version of > Java. That would be because these are handled by two entirely different organizations. The FreeBDD core development group handles "bumping version numbers in FreeBSD" while the FreeBSD Foundation handles Java development .. instead of complaining how about you vote with your money and donate to the FBSD Foundation which allows monetary voting. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL+2jSAAoJEJh00PI1XILnpTsP/2Nf+0sNwyLlPM759wzYCt9p eMEdhEZfXhhzRFpKdkdaRZjaflrQEA4V1L8Y5iOfQzmVqvxOnQsRYsrSOHzK+Tc2 Qgq59OlwwErsv6jmkZZJQgdsAKFxgd652QiSbtPjWTsBA7GzTxw9PefdFF48/pt+ w8anN/+3VFaoEn05ttHJM/2NJv0P1BUosJuuCt6ZbxmLDv8HH58uOrUmn0/OjU2X dFalbI3fGr8EBO9EsFn1ZspXOlB7UIvnpdXJVZzmqvi9xfA9mA7kCCqm3O9j7nMy /W9GNIT2nIeUnLR/w+1BO3KWNYP0hamTaPKN6pOJP6wLgQizGN0ArvX/jgiR6JsF Zf6Okh/Y6mf2b/r0MWiL0M+8HX+nR3VO5jkxN7fhceSDiIvCAlaP3BXP6APl+jfK jSkrf+AW6+czMESMfogf8HVkc3Mw3wEJ+iWqcbOeYwLgPPS1TbFz2QF1YZ7fxNdN 0NHIsidieUOcuw7WIYK/AKOELC4/E5oBkzR+7/xJfoWlkDMwaemJkwni6L61HAvV +xBztfDvem3ZwFsc0NXc4cWnZlgdIHfz85Ut3SzGpr1o0T4r0tNjDjmWJCuijkHF xIgPrq99YdeEgsJMqozC7yKG5ErcGvFCVXfhMzT1+axlec/E2OEOGqY8DSeZ3/mR bxq3XMzQHfrb6khbNXy1 =FwpC -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: Diablo on 7.0-BETA
Hmmm .. let me try install COMPAT6X . Norberto: Can you try running an actual jar application and not just -version ... -version works fine for me also, its actually get a jar to run where it breaks. -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diablo on 7.0-BETA
I don't get an error to be honest. I maintain both games/ftjava and games/sfbol and when I run them they simply don't work. A window pops up for a second or so and then closes. If I add -verbose to the wrappers I see no errors either. They worked fine on 6.x though. I can troubleshoot them more but not sure how .. pointers? -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Error: Building texproc/p5-XML-Parser
So trying to track down this diablo problem and having something similar (at least in appearance) with xchat. Trying to rebuild everything (IRC suggestion) with portupgrade -rRf xchat to no avail as I can't seem to build p5-XML-Parser ... it seems to be the only port on my system that won't build. ssfbsd# uname -a FreeBSD ssfbsd.securestate.org 7.0-BETA2 FreeBSD 7.0-BETA2 #1: /usr/obj/usr/src/sys/SSFBSD amd64 NOTE: I have already did a portupgrade -rRf p5-XML-Parser and everything worked fine until it went to build the port itself. Below: ssfbsd# make ===> Extracting for p5-XML-Parser-2.34_2 => MD5 Checksum OK for XML-Parser-2.34.tar.gz. => SHA256 Checksum OK for XML-Parser-2.34.tar.gz. ===> p5-XML-Parser-2.34_2 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for p5-XML-Parser-2.34_2 ===> p5-XML-Parser-2.34_2 depends on file: /usr/local/bin/perl5.8.8 - found ===> p5-XML-Parser-2.34_2 depends on file: /usr/local/bin/perl5.8.8 - found ===> p5-XML-Parser-2.34_2 depends on shared library: expat.6 - found ===> Configuring for p5-XML-Parser-2.34_2 /libexec/ld-elf.so.1: /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Cwd/Cwd.so: Undefined symbol "Perl_Gthr_key_ptr" *** Error code 1 Stop in /usr/ports/textproc/p5-XML-Parser. Ideas? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kismet-200710.r1 fails to build - FreeBSD 6.2-RELEASE
I am pretty sure this builds fine on pointyhat and also builds fine on my amd64 6.2 FBSD box (and also on CURRENT). This was an issue awhile ago but was patched a year or two pack. Make sure you built base with libpcap and its current (I believe the exact patch was pushed upstream there) there was a recent closed PR about this ... I can dig up if you wish. -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: duration of the ports freeze
David Southwell wrote: > On Saturday 01 December 2007 Pav Lucistnik <[EMAIL PROTECTED]> answered part > of > the question: >> On Friday 30 November 2007 21:47:07 Jason C. Wells wrote: >>> Peter Jeremy wrote: On Fri, Nov 30, 2007 at 03:04:14PM -0600, Mark Linimon wrote: > On Fri, Nov 30, 2007 at 07:50:02AM -0800, Jason C. Wells wrote: >> It wouldn't surprise me if portmanager is hoping that KDE 4.0 will go >> prime time real soon. That's my big conspiracy theory. >> >> package builds out the door. The Razor, and past experience, would >> suggest that sweeping changes would delay all that significantly. > As a corollary, KDE4 will not hit the ports tree until after 7.0 and > 6.3 are released. > .> > We lucked out last time and got current updates of both gnome and kde. "It would be a pleasant surprise if portmgr were able to take KDE 4.0 to prime time real soon." Later, Jason ___ >>> I must say I am having difficulty understanding the policies applicable >>> during ports freeze. >>> >> What criteria are used to determine whether an update is allowed or barred >> during the freeze? > > Pav Lucistnik <[EMAIL PROTECTED]> answered part of the question with this > interjection: > >> David Southwell píše v so 01. 12. 2007 v 03:08 -0800: > >>> What criteria are used to determine whether an update is allowed or barred >>> during the freeze? > >> 1) Security update >> 2) Build fix on one of the release platforms >> 3) Major runtime fix >> > > This seems sensible unless: > a) The freeze is unduly long (I would suggest more than two weeks) > AND Actually IIRC when 5.0 and 6.0 first came out they had *unduly* long port freezes also, more so than the normal X.1, X.2, X.n release cycles. I think the issue is the large number of ports than simply break on a major release (gcc4.x is causing problems w/ 7.0 I believe) and then trying to create 7.0 specific patches or ween them from the release iso. As such, this takes time. >> I would hgowever like to ask, on the basis of what is being learned >> now,how could the length freezes be diminished on future occasions? When the port freeze first hits I believe they always release a URL to all the packages currently having build problems on the forthcoming release. If you want to cut down on the time of the freeze, try arbitrarily fixing some of them so the port managers don't have to. Not all ports have diligent maintainers and not all ports even have maintainers period. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maintaining of *-aspell ports
Nikola Lečić wrote: > Hello, > > All ~80 *-aspell ports have '[EMAIL PROTECTED]'. Does this > mean that someone should take maintainership? Yep ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Seg Fault: Xchat (on run)
Hello, Not which list to post this to so figured I would start here. The problem I have am is xchat segfaults on me right after I start it. Did not have the problem on 6.2 or 6.3 but doesn't seem to like 7.0-BETA4 ... anybody have any ideas? Cheers, -Peter ERROR: ssfbsd% gdb xchat GNU gdb 6.1.1 [FreeBSD] This GDB was configured as "amd64-marcel-freebsd"... (gdb) run xchat Starting program: /usr/local/bin/xchat xchat [New LWP 100266] [New Thread 0x804201120 (LWP 100266)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x804201120 (LWP 100266)] 0x000803cf5fd8 in amd64_set_fsbase () from /lib/libc.so.7 And this just hang here forever ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diablo on 7.0-BETA
Just an update got jdk16 working on 7.0-BETA4 by building it from scratch never had any luck though using the binary diablo build's for 6.2 on 7.0-BETA4 even w compat6x. Prob a compat issue but I happy with 1.6 ... now only if it wasn't so slow :( ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TrueCrypt
Well for a port I am not sure the license compatibility. ON a technical note, has anybody tried this yet? Just curious. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Morpheus in ports
Jeremy Messenger wrote: On Thu, 28 Feb 2008 14:19:00 -0600, Max Laier <[EMAIL PROTECTED]> wrote: Am Do, 28.02.2008, 20:27, schrieb Jeremy Messenger: On Thu, 28 Feb 2008 11:41:48 -0600, Wes <[EMAIL PROTECTED]> wrote: Just thought someone should know that the main web site link for Morpheus is pornographic. Fixed (http://www.winnicki.net/morpheus/), thanks for report. Well ... http://www.winnicki.net/morpheus/shots/shot1.jpg That isn't porn, which it's art. Compare between old and new link. ;-) Also porn or not, its irrelevant. Ports www pages point to the applications primary page as defined by the port owner. If you don't like it, don't use Morpheus (or any other useful port where you happen to disagree with whats on their site) Lets not start expecting port committers to vest and censor each and every port homepage ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: OPTIONS improvement
> > > > After pav@'s commit to bsd.port.mk, now you can test > WITH/WITHOUT > > > > freely with OPTIONS. I guess to ask the obvious question, as a low maintenance port maintainer (e.g don't follow all the latest and greatest nitty gritty details) exactly what does this do for me and why do I care (or want to adopt my ports to use this) .. I don't exactly find "now you can test WITH/WITHOUT freely with OPTIONS" self-evident. As a general comment, I think this is also sorely lacking in most "HEADS UP" port annoucements .. e.g. why do we care and what does it do for us in layman terms. -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports suggestion: curl-loader
Poul-Henning Kamp wrote: This seems like a worthy addition to ports, it's a load-generator for HTTP/HTTPS servers: http://sourceforge.net/projects/curl-loader Well then port it :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i2p from ports doesn't work
Will look at it later but try: ./runplain.sh intead of the rc file ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Diablo on 7.0-BETA
Anybody got Diablo working? If so, you do anything special (my jar's won't run). If not: 1) Anybody know when a Diablo support 7.0 is coming out? 2) Until then, can we mark Diablo as broken on 7.0 Thanks, -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diablo on 7.0-BETA
The Java JDK binary put out by the FBSD Foundation. While only 5.x and 6.x binaries are out, either they should work on 7.0 or it should be marked broken on 7.0 in the port tree (instead of letting me install it via ports). NOT the game ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Is portsmon.freebsd.org down?
Is portsmon down? Been trying to hit if for the last couple days. http://portsmon.freebsd.org/[EMAIL PROTECTED] -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Port Bloat
A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. -Peter Just some ideas (as I have ports I own that I no longer care about and would like to delete), -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: firefox 2.0
> Sorry, but the Firefox 2.0 release was too late to be included in > FreeBSD 6.2. Is it really that late? Firefox is something new uesrs look for / expect and it has a large enough view that we might want to think about including it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
