Re: Auto reject if autopkgtest of reverse dependencies fail or cause FTBFS
On Sat, 2017-01-14 at 11:05 +0100, Ole Streicher wrote:
> I don't see the need to keep things in sync: If a new failure is
> detected, it creates an RC bug against the migration candidate, with an
> "affects" to the package that failed the test. The maintainer then has
> the possibilities:
> * solve the problem in his own package, upload a new revision, and close
> the bug there
> * re-assign the problem to the package that failed the test is the
> problem lies there. In this case, that maintainer can decide if the
> problem is RC, and if not, then lower the severity.
> In any case, the maintainers can follow the established workflow, and if
> one needs to look up the problems a year later, one can just search for
> the bug.
You missed the (not at all hypothetical) case:
* downgrades the bug, regardless of the practical impact of the failure,
just so her package can migrate.