Unable to clean kcachegrind

[istlota@…]

Attempts to 'sudo port clean --all all' fail when it gets to kcachegrind with this error:

Error: Unable to open port: couldn't change working directory to "/Volumes/macintoshUSB/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/kde/kcachegrind": no such file or directory

This same command completed when I ran it a day or two ago.

[mf2k (Frank Schima)]

In the future, please use WikiFormatting.

Something is strange:

$ port info kcachegrind
Error: Unable to open port: couldn't change working directory to "/opt/mports/trunk/dports/kde/kcachegrind": no such file or directory

[NicosPavlov]

The port has been renamed due to a conflict with another port. Rebuilding the index with

sudo port selfupdate

should solve the issue, eventually along with

sudo port uninstall kcachegrind
sudo port install kcachegrind4

to replace the port.

[jamesfmarshall@…]

sudo port selfupdate does not solve the issue here, not even with the sudo port uninstall command.

Can we fix this manually?

[istlota@…]

I concur with jamesfmarshall. Even after I issued the suggested cmds [sudo port selfupdate, sudo port uninstall kcachegrind, sudo port install kcachegrind4], sudo port clean --all all still fails at the same spot.

[amadeus24]

The easiest way would be to create a link "kcachegrind" to "kcachegrind4".
"port clean all" should then do the job.
It's true we have then a system-cadaver, but it's just a link, which can be removed later.

[NicosPavlov]

The fact of making a symlink may not be sufficient, as any manual addition to the ports source would be suppressed when running selfupdate again, unless it is placed in a local port repository. Furthermore, this link may hide the other existing port devel/kcachegrind, which is the original reason for suppressing kde/kcachegrind.

One way which seemed to work for me is to manually force the full creation of a port index with:

cd ${prefix}/var/macports/sources/rsync.macports.org/release/tarballs/ports
sudo portindex -f

where ${prefix} is the Macports installation (usually /opt/local). This way is also maintained through selfupdates.

[amadeus24]

Replying to nicos@…:

The fact of making a symlink may not be sufficient, as any manual addition to the ports source would be suppressed when running selfupdate again, unless it is placed in a local port repository. Furthermore, this link may hide the other existing port devel/kcachegrind, which is the original reason for suppressing kde/kcachegrind.

One way which seemed to work for me is to manually force the full creation of a port index with:

cd ${prefix}/var/macports/sources/rsync.macports.org/release/tarballs/ports
sudo portindex -f

where ${prefix} is the Macports installation (usually /opt/local). This way is also maintained through selfupdates.

Agree with you. I create the link just to prevent "clean" to stumble and deleted the link after "clean" have finished the job. Even not emptying everything the function will go through all ports and will not stop.
Anyway, I will recommend your steps also.

[NicosPavlov]

This issue should be fixed, as the older port kcachegrind has been erased from the ports list after having been obsolete for some time.