[MacPorts] #28392: gnome-keyring not installing on account of missing schemas

[MacPorts]

#28392: gnome-keyring not installing on account of missing schemas
---------------------------------+------------------------------------------
 Reporter:  ben@…                |       Owner:  macports-tickets@…                   
     Type:  defect               |      Status:  new                                  
 Priority:  Normal               |   Milestone:                                       
Component:  ports                |     Version:  1.9.2                                
 Keywords:                       |        Port:  gnome-keyring                        
---------------------------------+------------------------------------------
 I'm trying to install ports with the ultimate aim of installing gnucash.
 However, when I get up to gnome-keyring, I get this complaint from
 macports:

 {{{
 :debug:activate Executing proc-post-org.macports.activate-activate-0
 :info:activate I/O warning : failed to load external entity
 "/opt/local/etc/gconf/schemas/*.schemas"
 :info:activate Failed to open `/opt/local/etc/gconf/schemas/*.schemas': No
 such file or directory
 :info:activate shell command "export GCONF_CONFIG_SOURCE=`gconftool-2
 --get-default-source` &&  gconftool-2 --makefile-install-rule
 /opt/local/etc/gconf/schemas/*.schemas" returned error 1
 :error:activate Target org.macports.activate returned: shell command
 failed (see log for details)
 :debug:activate Backtrace: shell command failed (see log for details)
     while executing
 "$post $targetname"
 :info:activate Warning: the following items did not execute (for gnome-
 keyring): org.macports.activate
 :notice:activate Log for gnome-keyring is at:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_gnome_gnome-keyring/main.log
 }}}

 Further investigation reveals that no /opt/local/etc/gconf/schemas
 directory even exists. Was it supposed to be created during gconf
 installation, or is gnome-keyring looking for something that's now
 inappropriate?

 The thread at http://www.mail-archive.com/macports-
 users at lists.macosforge.org/msg21779.html describes a similar problem with
 the package policykit-gnome. There, it was apparently remedied by changing
 the policykit-gnome port.

-- 
Ticket URL: <https://trac.macports.org/ticket/28392>
MacPorts <http://www.macports.org/>
Ports system for Mac OS