Le dimanche 18 octobre 2009 à 10:31 +1100, Ben Finney a écrit :
> =
> override_dh_pysupport:
> dh_pysupport /usr/share/backintime/
> =
>
> Is this necessary? Why can't ‘dh_pysupport’ do this without being
> overridden here?
Yes, dh_pysupport only looks at /usr/share/$package
and
Ben Finney writes:
> Ben Finney writes:
>
> > Once I learn how to make a ‘foo-dbg’ package, I can do that in the
> > next release […]
>
> I've learned some about creating a ‘foo-dbg’ package [0]. However, I'm
> ending up with a source package that installs none of the Python files
> into any of
On Sun, Oct 18, 2009 at 10:31:02AM +1100, Ben Finney wrote:
> Thanks, ‘backintime’ does indeed meet these criteria.
>
> The ‘debian/rules’ file is doing some things that I'm confused about:
>
> =
> override_dh_auto_clean:
> rm -rf locale common/po/*.mo
> find $(CURDIR) -name "
Ben Finney wrote:
> Paul Wise writes:
>
>> Do you object to spelling-error-in-binary,
>> duplicated-key-in-desktop-entry, embedded-zlib, duplicate-font-file or
>> the other lintian tests that check upstream stuff?
>
> I think they lead to widely-used, persistent overrides, and I think such
> ove
Bernd Zeimetz writes:
> Usually an override is a fail in the maintainer's brain or a bug in
> lintian. Only in rare cases overrides are the right way to go.
Yes, that's pretty much my point: that *if* a Lintian check leads to
many maintainers adding an override for that tag that persist over tim
5 matches
Mail list logo
