Corrupted ports.tar file?

Bill Cole macportsusers-20171215 at
Wed Apr 13 06:23:04 UTC 2022

On 2022-04-13 at 00:34:02 UTC-0400 (Tue, 12 Apr 2022 23:34:02 -0500)
Ryan Schmidt <ryandesign at>
is rumored to have said:

> On Apr 11, 2022, at 17:02, Dave Horsfall wrote:
>> On Mon, 11 Apr 2022, Ryan Schmidt wrote:
>>> Run "sudo port selfupdate" to get the most recent ports.tar. Do you
>>> still see the problem then?
>> I did run that first; apologies for not mentioning it (there were no
>> issues).
> I think you did mention it. I was suggesting you run it again, in case somehow the server files were in a weird state the last time you selfupdated. There was some intermittent network problem affecting the server that generates the ports.tar file a few days ago, and again today; although I thought our rsync updates happened pretty much atomically, maybe it was possible for a set of files to be published briefly that was not correct.

I just now (0600 UTC 2022-04-13) had a similar experience. Ran a selfupdate which suggested I do a reclaim at the end. I said 'y' and it did the leaf trim and the inactive purge, but while "Building list of distfiles still in use" it kicked out a lot of errors about a corrupted PortIndex as Dave reported.

I also got a handful of messages like these, interspersed with the others:

Warning: Failed to open port libpaper : can't read "portinfo(porturl)": no such element in array
Warning: Failed to open port p5.28-http-message : can't read "portinfo(porturl)": no such element in array

Running 'port info' for the supposedly "not found" ports gave the normal output.

Running 'port reclaim' again (without another update) did NOT trigger the flood of errors.

Theory: it's a problem related to running the reclaim from the prompt at the tail end of a selfupdate. Incomplete 'portindex' run perhaps?

Bill Cole
bill at or billcole at
(AKA @grumpybozo and many * addresses)
Not Currently Available For Hire

More information about the macports-users mailing list