Renaming a package
-----BEGIN PGP SIGNED MESSAGE-----
this has already been discusses some times, but
since this is a new situation for me I want to be
sure that it is still true and that I handle it properly :-)
Upstream application (non-library) has changed its name.
I want to reflect this new name in the debian
package name while ensuring that apt-get dist-upgrade
works seamless and pulls in the new package.
I create a new package with the new name which will
get uploaded to the NEW queue. This package replaces the
old package and conflicts with the old package:
Conflicts: oldPackage (<< firstVersionOfNewPackage)
Once the package has moved from the NEW queue to unstable,
I create a new revision of the old package which
serves as dummy package. It does not install any files
(except the mandatory ones in /usr/share/doc) and
depends on the new package.
Finally, after etch has been released end of this year,
I file a bug asking ftpmaster to remove the old, dummy package.
Is this the correct approach? Anything I missed?
Thanks & Best Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----