diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2016-11-11 13:15:27 +0100 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2016-11-11 23:40:39 +0100 |
| commit | 7434f15cb688f3a394accba2ce10615adcb9c48a (patch) | |
| tree | 63483149f01f0bd2ec696f44fff9cfc5fb2968e2 /test/integration/test-method-rred | |
| parent | d0c7d4d6328418b7c9f434a3398e5f7e08b7359c (diff) | |
show distribution mismatch for changed codenames
We have the last Release file around for other checks, so its trivial to
look if the new Release file contains a new codename (e.g. the user has
"testing" in the sources and it flipped from stretch to buster).
Such a change can be okay and expected, but also be a hint of problems,
so a warning if we see it happen seems okay. We can only print it once
anyhow and frontends and co are likely to ignore/hide it.
Diffstat (limited to 'test/integration/test-method-rred')
0 files changed, 0 insertions, 0 deletions