| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
It has one remaining use in experimental (see #785394)
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
(Thanks, Luca Falavigna)
|
|
* Finalized v9 mode, which is the new recommended default.
(But continuing to use v8 is also fine.)
* It is now deprecated for a package to not specify a compatability
level in debian/compat. Debhelper now warns if this is not done,
and packages without a debian/compat will eventually FTBFS.
|
|
override targets instead.
|
|
|
|
#604727
|
|
|
|
|
|
#578805
|
|
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.)
|
|
|
|
|
|
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.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#548382
|
|
|
|
after -- is much more sane. (However, -u will not go away any time soon.) Closes: #554509
|
|
The -a flag now does the same thing as the -s flag, so debhelper users do
not need to worry about using the -s flag when building a package that only
builds for some architectures, and dh will also work in that situation.
Closes: #540794
|
|
|
|
|
|
|
|
|
|
|
|
uses them.
Affected options are: -x, -r, -R, -l, -L, -m, --include-conffiles,
--no-restart-on-upgrade, --no-start, --restart-after-upgrade,
--init-script, --filename, --flavor, --autodest, --libpackage, --add-udeb,
--dpkg-shlibdeps-params, --dpkg-gencontrol-params, --update-rcd-params,
--major, --remove-d, --dirs-only, --keep-debug, --version-info,
--list-missing, --fail-missing, --language, --until, --after, --before,
--remaining, --with
* If any third-party debhelper commands use any of the above options,
they will be broken, and need to be changed to pass options to init().
* To avoid breaking rules files that pass options to commands that do not
use them, debhelper will now only warn if it encounters an unknown
option. This will be converted back to an error later.
|
|
passing a hash to init(), which is later passed on the Getopt::Long. Closes: #370823
|
|
|
|
in the prerm, and instead restarts it in the postinst, keeping its downtime minimal. Since some daemons could break if files are upgraded while they're running, it's not the default. It might become the default in a future (v8) compatability level. Closes: #471060
|
|
later).
|
|
|
|
|
|
preinst and postinst scripts. For example, if a package uses
dh_pysupport before dh_installinit, the prerm will first stop the init
script and then remove the python files.
* Introducing beginning of v6 mode.
* dh_installwm: In v6 mode, install a slave manpage link for
x-window-manager.1.gz. Done in v6 mode because some window managers
probably work around this longstanding debhelper bug by registering the
slave on their own. This bug was only fixable once programs moved out of
/usr/X11R6. Closes: #85963
* dh_builddeb: In v6 mode, fix bug in DH_ALWAYS_EXCLUDE handling, to work
the same as all the other code in debhelper. This could only be fixed in
v6 mode because packages may potentially legitimately rely on the old
buggy behavior. Closes: #242834
* dh_installman: In v6 mode, overwrite exsiting man pages. Closes: #288250
|
|
|
|
best of
a difficult situation.
* Revert all dh_python changes. Closes: #381389, #378604
* Conflict with python-support << 0.5.3 and python-central << 0.5.5.
* Make dh_python do nothing if debian/pycompat is found.
The new versions of dh_pysupport or dh_pycentral will take care of
everything dh_python used to do in this situation.
* dh_python is now deprecated. Closes: #358392, #253582, #189474
* Non-maintainer upload.
* Update of dh_python
- when buidling for a non-standard Python version, generate more
reasonable Depends like "python (>= X.Y) | pythonX.Y"
Closes: #375576
- fix handling of private extensions. Closes: #375948
- fix parsing of XS-Python-Version, it didn't work if only fixed versions
were listed in XS-Python-Version.
- fix use of unitialized value. Closes: #374776
- fix typos in POD documentation. Closes: #375936
* Non-maintainer upload.
* Update of dh_python
- vastly refactored, easier to understand, and the difference
between old policy and new policy is easier to grasp
- it supports an -X option which can be used to not scan some files
- uses debian/pyversions as reference source of information for
dependencies but also parse the XS-Python-Version header as fallback.
- ${python:Versions}'s default value is XS-Python-Version's value
instead of "all" when the package doesn't depend on a
specific python version. Closes: #373853
- always generate ${python:Provides} and leave the responsibility to the
maintainer to not use ${python:Provides} if he doesn't want the
provides.
- uses debian/pycompat or DH_PYCOMPAT as reference field to run in new
policy mode. The presence of XS-Python-Version will also trigger the
new policy mode (this is for short-term compatibility, it may be removed in
the not too-distant future).
DH_PYCOMPAT=1 is the default mode and is compatible to the old policy.
DH_PYCOMPAT=2 is the new mode and is compatible with the new policy.
* Use "grep ^Version:" instead of "grep Version:" on the output of
dpkg-parsechangelog since the above changelog entry matched "Version:" and
thus made the build fail.
* Non-maintainer upload.
* Integrate the new dh_python implementing the new Python policy. Closes: #370833
|
|
|
|
|
|
|
|
|
|
|
