found 636083 3.2.3-1
thanks
Hi,
apparently the bug is still present in the latest version of gconf2. As
gconf-schemas is a debian-only python script, this can only be fixed by
the maintainers.
Let me add with this, that if you decide that instead of preserving the
whole environment and just changing HOME and GCONF_CONFIG_SOURCE (as
shown with the patch in the last mail) you just set some special
environment variables (as shown in the patch below), then please besides
LD_PRELOAD and LD_LIBRARY_PATH, put QEMU_LD_PREFIX on the list of to be
preserved variables as from qemu 1.0 onward it is used for handing a
linker prefix to qemu-user.
A possible patch that does this:
@@ -59,7 +59,10 @@
if schemas:
tmp_home=tempfile.mkdtemp(prefix='gconf-')
env={'HOME': tmp_home,
- 'GCONF_CONFIG_SOURCE': 'xml:readwrite:'+defaults_dest}
+ 'GCONF_CONFIG_SOURCE': 'xml:readwrite:'+defaults_dest,
+ 'QEMU_LD_PREFIX': os.environ.get('QEMU_LD_PREFIX', ''),
+ 'LD_PRELOAD': os.environ.get('LD_PRELOAD', ''),
+ 'LD_LIBRARY_PATH': os.environ.get('LD_LIBRARY_PATH', '')}
if options.register:
arg='--makefile-install-rule'
else:
On the other hand this could lead to others wanting more variables to be
included so the proper way would probably having a blacklist of
environment variables that should be handed to gconftool-2 instead of a
whitelist as shown in the patch above.
In all I dont really see why the environment is dropped at all for the
gconftool-2 spawnvpe call?
cheers, josch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
