Thanks for review! I tried to revise the plan below, does this work? I think we should compare this plan to simply remove the 'signify' package, but haven't fleshed out that plan yet.
/Simon x) Take current non-OpenBSD 'signify' source package and upload NEW 'signify-mail' package, say version 1.14-8 (?), that provides /usr/bin/signify-mail instead of /usr/bin/signify, and has d/control: Source: signify-mail ... Package: signify-mail Replaces: signify (<= 1.14-7) Conflicts: signify (<= 1.14-7) ... Package: signify Depends: signify-mail Breaks: signify (<= 1.14-7) Replaces: signify (<= 1.14-7) Provides: signify x) Normal archive cleanup should remove the old 'signify' package. If this doesn't happen, once 'signify-mail' has entered testing, open a ftp.debian.org RM bug for the old package 'signify' to get the binary packages removed from unstable. x) File a wishlist bug for 'signify-openbsd' (with patch) to ALSO provide /usr/bin/signify (hardlink?), and to add a: Conflicts: signify (<= 1.14-7) Could it be a 'Conflicts: signify' to get the transitional dummy package removed after installing 'signify-openbsd'? Or does that just break upgrades? x) File a bug to suggest a trixie release note saying that the non-OpenBSD 'signify' package has been rename to 'signify-mail', and provides /usr/bin/signify-mail instead. Say that the 'signify-openbsd' package now provide /usr/bin/signify. Also say that for trixie+1 the intention is for the OpenBSD signify package to ship a 'signify' package that provide /usr/bin/signify. x) Open a bug for 'signify-mail' to say that the transitional package should be removed in trixie+1. x) Open a wishlist bug for 'signify-openbsd' (with patch) to track that in trixie+1 (+2?) it should provide a 'Package: signify' that has /usr/bin/signify and to add: Conflicts: signify (<= 1.14-7) Replaces: signify (<= 1.14-7) The 'signify-openbsd' binary package should be left around as a empty dummy package for transitions to the new 'signify' binary package: Package: signify-openbsd Depends: signify Breaks: signify-openbsd (<= x.y.z) Replaces: signify (<= x.y.z) Provides: signify Not sure when it makes sense to drop /usr/bin/signify-openbsd from the 'signify' package? trixie+1? x) OPTIONAL: Open a wishlist bug for 'signify-openbsd' to, after trixie, upload itself as a NEW 'signify' source package and to ask for removal of the old 'signify-openbsd' source package. It was suggested this can trigger BTS bugs, so may not be worth doing. It doesn't really gain anything except aesthetics. x) Open a wishlist bug for the OpenBSD signify package to remove the transitional 'signify-openbsd' package for trixie+2 (+3?). The /usr/bin/signify-openbsd name is then also removed.
signature.asc
Description: PGP signature
