From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Mar 2 00:33:29 2014 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C051986; Sun, 2 Mar 2014 00:33:29 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E8691198; Sun, 2 Mar 2014 00:33:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s220XSTm023891; Sun, 2 Mar 2014 00:33:28 GMT (envelope-from gerald@freefall.freebsd.org) Received: (from gerald@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s220XSKG023890; Sun, 2 Mar 2014 00:33:28 GMT (envelope-from gerald) Date: Sun, 2 Mar 2014 00:33:28 GMT Message-Id: <201403020033.s220XSKG023890@freefall.freebsd.org> To: freebsd-lists@potato.growveg.org, gerald@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org From: gerald@FreeBSD.org Subject: Re: ports/186480: astro/wmmoonclock fails to build X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 00:33:29 -0000 Synopsis: astro/wmmoonclock fails to build State-Changed-From-To: open->closed State-Changed-By: gerald State-Changed-When: Sun Mar 2 00:28:42 UTC 2014 State-Changed-Why: Thanks you for your report. It seems something went wrong with your download of the source for this port. I could not find any such problem reported by FreeBSD's regular builders nor reproduce this myself. Removing $PORTSDIR/distfiles/wmMoonClock*.tar.gz and starting the build again should fix this for you. If it does not, perhaps there is some web proxy/cache in between you and the download server? http://www.freebsd.org/cgi/query-pr.cgi?pr=186480