On 2020-03-11 20:31, Daniel Kahn Gillmor wrote:
> On Wed 2020-03-11 21:42:43 +0100, Aurelien Jarno wrote:
> >> Every other debug symbol package in debian is named $foo-dbgsym.  libc6
> >> seems to be the exception.
> >
> > Well libc6-dbg is not a standard dbgsym package:
> > - It is a dependency for other packages
> > - It is a build-dependency for other source packages
> > - It is not an automatic debug package (ie using debhelper) as we need
> >   to strip libpthread.so and crt*.o differently. This means that the
> >   resulting package do not have the same properties.
> Thanks for outlining these differences.  I expected that it would indeed
> be different from others due to the unique position of libc, but i
> didn't know the details.
> >> Can we please rename this package (along with a transitional package to
> >> help folks upgrade from libc6-dbg) and set up an appropriate Provides:
> >> at least?
> >
> > With all the above said, I am not sure it's something we can do. However
> > I don't know who can actually answer that question.
> What about just adding a Provides: libc6-dbgsym to the package?  That
> should make it findable at least, for people who are now used to the
> convention that foo's debug symbols are in foo-dbgsym.

That would clearly work for your use case. Now I am not sure it won't
break other things. I asked on IRC and so far only get the confirmation
that the package shall not be renamed to libc6-dbgsym.

Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature

Reply via email to