Hi,
On 10/7/24 21:43, Marvin Renich wrote:
trixie:
remove old src: signify
yes.
single source upload:
src: signify -> signify-mail
binary: signify -> signify-mail
new signify as transitional
unversioned Depends: signify-mail
yes.
trixie+1:
remove transitional binary signify
yes.
trixie+2:
rename binary signify-openbsd -> signify
Is the following necessary?
versioned Conflicts: signify <= version of transitional signify in trixie
no, because the new package has the same name as the old transitional
package and thus implicitly conflicts, also the old package should not
be installed anymore.
version of this signify must be > version of old transitional pkg
not strictly necessary (that's why we leave one release gap in between).
This is a gap in the frontend software though: we have very little UI to
guide people into uninstalling transitional packages -- basically
aptitude showing them in a separate section is the strongest there is.
We also don't have any UI (not even in aptitude -- #990118) to inform
people that they have packages installed that exist in the archive but
they will not receive any upgrades for because their local version is newer.
I believe that renaming the source from signify-openbsd to signify has
very little benefit. What most users are going to see is the binary
package. Anyone searching for the source package generally has enough
knowledge of Debian to find the correct source. Leaving the source name
clearly distinguishes it from the old source.
I'd expect the archive to enforce
oldstable < stable && stable < testing && testing < unstable
for source package versions as well, so if the new package's version
number is higher than the old one's, it can be done in one release,
otherwise it needs two. Not sure how the archive would react if
oldstable and testing have the same version number but different
packages. :P
Simon
