Re: autopkgtest results influencing migration from unstable to testing
On Wed, 06 Jun 2018 at 10:28:53 +0530, Pirate Praveen wrote:
> ruby-state-machines and ruby-state-machines-activemodel should go
> together and even when autopkgtest for the version is unstable passed,
> instead of reducing the age, it is considered a regression because
> autopkgtest for the version in testing failed and age is increased.
Isn't this a sign that ruby-state-machines has broken API, and should gain
"Breaks: ruby-state-machines-activemodel (<< 0.5)" or similar before it
migrates to testing? If so, then the autopkgtest is doing its job: it
has found a bug.
If packages in unstable "should go together" then you need to tell
apt that, otherwise it will assume that arbitrary partial upgrades are
a valid solution. Testing migration uses the same metadata.