Your message dated Sun, 19 Aug 2012 00:11:55 +0200
with message-id <20120818221153.ga20...@ugent.be>
and subject line Re: gdm3: FTBFS ("`+' is an invalid character in a
configuration, storage address")
has caused the Debian Bug report #665708,
regarding gdm3: FTBFS ("`+' is an invalid character in a configuration storage
address")
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
665708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdm3
Version: 3.0.4-4
Severity: serious
Hi,
gdm3 FTBFS (when rebuilt against a newer CDBS to pick up hardening
flags); from the amd64 build log:
gconftool-2 --direct
--config-source=xml:merged:/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/debian/gdm3//var/lib/gdm3/.gconf.mandatory
--recursive-unset /
(gconftool-2:13143): GConf-WARNING **: Failed to load source
"xml:merged:/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/debian/gdm3//var/lib/gdm3/.gconf.mandatory":
Couldn't resolve address for configuration source: Bad address
`xml:merged:/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/debian/gdm3//var/lib/gdm3/.gconf.mandatory':
`+' is an invalid character in a configuration storage address
**
GConf:ERROR:gconftool.c:969:main: assertion failed: (err == NULL)
make[5]: *** [install-data-hook] Aborted
make[5]: Leaving directory
`/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/data'
make[4]: *** [install-data-am] Error 2
make[4]: Leaving directory
`/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/data'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory
`/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/data'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4/data'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/build/buildd-gdm3_3.0.4-4+b1-amd64-Higyv6/gdm3-3.0.4'
make: *** [debian/stamp-makefile-install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit
status 2
Full logs available via
https://buildd.debian.org/status/package.php?p=gdm3&suite=sid
Regards,
Adam
--- End Message ---
--- Begin Message ---
Version: 3.4.1-1
Hi,
On Thu, Apr 05, 2012 at 12:02:39PM +0100, peter green wrote:
> >gdm3 FTBFS (when rebuilt against a newer CDBS to pick up hardening
> >flags); from the amd64 build log:
>
> To clarify the actual issue is that gdm3 FTBFS when there is a + in
> the name of the build directory because the build process tries to
> set a gconf config dir under the build directory and gconf doesn't
> like directory names containing +.
Version 3.4.1-1 doesn't call gconf anymore. From the changelog:
* Get rid of anything related to GConf.
So this problem should be gone now.
Cheers,
Ivo
--- End Message ---
