Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 May 2016 18:47:50 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 209211] 11.0-CURRENT r298192 breaks portupgrade on amd64 and powerpc64 (and may be more); its MFC r298920 breaks on 10-STABLE
Message-ID:  <bug-209211-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209211

            Bug ID: 209211
           Summary: 11.0-CURRENT r298192 breaks portupgrade on amd64 and
                    powerpc64 (and may be more); its MFC r298920 breaks on
                    10-STABLE
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: markmi@dsl-only.net

In reply to list notices for amd64 I had written for powerpc64:

On 2016-Apr-26, at 11:16 AM, Mark Millard <markmi at dsl-only.net> 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:

=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



Now there is a reply to my note that identifies -r298192 (11.0-CURRENT) and
-r298920 (MFC to 10-STABLE) as the revision that breaks portupgrade. . .



On Mon May 2 15:44:19 UTC 2016 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.=20

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. :-<

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209211-8>