Date: Sun, 29 Jul 2001 02:05:22 +0100 From: Chris Elsworth <chris@shagged.org> To: fenner@FreeBSD.org Cc: ports@freebsd.org Subject: Re: Possibly unbuildable ports reminder Message-ID: <20010729020522.A67919@shagged.org> In-Reply-To: <200107281700.f6SH01h34901@freefall.freebsd.org>; from fenner@FreeBSD.org on Sat, Jul 28, 2001 at 10:00:01AM -0700 References: <200107281700.f6SH01h34901@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 28, 2001 at 10:00:01AM -0700, fenner@FreeBSD.org wrote: > In addition, the list of ports with no MAINTAINER with build problems is > > http://people.freebsd.org/~fenner/errorlogs/ports@freebsd.org.html > > Since no one is responsible for these ports, the problem won't get > fixed unless someone on this list takes the initiative. Guys, If I check any of these ports - how do I update the status of them if its not actually a problem with the port? For example, net/trafd ( http://bento.freebsd.org/errorlogs/4-latest/trafd-3.0.1.log ) appears to be a dodgy file on the ftp server in the log. I don't have any problems matching the checksum from a couple of UK FreeBSD mirrors. What should be done in this case? I'd be more than happy to work through a few of these ports if I knew what I was doing :) -- Chris Elsworth - Software & Systems Developer / Systems Administrator girls = time x money (and time is money) . chrise@demon.net = money^2 (money is root of all evil) . . tel: 020 8371 1041 = _/(evil^2) = evil t h u s mob: 07968 324 693 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010729020522.A67919>