Package: signify-openbsd
Version: 28-1

The signify package is inactive since 2003

https://sourceforge.net/projects/signify

Maintaining this package with the current name prevents another software with the same name to be distributed with the name it's known for everywhere, forcing it to be renamed into 'signify-openbsd' in Debian.

signify should be renamed (signify-mail for example) and signify-openbsd should be renamed to signify in order to avoid confusion as signify-openbsd is widely used and known simply as signify everywhere else.

Hi

I would like that 'apt install signify' install OpenBSD's signify (from
the Debian 'signify-openbsd' package) and not the 2003 mail-related
signify perl script from the Debian 'signify' source package.

I would also like that /usr/bin/signify is OpenBSD's signify, after
doing the 'apt install signify', instead of /usr/bin/signify-openbsd.

As background please read:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951010
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738884

What do you think about the attached debdiff for the existing
(non-OpenBSD) 'signify' source package?

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?  Any objections to an upload?  The
package seems to be orphan'ed and QA-maintained.  One alternative is to
remove the package, but that seems to involve more effort than a QA
upload.

The next step would be for the 'signify-openbsd' source package to
rename the 'signify-openbsd' binary package to 'signify'.  I believe it
should declare a Conflicts and Breaks towards 'signify (<< 1.14-8~)'.

The final step would be for signify-openbsd's 'signify' package to
rename the binary into /usr/bin/signify, and that would require adding a
Conflicts/Breaks towards all versions of signify-mail.

Tomasz, what do you think about this?

Adding debian-devel to get wider review of the
Replaces/Conflicts/version magic, this always tend to confuse me.

See pipeline for the 'signify' source package that I propose to upload:

https://salsa.debian.org/jas/signify/-/pipelines/742414

To make this happen for trixie, I don't see how to do it.  Anyone having
the old 'signify' package on their system would get OpenBSD's signify
instead of the new 'signify-mail' package after an upgrade.  Is that
problem really worth caring about?  I think a release note about this
could solve it.  I believe OpenBSD's 'signify' is important enough to
warrant this to be part of trixie instead of having to wait for t+1.

/Simon

Agreed: the current signify package is a niche tool maintained by QA and
last updated upstream in 2004: it should be renamed without wasting any
more time.