diff options
author | David Kalnischkies <david@kalnischkies.de> | 2014-05-10 12:50:00 +0200 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2014-05-10 12:50:00 +0200 |
commit | 7a223b933cab0447438ca2e964576da39078eaf4 (patch) | |
tree | f68a84e3093f5df15c6bcba41cf4503569312d2c /test/integration/test-bug-618288-multiarch-same-lockstep | |
parent | 8710a36a01c0cb1648926792c2ad05185535558e (diff) |
invalid cache if architecture set doesn't match
The cache heavily depends on the architecture(s) it is build for,
especially if you move from single- to multiarch. Adding a new
architecture to dpkg therefore has to be detected and must invalidate
the cache so that we don't operate on incorrect data.
The incorrect data will prevent us from doing otherwise sensible
actions (it doesn't allow bad things to happen) and the recovery is
simple and automatic in most cases, so this hides pretty well and is
also not as serious as it might sound at first.
Closes: 745036
Diffstat (limited to 'test/integration/test-bug-618288-multiarch-same-lockstep')
0 files changed, 0 insertions, 0 deletions