From owner-freebsd-ports@freebsd.org Wed Dec 28 03:58:00 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E644DC90020 for ; Wed, 28 Dec 2016 03:58:00 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id CB8881FFE for ; Wed, 28 Dec 2016 03:58:00 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vvelox.net (localhost [127.0.0.1]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id E1C0C3791154 for ; Tue, 27 Dec 2016 21:56:45 -0600 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 27 Dec 2016 21:56:45 -0600 From: "Zane C. B-H." To: freebsd-ports@freebsd.org Subject: Re: what broke? In-Reply-To: <20161227123114.2041f886@vixen42.vulpes.vvelox.net> References: <20161227082854.1d0f3a27@vixen42.vulpes.vvelox.net> <20161227123114.2041f886@vixen42.vulpes.vvelox.net> Message-ID: <2c49715f8e5c9edeccc6909c9225c1fe@vvelox.net> X-Sender: v.velox@vvelox.net User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2016 03:58:01 -0000 On 2016-12-27 12:31, Zane C. B-H. wrote: > On Tue, 27 Dec 2016 08:28:54 -0600 > "Zane C. B-H." wrote: > >> Just did an svn update and I am seeing synth, portupgrade, and >> portupgrade-devel give me errors like this. >> >> Scan >> of /arc/src/FreeBSD/ports/head/multimedia/gstreamer1-plugins-core >> failed (port deleted), it will not be considered. >> >> The directories I've checked and very much are there. >> >> ftp/curl is one that will throw that for me as well. Rebuilding that >> port manually and reinstalling got the error to go away. >> >> Does not appear to happen with all, just some. > > Been testing with rebuilding some more and rebuilding and > reinstalling any of those ports via hand works. The problem does not > come back after that. I've been unable to figure out what the root > cause of this is. Been disecting this some more and it appears anything broken was installed with the wrong origin. Basically it used the full path, so ftp/curl would become /usr/ports/ftp/curl. Which in turn meant portupgrade and the like looking for /usr/ports/usr/ports/ftp/curl.