On Sat, Apr 25, 2009 at 02:28:15PM +0200, Robert Millan wrote: > reopen 525547 > thanks > > 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 > > gconf-schemas. > > 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:
I gave it some thought; I'm guessing you intend gconf-2.m4 to be usable for upstream developers rather than for debian packages? If this is so, I'll try to get cdbs use --with-gconf-schema-file-dir and be done with it (I couldn't care less about problems with non-cdbs packaging). Anyway, I'm just guessing since you haven't told me. I'm still waiting for an explanation. -- Robert Millan 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." -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
