From owner-freebsd-current@freebsd.org Sun May 15 11:06:02 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 ADDD3B3A8B9 for ; Sun, 15 May 2016 11:06:02 +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 4CFA21DDA for ; Sun, 15 May 2016 11:06:02 +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 u4FB5rqP099479 for ; Sun, 15 May 2016 20:05:53 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sun, 15 May 2016 20:05:52 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Weird portupgrade error on current amd64 [and powerpc64?] Message-Id: <20160515200552.b7708ae8c1b4891bcab1eb39@dec.sakura.ne.jp> In-Reply-To: <20160508225457.cdbc57709d14a91098463c01@dec.sakura.ne.jp> References: <86zis2js44.knu@iDaemons.org> <20160507213515.6455fed968a4ac584530dd43@dec.sakura.ne.jp> <20160508225457.cdbc57709d14a91098463c01@dec.sakura.ne.jp> 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: Sun, 15 May 2016 11:06:02 -0000 Remaining fix is introduced to head at r299238 (almost just after my previous post) and stable/10 is rolled back to 5.25 at r299236 for now. Moreover, 5.27 is introduced to head at r299736. This version is confirmed OK for me. So both head and stable/10 are OK now. Thanks, Xin! Regards. On Sun, 8 May 2016 22:54:57 +0900 Tomoaki AOKI wrote: > Broken pipe problem alone is fixed on head by r299234. (MFC after 3days) > *Confirmed on stable/10. As this is the first related update > after r298192(MFC'ed one), the effect should be the same. > > But another problem Akinori mentioned is not yet fixed. > *On upstream bugtracker, it's already fixed on upstream head, > but cannot be confirmed on upstream public (read only) github. > Doesn't seem to be sync'ed yet. > > > On Sat, 7 May 2016 21:35:15 +0900 > Tomoaki AOKI wrote: > > > Thanks for your investigation. > > I left comment about this on bugzilla > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209211 > > > > and related thread in The FreeBSD Forums. > > > > https://forums.freebsd.org/threads/55989/#post-319345 > > > > Regards. > > > > > > On Sat, 07 May 2016 15:32:11 +0900 > > "Akinori MUSHA" wrote: > > > > > This looks like a bug in file 5.26. I've just filed an issue on the > > > tracker of file(1): > > > > > > http://bugs.gw.com/view.php?id=543 > > > > > > File 5.26 turned out to have some other nasty bugs like the following, > > > so I'd recommend you avoid it. > > > > > > http://bugs.gw.com/view.php?id=540 > > > > > > Fortunately the port is still at 5.25, so you could replace > > > /usr/bin/file with the one from the port: > > > > > > pkg install file > > > ln -sf /usr/local/bin/file /usr/bin/ > > > > > > However, /usr/lib/libmagic.* cannot be safely replaced like this, so > > > you can only wait for the next update or have to manually revert > > > /usr/src/contrib/file/ and reinstall it from /usr/src/usr.bin/file/. > > > > > > On Mon, 02 May 2016 23:55:47 +0900, > > > junc...@dec.sakura.ne.jp (Tomoaki AOKI) wrote: > > > > > > > > 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...@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-curre...@freebsd.org" > > > > > > > > > > > > > > > > > -- > > > > Tomoaki AOKI junc...@dec.sakura.ne.jp > > > > _______________________________________________ > > > > freebsd...@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to "freebsd-curre...@freebsd.org" > > > > > > > > > > -- > > > Akinori MUSHA / https://akinori.org/ > > > > > > -- > > Tomoaki AOKI junchoon@dec.sakura.ne.jp > > _______________________________________________ > > 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 > _______________________________________________ > 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