On 12/05/2017 12:00 PM, Michał Górny wrote:
> Disable using secure memory for pygcrypt backend since we are not
> processing secrets. This can avoid the libgcrypt memory error; however,
> it turned out to be a huge memory/resource leak which needs to be fixed
> independently.
> ---
>
On Tue, 5 Dec 2017 18:08:47 +0100
Michał Górny wrote:
> Closes: https://bugs.gentoo.org/615620
> ---
> pym/portage/checksum.py | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/pym/portage/checksum.py b/pym/portage/checksum.py
> index
Closes: https://bugs.gentoo.org/615620
---
pym/portage/checksum.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/pym/portage/checksum.py b/pym/portage/checksum.py
index 5424ce56b..9e7bffea9 100644
--- a/pym/portage/checksum.py
+++ b/pym/portage/checksum.py
@@ -150,7
On Tue, 5 Dec 2017 08:42:43 -0800
Brian Dolbec wrote:
> On Tue, 5 Dec 2017 17:34:23 +0100
> Michał Górny wrote:
>
> > Closes: https://bugs.gentoo.org/615620
> > ---
> > pym/portage/checksum.py | 5 -
> > 1 file changed, 4 insertions(+), 1 deletion(-)
Closes: https://bugs.gentoo.org/615620
---
pym/portage/checksum.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/pym/portage/checksum.py b/pym/portage/checksum.py
index 5424ce56b..0841ab231 100644
--- a/pym/portage/checksum.py
+++ b/pym/portage/checksum.py
@@ -150,7