* Niels Thykier <[email protected]>, 2012-02-07, 14:35:
11:55 < codehelp> buxy: what happens with -dbg packages which contain multiarch
libs in /usr/lib/debug/usr/lib/$triplet *and* executables in /usr/lib/debug/usr/bin/ ?
11:55 < codehelp> the -dbg package depends on the M-A: same lib package and a
M-A: foreign -bin package.
11:59 < codehelp> for now, I think I'll drop the M-A field from the -dbg
package.
[...]
13:22 < buxy> codehelp: they should be switched to use .build-id (or whatever
it's called) so that they do not conflict between each other
Perhaps a Lintian check for multi-arch -dbg packages to catch
potentional issues.
I believe that my patch for #650445 already catches these issues:
$ lintian bamf-dbg_0.2.104-1_i386.deb
E: bamf-dbg: arch-dependent-file-not-in-arch-specific-directory
usr/lib/debug/usr/lib/bamf/bamfdaemon
But now I relized that the patch also causes false-positives like this:
$ lintian libdb5.3-dbg_5.3.15-2_i386.deb
E: libdb5.3-dbg: arch-dependent-file-not-in-arch-specific-directory
usr/lib/debug/.build-id/0b/2db6fec4b3655ea15d70cb2166f23dba984d0c.debug
E: libdb5.3-dbg: arch-dependent-file-not-in-arch-specific-directory
usr/lib/debug/.build-id/49/32676ba584acbd66c2d9cd93c0fcc21a10a987.debug
[snip - more errors]
As far as I can tell, it takes debhelper compat 8 (or 9) to get
dh_strip to use .build-id (by default at least).
It's only in >= 9.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
