"Broken files found, but all associated ports are not in the index" error
ryandesign at macports.org
Thu Dec 16 23:08:50 UTC 2021
On Dec 16, 2021, at 02:55, Greg Earle wrote:
> On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this:
> [0:48] nightowl:/ % sudo port upgrade outdated
> Nothing to upgrade.
> ---> Scanning binaries for linking errors
> ---> Found 2 broken files, matching files to ports
> Warning: No port p5.26-net-ssleay found in the index; can't rebuild
> ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt.
> [0:49] nightowl:/ % port installed p5.26-net-ssleay
> The following ports are currently installed:
> p5.26-net-ssleay @1.900.0_0 (active)
> [0:50] nightowl:/ % port info p5.26-net-ssleay
> Error: Port p5.26-net-ssleay not found
> Tried to remove it but it didn't like that:
> [0:52] nightowl:/ % sudo port uninstall p5.26-net-ssleay
> Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents.
> The following ports will break:
> p5.26-io-socket-ssl @2.68.0_0
> p5.26-http-tiny @0.76.0_0
> p5.26-io-socket-ssl @2.69.0_0
> p5.26-io-socket-ssl @2.70.0_0
> p5.26-io-socket-ssl @2.71.0_0
> Continue? [y/N]: N
> ---> Cleaning p5.26-net-ssleay
> Is there anything I can do about it? I still have a ton of p5.26-* and p5.28-* ports installed, as well as p5.30-*.
> [0:54] nightowl:/ % sudo port installed | grep p5.26 | wc -l
I recommend uninstalling all p5.26 ports. Use p5.28 equivalents instead.
More information about the macports-users