1) Change your source package so that it provides binaries named like those in Debian. This is mainly in debian/control and some of the debhelper files (install etc.). You can see this easily by diffing the ubuntu and debian packages.
Note that the difference is just the removal of a dash (-) from the binary names, eg:
Ubuntu: libgdamm-3.0-8
Debian: libgdamm3.0-8
2) Change all libgdamm dependencies of packages in hardy to point to the new naming scheme. You can find these by using apt-cache with the rdepends option:
3) Add to your source package transitional packages to ease the gutsy->hardy upgrade. These are dummy packages which just depends on the right dependencies and eventually conflict/replace the old packages.
For example:
Package: libgdamm-3.0-9
Architecture: all
Depends: libgdamm3.0-9
Description: transitional package to new libgdamm naming scheme
This dummy package is provided to smooth the upgrade to the new libgdamm naming scheme.
This package can be safely removed.
It is not the case here, but if there was a previous version of the same package one should have added to the libgdamm3.0-9 stanza in debian/control:
Chris,
to make the transition it is needed to:
1) Change your source package so that it provides binaries named like those in Debian. This is mainly in debian/control and some of the debhelper files (install etc.). You can see this easily by diffing the ubuntu and debian packages.
Note that the difference is just the removal of a dash (-) from the binary names, eg:
Ubuntu: libgdamm-3.0-8
Debian: libgdamm3.0-8
2) Change all libgdamm dependencies of packages in hardy to point to the new naming scheme. You can find these by using apt-cache with the rdepends option:
apt-cache rdepends libgdamm-3.0-8 libgdamm-3.0-dev libgdamm-3.0-doc
libgdamm-3.0-dev
Reverse Depends:
libglom-dev
libgdamm-3.0-doc
Reverse Depends:
libgdamm-3.0-dev
libgdamm-3.0-8
Reverse Depends:
libglom0
libgdamm-3.0-dev
glom
So this is just the glom src package.
3) Add to your source package transitional packages to ease the gutsy->hardy upgrade. These are dummy packages which just depends on the right dependencies and eventually conflict/replace the old packages.
For example:
Package: libgdamm-3.0-9
Architecture: all
Depends: libgdamm3.0-9
Description: transitional package to new libgdamm naming scheme
This dummy package is provided to smooth the upgrade to the new libgdamm naming scheme.
This package can be safely removed.
It is not the case here, but if there was a previous version of the same package one should have added to the libgdamm3.0-9 stanza in debian/control:
Conflicts: libgdamm-3.0-9 (<< ${source:Version})
Replaces: libgdamm-3.0-9 (<< ${source:Version})
4) Request the removal of the old ubuntu packages from the archive