Problem after upgrade to 2.10.5

Riccardo Mottola riccardo.mottola at libero.it
Fri Jan 31 11:58:28 UTC 2025


Hi!

Joshua Root wrote:
>
> There is a ticket for this here: <https://trac.macports.org/ticket/70674>
>
> The reporter says that forcing a selfupdate worked around the problem. 
> Unfortunately I have never been able to reproduce the issue, so it's 
> nigh impossible to debug.

interesting. First, good thing to know I'm not alone, I was up to the 
point of thinkging having a corrupted DB or even hardware issues.
It may explain why I got this issue back then somehow it "cured" tiself. 
I thought a reboot, but possibly it was a sync.

However, this time it is more stubborn.

I get the stupid error right while executing selfupdate. I issued it 
several times, I always got the error with the same ID as duplicate.
If issue outdated, instead, I get consistently another ID as duplicate
port outdated even shows a couple of ports before throwing that error.

Riccardo




More information about the macports-users mailing list