Bug#969565: Bogus upper bound

2020-09-09 Thread Luca Boccassi
On Mon, 7 Sep 2020 09:41:28 +0200 Tristan Seligmann wrote: > I think the upper bound is just bogus and should be removed. Upstream > seems to have added it under the assumption that cryptography follows > semver, but it does not: 2.9 to 3.0 offers the same compatibility > guarantees as 2.8 to 2.9

Bug#969565: Bogus upper bound

2020-09-07 Thread Tristan Seligmann
I think the upper bound is just bogus and should be removed. Upstream seems to have added it under the assumption that cryptography follows semver, but it does not: 2.9 to 3.0 offers the same compatibility guarantees as 2.8 to 2.9.