Dnia 2015-09-20, nie o godzinie 19:38 +0200, Niels Thykier pisze:
[ cut ]
> > I added DH_BUILD_DDEBS = 1 to d/rules, changed dh_strip to use
> > --ddeb-migration and not -dbg-package, and removed *-dbg from
> > d/control.
> > After building I got python-pyopencl{3}-dbgsym*.dbg.
> > Those packages c
On 2015-09-20 19:04, Tomasz Rybak wrote:
> Dnia 2015-08-25, wto o godzinie 13:41 +, Jean-Michel Vourgère
> pisze:
>> Hi
>>[...]
>>
>> The question is also valid for python2:
>>
>> When using dh --with python2 *and* build-depending on python-all-dbg,
>> I'm getting [1]:
>> * Some files like /usr
Dnia 2015-08-25, wto o godzinie 13:41 +, Jean-Michel Vourgère
pisze:
> Hi
>
> Nikolaus Rath wrote:
> > On Aug 24 2015, Sebastian Ramacher wrote:
> > > What's the plan for python(3)-*-dbg packages that include both
> > > Python extensions
> > > built for the python-dbg interpreter and debug sy
On 2015-08-27 14:57, Bastian Blank wrote:
> On Mon, Aug 24, 2015 at 11:12:41PM +0200, Niels Thykier wrote:
>> * ddebs are Debian packages with the extension .deb that
>> contain debugging symbols and are built implicitly.
>> - A package foo_1.23.deb will receive a corresponding
>> foo_1.23-
On Mon, Aug 24, 2015 at 11:12:41PM +0200, Niels Thykier wrote:
> * ddebs are Debian packages with the extension .deb that
> contain debugging symbols and are built implicitly.
> - A package foo_1.23.deb will receive a corresponding
> foo_1.23-dbgsym.ddeb package.
Are they named .deb or .dd
On Mon, Aug 24, 2015 at 02:28:05PM -0700, Steve Langasek wrote:
> I wonder how this list was arrived at. Offhand, I see the libc6-dbg and
> python3.5-dbg packages are both in section 'debug', both of which are part
> of the build-dependency closure of main; I'm pretty sure we don't want them
> shu
Hi
Nikolaus Rath wrote:
> On Aug 24 2015, Sebastian Ramacher wrote:
>> What's the plan for python(3)-*-dbg packages that include both Python
>> extensions
>> built for the python-dbg interpreter and debug symbols? Should they also
>> change
>> their Section to something else?
>
>
> .. and wil
On 2015-08-25 11:29, Matthias Klose wrote:
> On 08/24/2015 11:12 PM, Niels Thykier wrote:
>> * debhelper will be including debug-ids in the control file to make it
>>easier to find the necessary debug symbols for a given file.
>>- Thanks to paultag for this idea.
>>- This is merged int
On 08/24/2015 11:12 PM, Niels Thykier wrote:
> * debhelper will be including debug-ids in the control file to make it
>easier to find the necessary debug symbols for a given file.
>- Thanks to paultag for this idea.
>- This is merged into git and will be included in the next upload.
a
On Aug 24 2015, Sebastian Ramacher wrote:
> Hi
>
> On 2015-08-24 23:12:41, Niels Thykier wrote:
>> * Up to 5 packages need to change section (see "Implementation-
>>details" below)
>>- See #796834, #796836, #796839, #796840, and #796842.
>
> What's the plan for python(3)-*-dbg packages th
Hi
On 2015-08-24 23:12:41, Niels Thykier wrote:
> * Up to 5 packages need to change section (see "Implementation-
>details" below)
>- See #796834, #796836, #796839, #796840, and #796842.
What's the plan for python(3)-*-dbg packages that include both Python extensions
built for the python
On 2015-08-24 23:28, Steve Langasek wrote:
> Hi Niels,
>
> On Mon, Aug 24, 2015 at 11:12:41PM +0200, Niels Thykier wrote:
>> [...]
>
> I wonder how this list was arrived at. Offhand, I see the libc6-dbg and
> python3.5-dbg packages are both in section 'debug', both of which are part
> of the bui
Hi Niels,
On Mon, Aug 24, 2015 at 11:12:41PM +0200, Niels Thykier wrote:
> * Up to 5 packages need to change section (see "Implementation-
>details" below)
>- See #796834, #796836, #796839, #796840, and #796842.
> Implementation-details
> ==
>
> There are some deta
Hi,
Here is the "post-debconf" status on automatic debug packages ("ddebs").
The previous status from 2015-06-29 can be found in [0].
What is it?
===
* ddebs are Debian packages with the extension .deb that
contain debugging symbols and are built implicitly.
- A package foo_1.23.deb
14 matches
Mail list logo
