Repotest tests packages that shouldn't

[Dmitry Teselkin]

When testing packages that came to additional repo (that is there are two repos in test - main and additional), it might occur that in additional repo there is no binary package from updated source package. Repotest doesn't detect this and tries to install old package from main repo. That fails the test, and this is wrong.

Example - https://packaging-ci.infra.mirantis.net/job/9.0-pkg-pipeline-ubuntu/2711/

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/23364
Submitter: Alexander Evseev <email address hidden>
Branch: master

Commit: 49c210783fa50d32a0f4023b06c1e8cf83b58734
Author: Dmitry Teselkin <email address hidden>
Date: Mon Jul 18 16:36:23 2016

Disable voting for repotest on feature/nfv

Repotest for feature/nfv sometimes can't detect that
binary package was removed in newer version of source
package and tries to install it.

Related-bug: #1604068

Change-Id: I7ab0d5468e802c2d731d1c88f9e97c41413bce02

[Dmitry Teselkin (teselkin-d)]

Please fix the test or remove it at all

[Alexander Tsamutali (astsmtl)]

Now you can use special record `Repotest-Exclude` in commit message to define which packages shouldn't be tested by repotest. For ex.:

Repotest-Exclude: package-a package-b

[Alexander Tsamutali (astsmtl)]

Just commited fix, now testing it.

[Alexander Tsamutali (astsmtl)]

Disregard last comment, posted from another window, after LP timeout.