jdk status in current

1.3: build fixed 1.4: build fixed 1.5: not fixed yet. 1.5 will take me a week or two. i386/hotspot is full of datatype assuptions that are wrong. I fixed them in 1.4 a long time ago, but never got around to it for 1.5. -Kurt

UPDATE: tor-0.1.0.16

Here is a quick update to tor. Changes in version 0.1.0.16 - 2006-01-02 o Crash bugfixes on 0.1.0.x: - On Windows, build with a libevent patch from "I-M Weasel" to avoid corrupting the heap, losing FDs, or crashing when we need to resize the fd_sets. (This affects the Win32 binar

Re: UPDATE: tor-0.1.0.16

Don't forget: PKGNAME=${DISTNAME}p0 -Ray-

Sviluppi e Nuove Proposte 2006

L'istituto ISI-CNV del dott Paret vi propone... >> C O N T E N U T O <<  - Notizia 1: Nuove tecniche basate    su nuovi principi di Neuro-Fascinazione  - inoltre: corsi di PNL, PNL3,    Ipnosi e Neuro-fascinazione  - Coaching e Carriera  

Re: UPDATE: tor-0.1.0.16

On Wed, 18 Jan 2006 10:15:48 -0600 Jon Trembley <[EMAIL PROTECTED]> wrote: > Here is a quick update to tor. could you please send a unified diff? (with -u that is) Cheers, Jasper pgpgoegibaiib.pgp Description: PGP signature

PATCH: fix sunsite.org.uk cpan path

This patch corrects the path for finding Perl modules on sunsite.org.uk. Questions? Jim Index: network.conf.template === RCS file: /cvs/ports/infrastructure/templates/network.conf.template,v retrieving revision 1.79 diff -u -r1.79 ne

Re: telephony/asterisk 1.0.9 => 1.2.1

1.2.2 was just announced; can you update the port for that please? Stuart Henderson wrote: This patch no longer applies to -current after naddy's updates for types.h (Jan 13). The attached patch, based on yours, fixes that and: - s/#else/else/ in Makefile patch to build with -O2 not -O2 -O6 -

PATCH v2 Fix two cpan mirror paths

The cpan mirror mirrors.dotsrc.org also has the wrong path. This patch fixes both sunsite.org.uk and mirrors.dotsrc.org cpan mirror paths. Jim Index: network.conf.template === RCS file: /cvs/ports/infrastructure/templates/network.co

Re: OpenAFS Port (please test)

Sorry I should have said. i386 for now only. I will fix the port to prevent it from trying on other platforms for now. Thanks. -Ober On Wed, 18 Jan 2006, [ISO-8859-1] Sigfred Håversen wrote: Date: Wed, 18 Jan 2006 18:45:16 +0100 From: "[ISO-8859-1] Sigfred Håversen" <[EMAIL PROTECTED]> To: ob

Re: Port: ctorrent

Aleksander Piotrowski wrote: > > What about net/rtorrent? This port does merely the same in terms of getting files via BitTorrent. And I agree with your attitude that it's unnecessary to have two ports in the tree that do the same job. But with the dnh2-version of ctorrent, clients can be manage

New port: ctorrent-dnh2

Hi, I compiled a new port of ctorrent with the dnh2 patches. An interesting feature of dnh2 is the possiblity of monitoring and controlling the clients via a control server: (http://www.rahul.net/dholmes/ctorrent/ctcs.html Please test it; I didn't have the possibility to test any other platform

Re: UPDATE: tor-0.1.0.16

* Jasper Lievisse Adriaanse [2006-01-18]: > > Here is a quick update to tor. > > could you please send a unified diff? (with -u that is) When we ask for unified diffs, then because there is a reason for it: it simplifies our work. This diff is so trivial that there is hardly any reason asking thi

ports/x11/fltk/

Hallo, This email attachment have updates for fltk. fltk.1.1.4 to fltk.1.1.7 is only suggestion... http://www.fltk.org/articles.php?L564 greet from Switzerland pascal *** Pascal Vizeli Bern (CH) *** www.openbsd.org www.free4net.ch www.dr

Re: UPDATE: tor-0.1.0.16

On Wed, 18 Jan 2006 23:09:29 +0100 Nikolay Sturm <[EMAIL PROTECTED]> wrote: > * Jasper Lievisse Adriaanse [2006-01-18]: > > > Here is a quick update to tor. > > > > could you please send a unified diff? (with -u that is) > > When we ask for unified diffs, then because there is a reason for it: i

Re: Problem w/ Python 2.3.5

Joachim Schipper ([EMAIL PROTECTED]) shaped the electrons to say: > > If it's memory, it's likely to be found by memtest86, if your hardware > is i386. It can be had from various sources, and is included on the > Knoppix CD, which I can recommend - it's not OpenBSD, but occasionally > very useful.

Problem with recent Ruby update and Rails/Lighttpd

Cheers, After updating to Ruby 1.8.4 on a 6-STABLE machine I'm getting this error with Lighttpd/Rails 1.0: /usr/local/lib/ruby/1.8/monitor.rb:218: [BUG] cross-thread violation on rb_thread_schedule() ruby 1.8.4 (2005-12-24) [i386-freebsd6] I get this sporadicly on the console that started

Re: Problem with recent Ruby update and Rails/Lighttpd

Ahh, this was ment for [EMAIL PROTECTED] Jonathan Weiss wrote: Cheers, After updating to Ruby 1.8.4 on a 6-STABLE machine I'm getting this error with Lighttpd/Rails 1.0: /usr/local/lib/ruby/1.8/monitor.rb:218: [BUG] cross-thread violation on rb_thread_schedule() ruby 1.8.4 (2005-12-24) [i

PATCH: Fix Packetstorm Mirrors

Patch to remove four defunct mirrors and add five new ones per the web site. Jim Index: network.conf.template === RCS file: /cvs/ports/infrastructure/templates/network.conf.template,v retrieving revision 1.81 diff -u -r1.81 network.co

OpenAFS Port (please test) (fwd)

I have updated the port to fix a few issues listed below. 1. Fix to prevent port from trying to compile on non i386 platforms. 2. Remove echoing the real password on the klog line. 3. Relocate test for /vicepa to earlier in the script to prevent wasted effort. 4. Fixed it so the script creates