On 04/06/2017 08:39 PM, Ondrej Novy wrote: > And auto -dbgsym doesn't support python-dbg. So it's wrong for Python C > modules.
I guess I need to read more about this then. On 04/06/2017 06:31 PM, Dmitry Shachnev wrote: > In my opinion a better solution (for Stretch) would be just adding an > Architecture: field to the -dbg packages (and for Buster, porting the > code to support big endian architectures). This looks like the most reasonable solution to me. Thoughts anyone? Cheers, Thomas Goirand (zigo)