Opened 14 years ago
Closed 14 years ago
#28392 closed defect (fixed)
gnome-keyring not installing on account of missing schemas
Reported by: | ben@… | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | rmstonecipher@… | |
Port: | gnome-keyring |
Description
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@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.
Attachments (1)
Change History (5)
comment:1 Changed 14 years ago by jmroot (Joshua Root)
Cc: | rmstonecipher@… added; devans@… removed |
---|---|
Owner: | changed from macports-tickets@… to devans@… |
Changed 14 years ago by ben@…
Attachment: | Portfile-gnome-keyring.txt added |
---|
comment:2 Changed 14 years ago by ben@…
comment:4 Changed 14 years ago by dbevans (David B. Evans)
Resolution: | → fixed |
---|---|
Status: | new → closed |
This was caused by the premature upgrade of gnome-keyring to version 2.32. This version uses GSettings from GIO for preference settings instead of GConf. So the post-activate phase where the old GConf schemas were installed is unnecessary and fails in the case where *NO* port that installs GConf schemas has previously been installed.
At the same time, the GSettings functionality is currently broken on Darwin as they do not yet support launchd as a way of managing the dbus session bus. Once this is resolved then, upgrading all of the GNOME related ports to 2.32 (and beyond) will be relatively straight forward and should be done at the same time due to their inter-dependencies.
This being the case, please don't upgrade any of the GNOME ports to 2.32 unless you are sure you understand all the consequences and that they have been tested and are fully functional within the current GNOME environment.
For now, I am reverting this port back to the 2.30.3 version. This should resolve your problem.
Reversion committed in r77986.
Please sync your ports tree, clean the port and upgrade.
I've just attached a patched Portfile, which I made by adapting the solution posted in r72660 (referenced in the email thread I linked to).