From owner-freebsd-current@freebsd.org Mon May 2 15:44:19 2016 Return-Path: Delivered-To: freebsd-current@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 6E1D6B2ADC5 for ; Mon, 2 May 2016 15:44:19 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DF021CE4 for ; Mon, 2 May 2016 15:44:19 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (123-48-23-227.dz.commufa.jp [123.48.23.227]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id u42EtmUP003656 for ; Mon, 2 May 2016 23:55:48 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 2 May 2016 23:55:47 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Weird portupgrade error on current amd64 [and powerpc64?] Message-Id: <20160502235547.245f47a21361ba801763c4a4@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 15:44:19 -0000 Hi. Today I encountered this problem on stable/10 and could determine the problematic commit is r298920, "Update file to 5.26". This commit is MFC of r298192, and reverting it fixes the issue on head, too. What I did (for stable/10) is... 1) Running at r298836: No problem. 2) Update to r298920: Problem is reproduced! 3) Downgrade to previous commit (r298889): No problem. 3) was done by `zfs rollback` to r298836 state, `svnlite up r298889', and proceeded usual rebuilding procedure. Fortunately, there was only 3 commits between r298836 and r298920, and I got right one in first attempt. But unfortunately, fixing portupgrade[-devel] or file/libmagic beyonds my hand. :-< On Tue, 26 Apr 2016 11:16:14 -0700 Mark Millard wrote: > https://lists.freebsd.org/pipermail/freebsd-ports/2016-April/102983.html reported a "Broken pipe" problem with portupgrade on 11.0-CURRENT on amd64. > > FYI: I had the/a "Broken pipe" portupgrade problem on powerpc64 under 11.0-CURRENT -r298518 on 2016-Apr-23 updating from /usr/ports -r413230 to -r413919. If this might be the same I do not know. The relevant part of the script log is: > > > ====> Compressing man pages (compress-man) > > ---> Backing up the old version > > ---> Uninstalling the old version > > [Reading data from pkg(8) ... - 68 packages found - done] > > ---> Deinstalling 'perl5-5.22.1_7' > > [Reading data from pkg(8) ... - 68 packages found - done] > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > > ! perl5-5.22.1_7 (Broken pipe) > > ---> Skipping 'ports-mgmt/portlint' (portlint-2.16.8) because a requisite package 'perl5-5.22.1_7' (lang/perl5.22) failed (specify -k to force) > > ruby was still lang/ruby21 at the time. > > I used portmaster instead and everything worked fine. > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI junchoon@dec.sakura.ne.jp