Re: Kernel debug symbols are always NEW

2016-11-22 Thread Ansgar Burchardt
Bastian Blank writes: > On Mon, Nov 14, 2016 at 05:47:25PM +, Ben Hutchings wrote: >> If I've diagnosed this correctly, I see several possible options to fix >> this: >> >> a. dpkg excludes packages with Package-Type: debug from the Binary >>field >> b. dak ignores packages ending -dbgsym i

Re: Kernel debug symbols are always NEW

2016-11-17 Thread Ben Hutchings
On Mon, 2016-11-14 at 19:07 +0100, Bastian Blank wrote: > On Mon, Nov 14, 2016 at 05:47:25PM +, Ben Hutchings wrote: > > If I've diagnosed this correctly, I see several possible options to fix > > this: > > > > a. dpkg excludes packages with Package-Type: debug from the Binary > >    field > >

Re: Kernel debug symbols are always NEW

2016-11-14 Thread Bastian Blank
On Mon, Nov 14, 2016 at 05:47:25PM +, Ben Hutchings wrote: > If I've diagnosed this correctly, I see several possible options to fix > this: > > a. dpkg excludes packages with Package-Type: debug from the Binary >field > b. dak ignores packages ending -dbgsym in the Binary field. > c. dak'

Kernel debug symbols are always NEW

2016-11-14 Thread Ben Hutchings
There seems to be a problem with the new-style dbgsym packages for the kernel. On (almost?) every upload, they are treated as NEW whether or not there has been an ABI change leading to package name changes. I think this explains it: 1. dak treats an upload as NEW if not all packages in the Binar