When building Gnome packages you get a lot of warnings liks this:

Resolved address “xml:merged:/nix/store/nk8ind8bc38hhdyby3ly86xajmv41ymj-GConf-2.14.0/etc/gconf/gconf.xml.default
s” to a read-only configuration source at position 0
None of the resolved addresses are writable; saving configuration settings will not be possible
WARNING: failed to install schema /schemas/apps/panel/default_profiles/medium/general/panel_id_list localeC:
Unable to store a value at key /schemas/apps/panel/default_profiles/medium/general/panel_id_list, as the confi
guration server has no writable databases. There are some common causes of this problem: 1) your configuration pa
th file /nix/store/nk8ind8bc38hhdyby3ly86xajmv41ymj-GConf-2.14.0/etc/gconf/2/path doesnt contain any databases o
r wasnt found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so
NFS file locking doesnt work in your home directory or 4) your NFS client machine crashed and didnt properly n
otify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the
time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you h
ave stale locks, remove ~/.gconf*/lock. Perhaps the problem is that you attempted to use GConf from two machines
at once, and ORBit still has its default configuration that prevents remote CORBA connections - put “ORBIIOPIPv4
=1” in /etc/orbitrc. As always, check the user. syslog for details on problems gconfd encountered. There can onl
y be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual stor
age locations such as ~/.gconf

This is because the builder doesnt have write access in the GConf schema directory (which is a good thing). I think there is a configure flag to prevent schema registration.

Submitted on 13 September 2007 at 14:00