-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 > On Wed, Jan 13, 2016 at 16:27:02 -0600, Timothy Pearson wrote: > >> Package: mesa >> Version: 11.0.8-1 >> Severity: normal >> Tags: +patch >> >> The mesa package currently relies on an autogenerated debug symbol package >> for osmesa. The attached patch switches this to a control file-defined debug symbol package. > > Why? This seems backwards. > > Cheers, > Julien >
I thought each package was supposed to have a debug package defined, and that the -dbgsym packages were more of a stopgap? If the -dbgsym packages are the way Debian is going there's a fair amount of build infrastructure that may need to be fixed; there were already reports in the Debian bugtracker of certain package publishing programs failing due to the unexpected -dbgsym package (this actually is what alerted me to the problem in the first place). Can you point me to something showing which way the debug symbols are supposed to be published, and why that decision was made? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iFYEARELAAYFAlaasTQACgkQLaxZSoRZrGH5zADcCpjR4w9y8RIN9gL9eC6+mMAm 1ObPhLBGeZeM5QDfaSx5ifZHhjBGWXciAH2W8xKtQCHgxgnsSA/Oog== =RCHM -----END PGP SIGNATURE-----