Control: notfound -1 cryptsetup/2:2.6.1-1 This is not an issue in testing because the argon2/cryptsetup combination is okay there. The migration excuses did not catch the grave bugs' changes in time for the migration to happen. I do not think that the changes justify an unblock request, so I am not going to file one.
- Bug#1032221: cryptsetup: libgcc_s.so.1 must be in... Kai Weber
- Bug#1032221: cryptsetup: libgcc_s.so.1 must ... Kai Weber
- Bug#1032221: [pkg-cryptsetup-devel] Bug#... Christoph Anton Mitterer
- Bug#1032221: [pkg-cryptsetup-devel] ... Milan Broz
- Bug#1032221: [pkg-cryptsetup-dev... Christoph Anton Mitterer
- Bug#1032221: cryptsetup: li... Guilhem Moulin
- Bug#1032221: cryptsetup... Christoph Anton Mitterer
- Bug#1032221: crypts... Guilhem Moulin
- Bug#1032221: crypts... Bastian Germann
- Bug#1032221: crypts... Guillem Jover
- Bug#1032518: [pkg-crypt... Guilhem Moulin
- Bug#1032518: [pkg-c... Christoph Anton Mitterer
- Bug#1032221: cryptsetup: libgcc_s.so.1 must ... Daniel Leidert
- Bug#1032235: Bug#1014110: libargon2 0~201907... Paul Gevers
- Bug#1032235: Bug#1014110: libargon2 0~201907... Bastian Germann
- Bug#1032235: Bug#1014110: libargon2 0~201907... Guilhem Moulin
- Bug#1032235: Bug#1014110: libargon2 0~201907... Paul Gevers
- Bug#1032235: Bug#1014110: libargon2 0~201907... Bastian Germann
- Bug#1032235: Bug#1014110: libargon2 0~201907... Guilhem Moulin