Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#857278: python-nacl: sodium_init() fails because already initialized.

10 views
Skip to first unread message

Rahul De

unread,
Mar 9, 2017, 8:30:04 AM3/9/17
to
Package: python-nacl
Version: 1.0.1-2
Severity: important
Tags: upstream

Dear Maintainer,

The call to sodium_init() fails because already initialized.

This has been referenced in the upstream repo at https://github.com/pyca/pynacl/issues/186.
The patch for this is also available in https://github.com/pyca/pynacl/pull/199 and has been
merged too. I have requsted the upstream on https://github.com/pyca/pynacl/issues/265 to
do a newer release. Although a large number of commits have been done since but a new
release hasn't been done having this patch.

I was trying to install the matrix-synapse package which depends on this. matrix-synapse
fails to start due to this problem.

If a new release isn't available please consider releasing directly from the latest git.

Thanks.


-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-nacl depends on:
ii libc6 2.24-3
ii libsodium18 1.0.11-1
ii python 2.7.11-2
ii python-cffi 1.9.1-2
pn python-cffi-backend-api-max <none>
pn python-cffi-backend-api-min <none>
ii python-six 1.10.0-3
pn python:any <none>

python-nacl recommends no packages.

Versions of packages python-nacl suggests:
pn python-nacl-doc <none>

-- no debconf information

rah...@swecha.net

unread,
Mar 15, 2017, 1:40:02 AM3/15/17
to
This patch is no longer required now as this issue has been fixed with
the new release 1.1.0 in upstream.
Also this includes quite a few new features and doing a new release for
Debian will greatly help.

Tristan Seligmann

unread,
Mar 15, 2017, 6:10:03 AM3/15/17
to
On Wed, 15 Mar 2017 at 07:39 <rah...@swecha.net> wrote:
This patch is no longer required now as this issue has been fixed with
the new release 1.1.0 in upstream.

Thanks for tracking / following up on this issue; I have been paying attention despite the silence from my side, and it is appreciated :) 

I'm planning to look at uploading the new release in the next few days; should be by the end of the weekend at the latest.
0 new messages