Fix #12529
moving files between packages with deb
0%
Description
When moving a file from one package to the other, from ceph to ceph-common for instance, the following must be done in the debian/control file:
Package: ceph Depends: ceph-common (>= 0.94.2-2) Package: ceph-common Replaces: ceph-client-tools, ceph (<< 0.94.2-2), Breaks: ceph (<< 0.94.2-2),
The -2 is greater than -1trusty, -1jessie etc. which are used for releases (see https://github.com/ceph/ceph-build/blob/master/gen_debian_version.sh and https://github.com/ceph/ceph-build/blob/master/build_debs.sh#L35).
This method is difficult to remember and to understand. It could probably be fixed by moving the packaging outside of the sources or by using native package names (without the -1trusty for instance) when releasing deb packages to reflect the fact that they really are native packages.
See also the Breaks & Replaces in debian/control in backports discussion on ceph-devel.
History
#1 Updated by Ken Dreyer over 8 years ago
When working on the packaging for Calamari downstream in RHCS this week, Alfredo found that reprepro does not allow you to add packages with identical names into the same debian repository.
So we have to keep distro-specific suffixes in the packages' versions somewhere :/
#2 Updated by Loïc Dachary over 8 years ago
The right solution is probably to have multiple repositories. IMHO the benefit of mixing distributions in the same repository is not worth bending the intended use case of the tool as well as the debian package naming conventions.
#3 Updated by Sage Weil almost 6 years ago
- Status changed from New to Rejected