Bug#702190: dconf-editor warnings

[Jeremy Bicha]

Control: tags -1 +moreinfo

Arnaud, thanks for helping triage these bugs. The Debian Bug Tracker
does not automatically CC the bug reporter or people who have left
comments.

Stanislav, are you still able to reproduce this bug?

Thanks,
Jeremy Bicha

On Sun, Feb 18, 2018 at 9:45 AM, Arnaud Bonatti
 wrote:
> Upstream maintainer here.
>
> In the initial comment of the bug report, there are two different
> warnings. Both of them were displayed (I think) because historically
> (until release 3.20) Dconf Editor was using a custom schemas parser.
>
> The first:
> ** (dconf-editor:29681): WARNING **: dconf-schema.vala:330: Unknown
> property on , extends
> was a bug of Dconf Editor, as that property is valid.
>
> The second:
> ** (dconf-editor:29681): WARNING **: dconf-schema.vala:401: Unknown
> tag 
> looks more weird to me, as the tag  should never have been
> accepted when compiling the schema (see indicative DTD[1]). If you
> know what schema was causing that, please fix it and report a bug to
> glib-compile-schemas if it accepts even now to compile it.
>
> [1] https://gitlab.gnome.org/GNOME/glib/blob/master/gio/gschema.dtd
>
> Anyway, as Dconf Editor uses GLib.Settings for two years, the warnings
> shouldn’t be displayed anymore. Are you sure 3.22 has been concerned
> at one point here?
>
> --
> Arnaud Bonatti
> 
> courriel : arnaud.bona...@gmail.com
>

Bug#702190: dconf-editor warnings

[Arnaud Bonatti]

Upstream maintainer here.

In the initial comment of the bug report, there are two different
warnings. Both of them were displayed (I think) because historically
(until release 3.20) Dconf Editor was using a custom schemas parser.

The first:
** (dconf-editor:29681): WARNING **: dconf-schema.vala:330: Unknown
property on , extends
was a bug of Dconf Editor, as that property is valid.

The second:
** (dconf-editor:29681): WARNING **: dconf-schema.vala:401: Unknown
tag 
looks more weird to me, as the tag  should never have been
accepted when compiling the schema (see indicative DTD[1]). If you
know what schema was causing that, please fix it and report a bug to
glib-compile-schemas if it accepts even now to compile it.

[1] https://gitlab.gnome.org/GNOME/glib/blob/master/gio/gschema.dtd

Anyway, as Dconf Editor uses GLib.Settings for two years, the warnings
shouldn’t be displayed anymore. Are you sure 3.22 has been concerned
at one point here?

-- 
Arnaud Bonatti

courriel : arnaud.bona...@gmail.com