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 Binary field are included in the overrides file. 2. dak treats an upload as NEW if not all binary packages included are in the overrides file, *except* for packages with Package-Type: debug. 3. Packages with Package-Type: debug are never added to the overrides file, or packages in the debug archive are ignored when pruning it. 4. debhelper generates dbgsym packages without them ever being included in debian/control, thus they don't get listed in the Binary field and avoids NEW for reasons 1 and 2. 5. The dbgsym packages for the kernel are included in debian/control, so it hits NEW for readon 1. 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's override file includes dbgsym packages (somehow). d. linux generates dbgsym packages without including them in debian/control. I would be happy to attempt either a or d; less confident about b or c. Please could someone with more knowledge of the debug archive correct or comment on the above? Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
Attachment:
signature.asc
Description: This is a digitally signed message part