Bill Cole wrote:
Theory: it's a problem related to running the reclaim from the prompt at the
tail end of a selfupdate. Incomplete 'portindex' run perhaps?
Good theory. It's likely that when the periodic reclaim run at exit was
added, it wasn't considered that it might be running after code
On 2022-04-13 at 00:34:02 UTC-0400 (Tue, 12 Apr 2022 23:34:02 -0500)
Ryan Schmidt
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
On Tue, 12 Apr 2022, Ryan Schmidt wrote:
> > 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
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
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).
In fact, my schedule is:
Sunday: "port -u uninstall" to clean out
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
