Ben Hutchings <b...@decadent.org.uk> writes: > On Sat, 2024-10-05 at 12:31 +0200, Simon Josefsson wrote: > [...] >> This will rename the binary package to 'signify-mail', as suggested in >> the first bug report above, and add a 'signify (<< 1.14-8~)' Replaces >> header. >> >> Is anything more required here? > [...] > > Yes, I think you should also rename the source package signify.
I think that would be nice from a human namespace perspective but I don't know if Debian have any documented process for doing that. Can anyone find a pointer to relevant documentation? What is the process? Upload 'signify' to NEW again as 'signify-mail', and then ask for removal of the 'signify'? Can the source package name then be re-used by 'signify-openbsd'? Or is there a rename operation policy, asking for 'signify' to be renamed to 'signify-mail', and 'signify-openbsd' renamed to 'signify'? Doing renames is confusing for a long-term perspective, how is that piece of meta-information recorded and where? Is there any earlier examples of a source package rename? > Debbugs doesn't always properly distinguish source and binary package > names. This goes badly when there are a source and binary package of > the same name, but the binary package is built by a different source > package. > > And of course, a situation like that is also confusing to humans. +1 /Simon
signature.asc
Description: PGP signature
