#63545 closed defect (duplicate)
port selfupdate silently fails
Reported by: | lcvisser (Ludo Visser) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.6.4 |
Keywords: | Cc: | ||
Port: |
Description
I routinely run port selfupdate
as suggested by the application (twice a month or so). I noticed I'm still at 2.6.4, while 2.7.1 is available. It seems to silently fail:
% sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.6.4 installed, MacPorts base version 2.7.1 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.7.1 Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
Running again immediately after:
% sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.6.4 installed, MacPorts base version 2.7.1 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.7.1 Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
The last message of port -d selfupdate
shows:
Command failed: CC=/usr/bin/cc ./configure --prefix=/opt/local --with-install-user=root --with-install-group=wheel --with-directory-mode=0755 --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1 Exit code: 2
More complete output:
% sudo port -d selfupdate 2>&1 > selfupdate_log.txt Password: DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: system: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base.tar DEBUG: Rebuilding and reinstalling MacPorts if needed DEBUG: system: /usr/bin/rsync -rtzvl --delete-after --include=/ports.tar --include=/ports.tar.rmd160 --exclude=* rsync://rsync.macports.org/macports/release/tarballs/ /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: system: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports.tar DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/PortIndex_darwin_20_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/PortIndex_darwin_20_i386/PortIndex.rmd160 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: system: chmod -R a+r /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs DEBUG: Permissions OK DEBUG: system -W /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base: CC=/usr/bin/cc ./configure --prefix=/opt/local --with-install-user=root --with-install-group=wheel --with-directory-mode=0755 --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1
selfupdate_log.txt
is attached
I can download the installer for 2.7.1 and move forward, but selfupdate should report a failure.
Attachments (1)
Change History (4)
Changed 3 years ago by lcvisser (Ludo Visser)
Attachment: | selfupdate_log.txt added |
---|
comment:1 Changed 3 years ago by jmroot (Joshua Root)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Looks like the failure is probably because your command line tools are outdated. The lack of error message was #56549, so it will be fixed once you are updated to the current version.
comment:2 Changed 3 years ago by lcvisser (Ludo Visser)
How would I check that the CLT are outdated? I have them installed and there are no pending software updates:
% xcode-select --version xcode-select version 2384. % xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates %
comment:3 Changed 3 years ago by jmroot (Joshua Root)
Software Update often won't update the CLTs because of an Apple bug. See ProblemHotlist#reinstall-clt
Complete output of "port -d selfupdate"