gnome-keyring: is still broken after rebuilding it more than 3 times

[sousedik]

[sousedik@bsmbp ~/bddc]$ sudo port -d -y rev-upgrade
DEBUG: Copying /Users/sousedik/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
--->  Scanning binaries for linking errors
Could not open /opt/local/lib/libpng14.14.dylib: Error opening or reading file (referenced from /opt/local/bin/gnome-keyring)
DEBUG: Marking /opt/local/bin/gnome-keyring as broken
DEBUG: Marking /opt/local/lib/libgcr.0.dylib as broken
DEBUG: Marking /opt/local/libexec/gnome-keyring-prompt as broken
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/bugpoint
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llc
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/lli
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ar
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-as
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-bcanalyzer
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-cov
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-diff
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dis
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dwarfdump
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-extract
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ld
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-link
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-mc
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-nm
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-objdump
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-prof
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ranlib
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-rtdyld
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-size
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/macho-dump
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/opt
DEBUG: skipping ppc in /opt/local/share/cmake-2.8/Modules/CPack.OSXScriptLauncher.in since this system can't run it anyway
DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/ld64/ld

--->  Found 3 broken file(s), matching files to ports
--->  Found 1 broken port(s), determining rebuild order
DEBUG: Broken: gnome-keyring
DEBUG: Processing port gnome-keyring @0:2.32.1_0  
DEBUG: Processing port libgnome-keyring @0:2.30.1_1  
--->  Rebuilding in order
     gnome-keyring @2.32.1 
DEBUG: epoch: in tree: 1 installed: 1
DEBUG: gnome-keyring 2.32.1_0 exists in the ports tree
DEBUG: gnome-keyring 2.30.3_6  is the latest installed
DEBUG: gnome-keyring 2.32.1_0  is active
DEBUG: Merging existing variants '' into variants
DEBUG: new fully merged portvariants: 
DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gnome-keyring
DEBUG: OS darwin/11.4.2 (Mac OS X 10.7) arch i386
DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
DEBUG: adding the default universal variant
DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf
DEBUG: Not following dependencies
Skipping deactivate gnome-keyring @2.32.1_0 (dry run)
Skipping activate gnome-keyring @2.32.1_0 (dry run)
DEBUG: Rebuilding port gnome-keyring finished with status 0
Warning: If this was no dry run, rev-upgrade would now run the checks again to find unresolved and newly created problems
[sousedik@bsmbp ~/bddc]$ 

[neverpanic (Clemens Lang)]

I wonder why gnome-keyring links against libpng. That's probably a result of overlinking and might disappear in MacPorts 2.2 on Mavericks. However, this also means that the problem might not be fixable by rebuilding gnome-keyring, but rather be caused by a dependency of gnome-keyring that still references an outdated libpng version in its .la files.

Can you please post the output of port installed libpng? When did you last run selfupdate and upgrade outdated?

It seems this is a valid claim made by rev-upgrade and the binary is genuinely broken. The point we should rather figure out is why rebuilding gnome-keyring doesn't produce a working binary. Please try: sudo port clean gnome-keyring; sudo port -k install --no-rev-upgrade gnome-keyring and attach the file indicated by port logfile gnome-keyring. (You might want to sudo port uninstall gnome-keyring afterwards, because your next install or update without --no-rev-upgrade would detect the broken gnome-keyring binary and attempt to rebuild it again.)

[zow@…]

gnome-keyring logfile

[zow@…]

Cannot speak to the original poster, but I just encountered this exact same problem, so I'll answer these questions:

Can you please post the output of port installed libpng?

The following ports are currently installed:
  libpng @1.2.44_0
  libpng @1.4.5_0
  libpng @1.4.7_0
  libpng @1.4.8_0
  libpng @1.4.9_0
  libpng @1.5.12_0
  libpng @1.5.12_0+universal
  libpng @1.5.16_0+universal
  libpng @1.5.17_0+universal (active)

When did you last run selfupdate and upgrade outdated?

Today. It was upgrade outdated where I encountered the broken port. Prior to today it has been months since the last time I selfupdate and upgrade outdated.

It seems this is a valid claim made by rev-upgrade and the binary is genuinely broken. The point we should rather figure out is why rebuilding gnome-keyring doesn't produce a working binary. Please try: sudo port clean gnome-keyring; sudo port -k install --no-rev-upgrade gnome-keyring and attach the file indicated by port logfile gnome-keyring.

Attached.

(You might want to sudo port uninstall gnome-keyring afterwards, because your next install or update without --no-rev-upgrade would detect the broken gnome-keyring binary and attempt to rebuild it again.)

Done. Also had to remove the latest libgnome-keyring. I am left with

$ port installed gnome-keyring libgnome-keyring
The following ports are currently installed:
  gnome-keyring @2.30.3_0
  gnome-keyring @2.30.3_1
  gnome-keyring @2.30.3_3
  gnome-keyring @2.30.3_5
  gnome-keyring @2.30.3_6
  libgnome-keyring @2.32.0_0 (active)

[neverpanic (Clemens Lang)]

You seem to have a lot of old ports laying around. While this is not necessarily a problem and it certainly isn't causing this problem, you could save some disk space by running sudo port uninstall inactive from time to time.

Unfortunately your main.log doesn't help, because it doesn't show the build of gnome-keyring. It seems it did not cause a build, because it merely activated an already-available gnome-keyring version. Can you uninstall the latest version and try again using the instructions above?

In your list of installed ports, I also miss the latest version of gnome-keyring. Your list only has versions starting with 2.30, the current version of the port however is 2.32.1.

[macports@…]

Thanks cal@…

This solved the issue on my mac.

Didn't knew about "unstall inactive"

[neverpanic (Clemens Lang)]

Glad you could fix it.