Uniqueness of .deb versions/filenames over distributions
Hi,
we bundle some tools in a native package for use on Ubuntu
Precise and Trusty
(http://git.wikimedia.org/summary/?r=labs/toollabs.git).
Currently the package is identical for both distributions,
so (for example) misctools_1.9_amd64.deb could be used
everywhere.
I want to add a dependency calculated by debian/rules that
is different per distribution
(https://gerrit.wikimedia.org/r/#/c/268563/) which will
cause the created packages to be different as well. When I
added the test packages to the per-distribution repositories
of our aptly server and then tried to publish them, aptly
complained:
| scfc@toolsbeta-aptly-server-01:~$ sudo aptly publish --skip-signing update precise-toolsbeta
| Loading packages...
| Generating metadata files and linking package files...
| ERROR: unable to publish: unable to process packages: error linking file to /srv/packages/public/pool/main/t/toollabs/jobutils_1.10~dev_all.deb: file already exists and is different
| scfc@toolsbeta-aptly-server-01:~$
This leads me to the questions:
- Must .deb versions/filenames be unique over all distribu-
tions or is it sufficient if package_0.1_amd64.deb is
unique in a distribution (and thus there is an error in
aptly)?
- If they must be unique over all distributions, what is the
best practice for debian/* in that case? AFAICS, one
could consider the package for Precise a "backport" and
follow the versioning scheme for backports, but I would
like (very much) to keep one combined source repository.
- Are there example packages in the archives that demon-
strate that best practice?
TIA,
Tim
Reply to: