The current maintainer of signify, Brian White <bcwhite@pobox.com>,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: signify
Binary: signify
Version: 1.14-1
Maintainer: Brian White <bcwhite@pobox.com>
Architecture: all
Standards-Version: 3.6.1
Format: 1.0
Files:
 87c3991fd2e7f989bf7ffc1b16057b27 561 signify_1.14-1.dsc
 9200aec58ea4c10dab6d19c1f926a9f1 13853 signify_1.14-1.tar.gz
Checksums-Sha1:
 b37e569f16aab27991487ac0dabf59c2f109b36e 561 signify_1.14-1.dsc
 b3b317bde429872c93adef74c9de9d81a1bf7129 13853 signify_1.14-1.tar.gz
Checksums-Sha256:
 0ae97cced03288233872209c92b6003143d0fc48464474582237e4465d6d9b3d 561 signify_1.14-1.dsc
 8c1c19ead3c3dcb40e08a5ead4bba214c930d1e0e06cc18067d090b3d841cdd6 13853 signify_1.14-1.tar.gz
Directory: pool/main/s/signify
Priority: source
Section: mail

Package: signify
Version: 1.14-1
Installed-Size: 92
Maintainer: Brian White <bcwhite@pobox.com>
Architecture: all
Depends: perl5
Description-en: Automatic, semi-random ".signature" rotator/generator
 Signify is a neat little program that allows a random signature to be
 generated from a set of rules.  Each "section" can be one of an unlimited
 number of possibilities, each with its own weighting so those really cool
 quotes can appear more often than others.  Sections can also be placed next
 to each other vertically to create columns.  Each section can be formatted
 independently as left/right/center and top/bottom/vcenter.  See
http://signify.sf.net/ for more information.
Description-md5: 6c75c0e8b2a034e7cc3f0f4a8923169e
Tag: implemented-in::perl, interface::commandline, role::program,
 scope::utility, works-with::mail
Section: mail
Priority: optional
Filename: pool/main/s/signify/signify_1.14-1_all.deb
Size: 15336
MD5sum: bc7dd12a92185003f9e0472a465e95ae
SHA1: cd9235f74c6d8dcf0ee92f5e3f9a7087977e6a18
SHA256: 687d533e64baa03ff78ab9cb996325ab464346264b4dcafd5771ba0edba6db20

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.