Bug#525547: installs gconf-2.m4 with broken GCONF_SCHEMA_FILE_DIR
rmh.debian.bts at aybabtu.com
Sat Apr 25 12:28:16 UTC 2009
Don't close valid bugs. If you refuse to fix them, there's a tag for you
to indicate that.
On Sat, Apr 25, 2009 at 02:10:09PM +0200, Josselin Mouette wrote:
> Le samedi 25 avril 2009 à 11:48 +0000, Robert Millan a écrit :
> > This package installs /usr/share/aclocal/gconf-2.m4 whose GCONF_SCHEMA_FILE_DIR
> > definition ($(sysconfdir)/gconf/schemas) propagates to aclocal.m4 files,
> > resulting in gconf schema files being installed to /etc, which lintian is not
> > happy with:
> > W: gnote: package-installs-into-etc-gconf-schemas etc/gconf/schemas/gnote.schemas
> > N:
> > N: The package installs files into the /etc/gconf/schemas directory. No
> > N: package should do this; this directory is reserved for local overrides.
> > N: Instead, schemas should be installed into /usr/share/gconf/schemas.
> > N:
> > N: Severity: normal, Certainty: certain
> We do not change the upstream m4 files for this. Just use dh_gconf, or,
> if you like Manoj-like packages, move them by hand and add the calls to
It doesn't seem reasonable that everyone else has to go our of their way to
work around a bug in your gconf-2.m4. Why is it a problem to apply the
patch there instead of:
- Appliing in all the other packages (or working around the problem in
some other way).
- Thereby preventing them from regenerating aclocal.m4 if the need arised.
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
More information about the pkg-gnome-maintainers