dh_gencontrol wrapper breaks kernel dbgsym generation

Reproducing test case:
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/pkg-create-dbgsym/vivid/revision/242
Fix:
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/pkg-create-dbgsym/vivid/revision/243
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/pkg-create-dbgsym/vivid/revision/244 (that second one isn't strictly necessary for the kernel, but it showed up with the test case above, so let's fix it)

https://launchpad.net/~ubuntu-core-dev/+archive/ubuntu/ddeb-test/+packages now has pkg-create-dbgsym 0.66pitti1 which I intend to upload as 0.67 to vivid/utopic/trusty, and backport the fixes to precise. I copied the vivid kernel into the PPA, once it built successfully the SRUs can be accepted.

Hello Martin, or anyone else affected,

Accepted pkg-create-dbgsym into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pkg-create-dbgsym/0.67 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Martin, or anyone else affected,

Accepted pkg-create-dbgsym into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pkg-create-dbgsym/0.67~utopic in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Martin, or anyone else affected,

Accepted pkg-create-dbgsym into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pkg-create-dbgsym/0.67~trusty in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Martin, or anyone else affected,

Accepted pkg-create-dbgsym into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pkg-create-dbgsym/0.50.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The kernel which previously failed to build now built fine:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/7372132

The build log shows that this used pkg-create-dbgsym 0.67.

The precise kernel in https://launchpad.net/~ubuntu-core-dev/+archive/ubuntu/ddeb-test/+packages also built fine.

This bug was fixed in the package pkg-create-dbgsym - 0.50.2

---------------
pkg-create-dbgsym (0.50.2) precise-proposed; urgency=medium

  * testsuite: Add dhtest.customdbgsym for a package that produces its own
    -dbgsym package, like our "linux" source package. Reproduces LP #1450464.
  * pkg_create_dbgsym: When called with -B (i. e. from dh_strip), create a
    marker for dh_gencontrol, so that the latter does not try to process
    custom -dbgsym binaries. (LP: #1450464)
  * dh_strip: Don't try to process *-dbgsym binaries.

 -- Martin Pitt <email address hidden> Thu, 30 Apr 2015 16:45:12 +0200

The verification of the Stable Release Update for pkg-create-dbgsym has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package pkg-create-dbgsym - 0.67~trusty

---------------
pkg-create-dbgsym (0.67~trusty) trusty; urgency=medium

  * Backport to trusty.

pkg-create-dbgsym (0.67) vivid; urgency=medium

  * testsuite: Add dhtest.customdbgsym for a package that produces its own
    -dbgsym package, like our "linux" source package. Reproduces LP #1450464.
  * pkg_create_dbgsym: When called with -B (i. e. from dh_strip), create a
    marker for dh_gencontrol, so that the latter does not try to process
    custom -dbgsym binaries. (LP: #1450464)
  * dh_strip: Don't try to process *-dbgsym binaries.

 -- Martin Pitt <email address hidden> Thu, 30 Apr 2015 16:12:16 +0200

This bug was fixed in the package pkg-create-dbgsym - 0.67~utopic

---------------
pkg-create-dbgsym (0.67~utopic) utopic; urgency=medium

  * Backport to utopic.

pkg-create-dbgsym (0.67) vivid; urgency=medium

  * testsuite: Add dhtest.customdbgsym for a package that produces its own
    -dbgsym package, like our "linux" source package. Reproduces LP #1450464.
  * pkg_create_dbgsym: When called with -B (i. e. from dh_strip), create a
    marker for dh_gencontrol, so that the latter does not try to process
    custom -dbgsym binaries. (LP: #1450464)
  * dh_strip: Don't try to process *-dbgsym binaries.

 -- Martin Pitt <email address hidden> Thu, 30 Apr 2015 16:12:16 +0200

This bug was fixed in the package pkg-create-dbgsym - 0.67

---------------
pkg-create-dbgsym (0.67) vivid; urgency=medium

  * testsuite: Add dhtest.customdbgsym for a package that produces its own
    -dbgsym package, like our "linux" source package. Reproduces LP #1450464.
  * pkg_create_dbgsym: When called with -B (i. e. from dh_strip), create a
    marker for dh_gencontrol, so that the latter does not try to process
    custom -dbgsym binaries. (LP: #1450464)
  * dh_strip: Don't try to process *-dbgsym binaries.

 -- Martin Pitt <email address hidden> Thu, 30 Apr 2015 16:12:05 +0200