[Bug 1623256] Re: adjust the way to create dbgsym packages like Debian does

[Colin Watson]

launchpad-buildd (142) trusty; urgency=medium

  * lpbuildd.binarypackage: Pass DEB_BUILD_OPTIONS=noautodbgsym if we have
    not been told to build debug symbols (LP: #1623256).
  * debian/upgrade-config, lpbuildd.slave: Drop compatibility with ancient
    pre-lucid versions of python-apt.
  * lpbuildd.pottery.intltool: Remove unused and Python-3-unfriendly
    string/file conditional from ConfigFile.__init__.
  * Use Python-3-compatible forms of "print" and "except".
  * buildsnap: Set SNAPCRAFT_SETUP_CORE=1 during pull phase so that
    snapcraft will fetch and unpack the core snap for classic confinement
    when necessary (LP: #1650946).

 -- Colin Watson <cjwatson at ubuntu.com>  Fri, 10 Feb 2017 14:53:43 +0000

** Changed in: launchpad-buildd
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debhelper in Ubuntu.
https://bugs.launchpad.net/bugs/1623256

Title:
  adjust the way to create dbgsym packages like Debian does

Status in launchpad-buildd:
  Fix Released
Status in debhelper package in Ubuntu:
  In Progress
Status in pkg-create-dbgsym package in Ubuntu:
  New

Bug description:
  Debian now creates dbgsym packages in it's own way, incompatible with
  the Ubuntu approach.  This leads to ftbfs or failed-to-upload packages
  without changing the packaging.  It might be feasible to adjust the
  packaging, however in the long term it would be better to adjust to
  the way to build the dbgsym packages the Debian way.

  example: https://launchpad.net/ubuntu/+source/librevenge/0.0.4-6

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1623256/+subscriptions