Bug #6885
Updated by Brett Smith over 8 years ago
As we improve our deployment infrastructure, it's happening more and more that we make improvements to our packages that don't change the underlying code: more accurate dependencies, changes in support scripts like @arvados-api-server-upgrade.sh@, etc. Right now these changes don't trigger a new package build. We always use fpm's default iteration "package version" setting of 1, and fpm doesn't rebuild packages when it sees a destination package with the correct software version+iteration software+package version already on disk. We need at least a manual process to be able to increment/set the iteration. package version. Engineering to spec a solution.