On Thu, Aug 27, 2020 at 10:50:42AM +0200, Lukas Puehringer wrote:
> in-toto 0.5.0-1 [1] and python-securesystemslib 0.16.0-1 [2] fix this issue.
> Any
> chance we can get these accepted before in-toto is autoremoved from testing on
> 2020-09-01?
yes, I plan to upload until then. sorry for the
in-toto 0.5.0-1 [1] and python-securesystemslib 0.16.0-1 [2] fix this issue. Any
chance we can get these accepted before in-toto is autoremoved from testing on
2020-09-01?
Cheers,
Lukas
[1] https://mentors.debian.net/package/in-toto/
[2]
FYI: We just bumped upstream to include the fix:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.16.0
Will prepare a downstream release later this week.
On 06.08.2020 2:21 PM, Holger Levsen wrote:
> hey Lukas,
>
> On Thu, Aug 06, 2020 at 02:03:00PM +0200, Lukas
hey Lukas,
On Thu, Aug 06, 2020 at 02:03:00PM +0200, Lukas Puehringer wrote:
> FYI: https://github.com/secure-systems-lab/securesystemslib/pull/264 fixes the
> issue upstream.
nice. once it's released we should get this new version into unstable!
--
cheers,
Holger
FYI: https://github.com/secure-systems-lab/securesystemslib/pull/264 fixes the
issue upstream.
On 04.08.2020 3:11 PM, Lukas Puehringer wrote:
> Thanks for the report!
>
> It looks like a recent update to pyca/cryptography v3.0 causes our test code
> (only) to break. I just filed an issue
Thanks for the report!
It looks like a recent update to pyca/cryptography v3.0 causes our test code
(only) to break. I just filed an issue upstream, because I am not fully sure if
the change was made intentionally:
https://github.com/pyca/cryptography/issues/5373
If it was, I will update our
6 matches
Mail list logo
