Changes between Initial Version and Version 1 of Ticket #66031, comment 9


Ignore:
Timestamp:
Oct 21, 2022, 3:56:26 PM (2 years ago)
Author:
jculpon (Jamie Culpon)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #66031, comment 9

    initial v1  
    11I can confirm that I was also impacted by this on Monterey and Big Sur x86; it looked like the specific error I hit was:
     2ATTEMPT ONE (was having rsync issues due to connection, so wasn't surprised by a problem initially):
     3{{{
     4% sudo port selfupdate; && sudo port upgrade outdated;
     5Password:
     6--->  Updating MacPorts base sources using rsync
     7MacPorts base version 2.7.2 installed,
     8MacPorts base version 2.8.0 downloaded.
     9--->  Updating the ports tree
     10--->  MacPorts base is outdated, installing new version 2.8.0
     11Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
     12
     13Error: Couldn't change permissions of the MacPorts sources at /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base to root: child killed: kill signal
     14Please run `port -v selfupdate' for details.
     15Error: /opt/local/bin/port: port selfupdate failed: Couldn't change permissions of the MacPorts sources at /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base to root: child killed: kill signal
     16}}}
     17ATTEMPT 2 with -v
    218{{{
    319% sudo port -v selfupdate
    … …  
    5773}}}
    5874
    59 After rerunning self update another time the tree updated fine.
     75I can confirm that after that second self update ports is working fine.