lp://staging/ubuntu/lucid-updates/pkg-create-dbgsym
- Get this branch:
- bzr branch lp://staging/ubuntu/lucid-updates/pkg-create-dbgsym
Branch merges
Branch information
Recent revisions
- 43. By Martin Pitt
-
pkg_create_dbgsym: Do not check debian/files for whether we already
processed a .ddeb, since Launchpad Soyuz disables dpkg-distaddfile for
ddebs still. Instead, skip the run if we do not find any unstripped binary
in the current package. (LP: #562418) - 42. By Martin Pitt
-
* Add tests/dhtest.
doublestrip/ : Call dh_strip twice, to check whether this
keeps the debug symbols intact. This reproduces LP #562418, where debug
symbols and CRC checksums were damaged due to double-stripping.
* pkg_create_dbgsym: Do nothing if we already have built a .ddeb during this
package build, i. e. it is in debian/files already. This fixes
overwriting good .ddebs and debug links in case dh_strip gets called
twice. Thanks to Tormod Volden for investigating this! (LP: #562418)
* debian/control: Bump Standards-Version to 3.8.4 (no changes necessary). - 41. By Martin Pitt
-
* tests/dhtest.dbg2: Add a new package dhtest2-extra which we exclude from
dh_strip with -N. This causes dhtest2-dbgsym to not be generated and thus
reproduces LP #566602.
* dh_strip: Fix the "is this package in this list" grep to only match on
whitespace separation, not on e. g. dashes (which grep -w does). This
caused some ddebs like "libglib2.0-0-dbgsym" not to be built if dh_strip
was called with ignoring a similar package name (-Nlibglib2.0-0-refdbg) .
To make this more robust, define a new shell function in_list() for this
and just implement it once. (LP: #566602) - 40. By Michael Bienia
-
Strip -O from options passed from dh not only for comparison but also for
processing them. (LP: #520767) - 38. By Loïc Minier
-
* tests/run: set the new var PKG_IGNORE_
CURRENTLY_ BUILDING= 1 instead of
NO_PKG_MANGLE=1 since pkg-create-dbgsym also disables itself when setting
NO_PKG_MANGLE=1 and this breaks the testsuite; build-conflict with
pkgbinarymangler << 66~. Also, unset NO_PKG_MANGLE as it's set by buildds
and will cause the same issue.
* dh_strip: if PKG_IGNORE_CURRENTLY_ BUILDING is set to 1 don't read
/CurrentlyBuilding to decided whether or not to build -dbgsym packages but
build them unconditionally.
* Build-depend on gdb for the testsuite and on cdbs for the cdbstest
package. - 37. By Loïc Minier
-
tests/run: set NO_PKG_MANGLE=1 in the env when calling dpkg-buildpackage
to build test packages as to avoid pkgbinarymangler's pkgsanitychecks to
fail the build when it notices another package than the /CurrentlyBuilding
one is being built. Ideally, we'd also hook into dpkg-buildpackage or
some other place to detect what is being built. - 36. By Loïc Minier
-
* Drop XB-Python-Version from the headers we copy over from debian/control
for -dbgsym packages: it's usually set to ${python:Versions} -- but the
-dbgsym package has no such substvar -- and the -dbgsym isn't a python-
lib anyway.
* Add ${misc:Depends}.
* Bump debhelper build-dep to >= 7 for dh_prep.
* Rewrite rules using "dh" since we need debhelper 7 anyway.
* Also test for presence of tests/testsuite.tmp to fail clean:.
* Adapt dh_strip to test whether it's looping trying to run itself and also
to try running /usr/bin/dh_strip in the case where pkg-create-dbgsym is
not installed in the build environment (but debhelper is); this allows
running the testsuite during build, so do that.
* Bump debhelper build-dep to >= 7.0.50~ for overrides. - 34. By Loïc Minier
-
Also skip over XB-Python-Version header when generating the new control
file; this avoids the "unknown substitution variable ${python:Versions}"
warning when generating the -dbgsym packages; thanks Michael Bienia.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/ubuntu/maverick/pkg-create-dbgsym