port -v rev-upgrade reports error for gimp.app

[istlota@…]

When attempting to port install gimp, i got this error:

---> Scanning binaries for linking errors: 28.1% Warning: Error parsing file /Applications/MacPorts/GIMP.app/Contents/MacOS/GIMP: Error opening or reading file 

I, then, attempted port -v rev-upgrade and got same error.

[larryv (Lawrence Velázquez)]

Thanks. You don’t have to Cc yourself if you reported the ticket.

It’s important to note that, as per your comment on #37792, you initially saw this error while trying to install vtk5, even though you did not have the gimp port installed.

[istlota@…]

Did a port -f clean --all all, then got this after a port -d -y rev-upgrade

[neverpanic (Clemens Lang)]

This is weird. Rev-upgrade gets its list of installed binaries from the registry. An entry for /Applications/MacPorts/GIMP.app/Contents/MacOS/GIMP can only find its way into the registry, if it was ever installed. So lets assume you had GIMP.app installed at some point and then deactivated or removed it.

Since rev-upgrade will only query active binaries from the registry database, it could only have seen this binary path, if the deactivation process was not run to completion and left the database in an inconsistent state (which transactions should have prevented, though).

You say port -f clean --all all fixed the problem, but this cannot be the command that caused the problem to no longer appear, because clean doesn't even touch the registry. Whatever it was, I have no idea how that could have happened. I'll have a look at the deactivation code, but I doubt we have any race conditions or wrong transactions in there. I guess I'll just close this as worksforme…

[neverpanic (Clemens Lang)]

Oh, port -f clean --all all didn't actually fix the problem. I missed the line in the output still showing the error.

Can you give me the output of port -v installed gimp-app?

[istlota@…]

Jiva:~ istlota$ port -v installed gimp-app The following ports are currently installed:

gimp-app @2.8.2_1 (active) platform='darwin 10' archs='x86_64'

Jiva:~ istlota$

Hhm ... archs='x86_64', but my Mac's kernel only does 32 bit.

[larryv (Lawrence Velázquez)]

Replying to istlota@…:

Hhm ... archs='x86_64', but my Mac's kernel only does 32 bit.

You have 64-bit hardware. OS X can build 64-bit binaries on x86_64, regardless of whether the kernel is 32-bit or 64-bit.

[neverpanic (Clemens Lang)]

So rev-upgrade trying to scan /Applications/MacPorts/GIMP.app/Contents/MacOS/GIMP is actually not a bug. You do have gimp-app installed and active, so the file should be there. Can you check whether the file exists and what permission bits it has: ls -lash /Applications/MacPorts/GIMP.app/Contents/MacOS/GIMP. Deactivating and re-activating the gimp-app port might also fix the issue:

sudo port -n -f deactivate gimp-app
sudo port activate gimp-app

[istlota@…]

'ls -lash /Applications/MacPorts/GIMP.app/Contents/MacOS/GIMP' returns nothing. Finder confirms there is no GIMP.app folder in /Applications/MacPorts. Spotlight returns no hits when I use it to search for GIMP.app.

When I stated that I do not have gimp installed, that was based upon my never having successfully performed a 'port install gimp' or a 'port install gimp-app', and the fact that 'port installed gimp' returns nothing. Nevertheless, 'port installed gimp-app' reports that gimp-app is installed. My assumption is that something else that I have explicitly port installed, in turn, implicitly installed gimp-app as a dependency.

Proceeding with that assumption, I performed a 'port uninstall gimp-app'. followed by a 'port clean gimp-app', then tried 'port -v rev-upgrade' again. The result was that the rev-upgrade msg about not being able to open GIMP went away, but was replaced by the a new msg:

Jiva:~ istlota$ port -v rev-upgrade

---> Scanning binaries for linking errors: 11.4%

Warning: Error parsing file /opt/local/libexec/dbus-daemon-launch-helper: Error opening or reading file

---> Scanning binaries for linking errors: 100.0%

---> No broken files found.

I, then, performed a 'port install gimp-app +universal' . It has taken eight hours, so far, but continues. The term session is not locked up because it does periodically report the status of yet another dependent port it installs. The last one was webkit-gtk. Obviously, I would remember if I had ever sat thru this insanely lengthy process before. It has me wondering if, maybe, gimp-app was installed as part of the lengthy process of initially install MacPorts from the downloaded DMG. That was the only time I have ever done anything with MacPorts that took this long.

[neverpanic (Clemens Lang)]

It seems the information in your registry database does not correspond to the files you actually have on disk. This will happen whenever you (or a script) removes files installed by MacPorts without using port uninstall to do this. I assume /opt/local/libexec/dbus-daemon-launch-helper does not exist either?

sudo port -n -f deactivate dbus
sudo port activate dbus

should fix this.

gimp-app certainly isn't pre-installed when you install MacPorts, so I have no idea where it comes from in your case.

[larryv (Lawrence Velázquez)]

Replying to istlota@…:

My assumption is that something else that I have explicitly port installed, in turn, implicitly installed gimp-app as a dependency.

The only port that has a dependency on gimp-app is gimp.

[istlota@…]

Rather than spend any more time trying to figure what got installed when, I completely uninstalled MacPorts, then reinstalled it from the tarball this time, rather than from the DMG installatiom image. After that, 'port -v rev-upgrade' completed with no inexplicable messages, no linking errors, and no broken files.