From owner-freebsd-ports@FreeBSD.ORG  Mon Feb 14 19:56:30 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D783616A4CE
	for <ports@FreeBSD.org>; Mon, 14 Feb 2005 19:56:30 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6A62043D2D
	for <ports@FreeBSD.org>; Mon, 14 Feb 2005 19:56:30 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 4D606148F5; Mon, 14 Feb 2005 13:56:29 -0600 (CST)
Date: Mon, 14 Feb 2005 13:56:29 -0600 (CST)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20050214193022.GA29045@xor.obsecurity.org>
Message-ID: <Pine.LNX.4.44.0502141349570.23808-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: ports@FreeBSD.org
cc: Ceri Davies <ceri@submonkey.net>
Subject: Re: Unmaintained ports with fetch errors
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Feb 2005 19:56:31 -0000

On Mon, 14 Feb 2005, Kris Kennaway wrote:

> It's probably mostly overlapping, but it's not the source I'm using.
> I'll compile a list of ports and send them once the current build is
> finished.

You could always use
http://portsmon.firepipe.net/portsconcordanceforbuilderror.py?build_error=fetch&sortby=maintainer

which shows 431 ports.

This page is the union of all the summaries of all pointyhat runs, so
if some of the runs are stale, there will be false positives.  However,
each link to an errorlog uses the latest one across all the buildenvs,
so this is mitigated somewhat.

Of the 431 fetch errors, only about 150 seem to be for unmaintained ports.

Note: some of the errorlog links that portsmon reports have been broken
for a while.  portsmon uses the data from the pointyhat index pages and
those index pages sometimes seem to be out-of-date.  I have not had
enough time recently to try to go understand where the problem lies.

mcl