From owner-freebsd-ports@FreeBSD.ORG Sat Mar 16 21:11:15 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2935D6A8 for ; Sat, 16 Mar 2013 21:11:15 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id F35BC289 for ; Sat, 16 Mar 2013 21:11:14 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id 5225433C18; Sat, 16 Mar 2013 17:11:03 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 3432439829; Sat, 16 Mar 2013 17:11:00 -0400 (EDT) From: Lowell Gilbert To: freebsd-ports@freebsd.org Subject: Re: graphviz -- can't fetch References: <54657.1363392574@server1.tristatelogic.com> Date: Sat, 16 Mar 2013 17:11:00 -0400 In-Reply-To: <54657.1363392574@server1.tristatelogic.com> (Ronald F. Guilmette's message of "Fri, 15 Mar 2013 17:09:34 -0700") Message-ID: <44mwu3rqxn.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: "Ronald F. Guilmette" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 21:11:15 -0000 "Ronald F. Guilmette" writes: > Well, I just did try that and I am still getting the same result. In fact, > it appears to me that the entire web site of "www.graphviz.org" is most > seriously and entirely baroque.... I mean busted, kaput, blewie, snafued, > hosed in a major way. > > Please look for yourself. Well, I have, but I haven't seen the problem. > But anyway, meanwhile, back here on earth, forget about THAT for a > second... How come a copy of the dist file is *also* not available > (still) from ftp.FreeBSD.org ?? > > I'm filing a PR. This is really broke. I suspect that it's tied to the package building cluster problems. I'm not sure who to ask directly, so a PR is the right approach.