Re: dh >= 9 builds strange debug-pkg

> See #642158, for an explanation. The short story is, it's easier to > support build-id (from a gdb PoV) than N+1 multi-arched paths. > > It should not cause any issues. Thanks for your answer. So everything is fine as it gets done then, I think. BR, Björn Esser -- To UNSUBSCRIBE, email to

Re: dh >= 9 builds strange debug-pkg

Björn Esser writes: > Hello! > > Why does dh >= 9 (in paticular the latest version in sid) put the > debugging-symbols in > usr/lib/debug/.build-id/$(2-Byte-Random)/$(Random).debug when building > a lib with multi-arch-support? See #642158, for an explanation. The short story is, it's easier to

Re: dh >= 9 builds strange debug-pkg

On Mon, Jun 04, 2012 at 10:03:06AM +0200, Björn Esser wrote: > Why does dh >= 9 (in paticular the latest version in sid) put the > debugging-symbols in > usr/lib/debug/.build-id/$(2-Byte-Random)/$(Random).debug when building > a lib with multi-arch-support? Because it uses NT_GNU_BUILD_ID field to

dh >= 9 builds strange debug-pkg

Hello! Why does dh >= 9 (in paticular the latest version in sid) put the debugging-symbols in usr/lib/debug/.build-id/$(2-Byte-Random)/$(Random).debug when building a lib with multi-arch-support? The package uses straight debhelper. No tweaks in debian/rules, but some usual override_*-indep and o