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 ... Kai Weber
- Bug#1032221: cryptsetup: libgcc_s.so.1 mus... Kai Weber
- Bug#1032221: [pkg-cryptsetup-devel] Bu... Christoph Anton Mitterer
- Bug#1032221: [pkg-cryptsetup-devel... Milan Broz
- Bug#1032221: [pkg-cryptsetup-d... Christoph Anton Mitterer
- Bug#1032221: cryptsetup: ... Guilhem Moulin
- Bug#1032221: cryptset... Christoph Anton Mitterer
- Bug#1032221: cryp... Guilhem Moulin
- Bug#1032221: cryp... Bastian Germann
- Bug#1032221: cryp... Guillem Jover
- Bug#1032221: cryptsetup: libgcc_s.so.1 mus... Daniel Leidert
- Bug#1032221: Bug#1014110: libargon2 0~2019... Guilhem Moulin
- Processed: Re: Bug#1014110: libargon2 0~20... Debian Bug Tracking System
- Bug#1032221: marked as done (cryptsetup: l... Debian Bug Tracking System
- Bug#1032235: Bug#1014110: libargon2 0~2019... Bastian Germann
- Processed: Re: [pkg-cryptsetup-devel] Bug#... Debian Bug Tracking System
- Processed (with 1 error): Re: Bug#1032221:... Debian Bug Tracking System
- Bug#1032235: closing 1032235 Guilhem Moulin
- Processed: closing 1032235 Debian Bug Tracking System