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

[Martin Pitt]

I'm currently looking into using debhelper's dbgsym generation instead
of pkg-create-dbgsym. This requires some modifications, in particular:

  * Naming the dbgsym packages .ddeb instead of .deb (as LP cannot deal with .deb right now)
  * Reading /CurrentlyBuilding to determine whether or not build dbgsyms.

It would be nice if Launchpad builders could move away from
/CurrentlyBuilding and instead set ENABLE_DBGSYM=0 if debug symbols
should *not* be built; for the default, it can either not set it at all
or set ENABLE_DBGSYM=auto. This would then get rid of the
/CurrentlyBuilding parsing logic in dh_strip.

** Also affects: debhelper (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: pkg-create-dbgsym (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: debhelper (Ubuntu)
       Status: New => In Progress

** Changed in: debhelper (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
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 itself:
  New
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/+bug/1623256/+subscriptions