On Fri, Oct 12, 2012 at 16:29:21 -0400, Michael Gilbert wrote: > On Fri, Oct 12, 2012 at 4:05 AM, Julien Cristau <jcristau@debian.org> wrote: > > On Thu, Oct 11, 2012 at 20:34:08 -0400, Michael Gilbert wrote: > > > >> So, the -dbg issue has to do with way in which debug files are > >> compared betwen different arch m-a:same packages. At compat level 9 > >> hashes of the paths are used vs. actual file contents at lower compt > >> levels. Consequently, debug packages cannot be m-a:same at lower > >> compat levels. > >> > > debug packages for a multiarch library have different paths on each > > arch. The bug here IMO is to include debug symbols for the tools in > > libopenjpeg2-dbg. > > Yes, of course that would work, but what about when someone wants to > debug one of the tools. We would need a separate package for that, > but creating a new debug package just for the tools is an intrusive > change at this point. > Needing to debug the tools is both a lot more unlikely than debugging the library or something that uses it, and easy enough to build a debug version of the tool (which you need to do anyway to debug). So I don't think this is a problem. > So, since compat 9 is off the table, I think it best to just not > multiarch the debug package, which lets the user select the right > package for the arch that they're interested in debugging. > *shrug* Cheers, Julien
Attachment:
signature.asc
Description: Digital signature