Date: Tue, 26 Apr 2016 11:16:14 -0700 From: Mark Millard <markmi@dsl-only.net> To: freebsd-ports@freebsd.org Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: RE: Weird portupgrade error on current amd64 [and powerpc64?] Message-ID: <CB1F148A-77DB-448C-8453-B65BAF0519DB@dsl-only.net>
next in thread | raw e-mail | index | archive | help
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: > =3D=3D=3D=3D> 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. =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CB1F148A-77DB-448C-8453-B65BAF0519DB>