question on packaging and gconf failures

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello List,
today I packaged the newly released Gnucash 2.0.2, but it
failed this
time, whereas 2.0.1 worked just fine.

The following error caused the build (or better make
install) to stop:

> mkdir -p
/var/tmp/gnucash-compiler/etc/gconf/gconf.xml.defaults
> GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults
> /opt/gnome/bin/gconftool-2 --makefile-install-rule
> apps_gnucash_history.schemas
> Failed to load source
"xml::/etc/gconf/gconf.xml.defaults": Failed:
> Could not make directory
`/etc/gconf/gconf.xml.defaults': No such file
> or directory

After asking back on gnucash-devel, this issue could be
resolved by
adding the following line just before
"%__make install DESTDIR=%"

> export GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1

According to http://www.gnome
.org/projects/gconf/ (Section Application
developer information), this is known and they tell a
workaround there.

Is this the established way to workaround this or is there a
"suse way"
to do this?

Thanks,
Christian Rauch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFKj20ayhvFxrDZlkRApjmAJ9VwD/S5i58FFLSez2TUN8z1fe3VgCd
Ei8S
UeYuGMMXSlmk3zRkoA0dF34=
=bMbt
-----END PGP SIGNATURE-----
------------------------------------------------------------
---------
To unsubscribe, e-mail: opensuse-packaging+unsubscribeopensuse.org
For additional commands, e-mail: opensuse-packaging+helpopensuse.org

Rauch Christian wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello List,
> today I packaged the newly released Gnucash 2.0.2, but
it failed this
> time, whereas 2.0.1 worked just fine.
> 
> The following error caused the build (or better make
install) to stop:
> 
> > mkdir -p
/var/tmp/gnucash-compiler/etc/gconf/gconf.xml.defaults
> >
GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults
> > /opt/gnome/bin/gconftool-2 --makefile-install-rule
> > apps_gnucash_history.schemas
> > Failed to load source
"xml::/etc/gconf/gconf.xml.defaults": Failed:
> > Could not make directory
`/etc/gconf/gconf.xml.defaults': No such file
> > or directory
> 
> After asking back on gnucash-devel, this issue could be
resolved by
> adding the following line just before
> "%__make install DESTDIR=%"
> 
> > export GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1

Or better configure with --disable-schemas-install

> According to http://www.gnome
.org/projects/gconf/ (Section Application
> developer information), this is known and they tell a
workaround there.
> 
> Is this the established way to workaround this or is
there a "suse way"
> to do this?

Yes:

1)
Never install gconf database to build root. Use
--disable-schemas-install or
GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1.

2) Use %post

%post
export GCONF_CONFIG_SOURCE=`opt/gnome/bin/gconftool-2
--get-default-source`
opt/gnome/bin/gconftool-2 --makefile-install-rule
etc/opt/gnome/gconf/schemas/foo.schemas >/dev/null
(one line per each schemas file)

3) Don't use %postun. RPM cannot do it correctly:
http
://bugzilla.gnome.org/show_bug.cgi?id=306924

4) In file list, never use *.schemas
/etc/opt/gnome/gconf/schemas/foo.schemas
(one line per each schemas file)
It is cosmetic, but prevents upgrading with missing lines in
%post.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
------------------------------------------------------------
---------
SUSE LINUX, s. r. o.                          e-mail:
sbrabecsuse.cz
Lihovarská 1060/12                            tel: +420 284
028 966
190 00 Praha 9                                fax: +420 284
028 951
Czech Republic                                http://www.suse.cz/

------------------------------------------------------------
---------
To unsubscribe, e-mail: opensuse-packaging+unsubscribeopensuse.org
For additional commands, e-mail: opensuse-packaging+helpopensuse.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stanislav Brabec schrieb:
> Or better configure with --disable-schemas-install
> 
>> According to http://www.gnome
.org/projects/gconf/ (Section Application
>> developer information), this is known and they tell
a workaround there.
>>
>> Is this the established way to workaround this or
is there a "suse way"
>> to do this?
> 
> Yes:
> 
> 1)
> Never install gconf database to build root. Use
> --disable-schemas-install or
GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1.
> 
> 2) Use %post
> 
> %post
> export GCONF_CONFIG_SOURCE=`opt/gnome/bin/gconftool-2
--get-default-source`
> opt/gnome/bin/gconftool-2 --makefile-install-rule
etc/opt/gnome/gconf/schemas/foo.schemas >/dev/null
> (one line per each schemas file)
> 
> 3) Don't use %postun. RPM cannot do it correctly:
> http
://bugzilla.gnome.org/show_bug.cgi?id=306924
> 
> 4) In file list, never use *.schemas
> /etc/opt/gnome/gconf/schemas/foo.schemas
> (one line per each schemas file)
> It is cosmetic, but prevents upgrading with missing
lines in %post.
> 

Thanks a lot for this instructions, y2pmbuild is currently
running and
building i686 and x84_64 for 10.0, 10.1 is already finished!

Regards,
Rauch Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFKnzSayhvFxrDZlkRAgH3AJ9hSQD7pDfhi8/JJ0Bgoyokx04PJACd
F7Se
q1qRj/7zbFVmBPOITBHruKo=
=p5PS
-----END PGP SIGNATURE-----
------------------------------------------------------------
---------
To unsubscribe, e-mail: opensuse-packaging+unsubscribeopensuse.org
For additional commands, e-mail: opensuse-packaging+helpopensuse.org