| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids ambiguities when parsing options to be passed on to debhelper
commands. (See #570039)
In the end, the idea of putting the debhelper command options after --
seemed to need too much knowledge about whether an option like
--buildsystem is a dh option or a command option.
I did consider making no change.. The ambiguities this eliminates are
small. But it seemed worth simplifying dh's option parser, and only about
1/6th of calls to dh in the archive don't put the sequence first already.
(Docs have shown that as the right thing to do for some time.)
|
| |
|
|
|
|
| |
incorrectly matching things like "foo.sources". Closes: #583328
|
| |
|
| |
|
| |
|
|
|
|
| |
still uses them.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2 packages in the archive still use it, but both like this:
ifneq ($(shell dh_testversion '<<' 7.4.10 2>/dev/null && echo old),old)
dh_parallel = --parallel
endif
Happily, the way that was written, if the command doesn't exist,
it does the right thing and enables the behavior for the new debhelper.
Not that it would greatly matter if it did not, since --parallel is not
crucial.
|
|
|
|
| |
it generates shlibs files for. This means that -X can be used to exclude libraries from processing by dpkg-gensymbols. It also means that libraries in unusual locations, where dpkg-gensymbols does not itself normally look will be passed to it, a behavior change which may break some packages. Closes: #557603
|
|
|
|
| |
commands. (Unknown options in DH_OPTIONS still only result in warnings.)
|
|
|
|
| |
dpkg supports the field now, so no XC- needed
|
| |
|
|
|
|
| |
not present in the same binary package, on advice of Colin Watson. (To support eventual so search paths.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
As per the upcoming policy change discussed in #579457,
perlapi-$Config{debian_abi} is preferred over perlapi-$Config{version}
where available.
|
| |
|
|
|
|
| |
typical package with no explicit architecture mentions in control file or debhelper config files.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
dpkg-architecture at all for simple comparisons not involving architecture wildcards. Closes:# 579317
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Starting from 2.28.1-2, the gconf2 package uses triggers which make the
maintainer scripts obsolete.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
joeyh: debhelper has an undocumented variable with INTERNAL in its name.
People keep trying to use it. Why?
liw: debhelper is magic. magic is power derived from secrets. secrets are
desireable. solution: document it. :)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
acting on all packages in the control file, which was a guaranteed failure if the control file listed packages that did not build for the target architecture. After recent optimisations, this default behavior can efficiently be changed to the more sane default of acting on only packages that can be built for the current architecture. This change is mostly useful when using minimal rules files with dh. Closes: #572077
|
| |
|
|
|
|
| |
all packages are acted on (due to architecture limits or flags). Closes: #570373
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
debhelper 7.4.11. Closes: #570503
Previously the test used make -s -n | head -n 1 and then chomped the
output. In the case of this bug, root-system's Makefile *always* outputs
something to stdout, even for targets that don't exist, before configure is
run. It accidentially worked before, since the first line it outputs
happens to be empty.
So bring back the chomp to retain compatability with this package that used
to work before, but the test only does the right thing for this package due
to sheer luck, really.
|
| |
|
| |
|
|
|
|
| |
misbehave when stderr is closed. Reopen it to /dev/null when testing for the existance of a makefile target. Closes: #570443
|
| |
|