Corrupted ports.tar file?

[Ryan Schmidt]

On Apr 10, 2022, at 16:31, Dave Horsfall wrote:

> Early MacBook Pro, High Sierra 10.13.6, MacPorts 2.7.2.
> 
> When doing my weekly MacPorts maintenance (doesn't everyone?), I saw this 
> during a "port reclaim" (automatically requested):
> 
>    Found no inactive ports.
>    --->  Building list of distfiles still in use
>    Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt.
>    Warning: Port bzip2 not found: 
>    Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt.
>    Warning: Port db48 not found: 
>    Warning: It looks like your PortIndex file for rsync://rsync.macports.org/macports/release/tarballs/ports.tar may be corrupt.
> 
> Etc; I do have "bzip2" and so on.
> 
> Haven't seen that before; what's going on?  A following "port upgrade 
> outdated" saw no problems...

Run "sudo port selfupdate" to get the most recent ports.tar. Do you still see the problem then?

This message could occur if you run "sudo port selfupdate" (or "sudo port sync") in one terminal window while another MacPorts process is still running in another terminal window. So it's best not to do that. If you weren't doing that, I can't explain it.