GNU bug report logs - #49979
Duplicity BackendException: No module named 'paramiko'

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Leo Famulari <leo <at> famulari.name>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#49979: closed (Duplicity BackendException: No module named
 'paramiko')
Date: Wed, 11 Aug 2021 16:26:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 11 Aug 2021 12:25:17 -0400
with message-id <YRP57QxC1nQcNFmO <at> jasmine.lan>
and subject line Re: bug#49979: Duplicity BackendException: No module named 'paramiko'
has caused the debbugs.gnu.org bug report #49979,
regarding Duplicity BackendException: No module named 'paramiko'
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
49979: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=49979
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Cayetano Santos <cayetano.santos <at> inventati.org>
To: bug-guix <at> gnu.org
Subject: Duplicity BackendException: No module named 'paramiko'
Date: Tue, 10 Aug 2021 12:15:44 +0200

Context:

Using guix as a package manager under a foreign up to date 
archlinux distribution.

The output of guix describe --format=channels is

   https://gitlab.com/csantosb/wikidata/-/blob/master/guix-profiles-backup/guix-channels.scm


Problem:

When using duplicity to backup to a sftp server, I get this error 
message

   BackendException: Could not initialize backend: No module 
   named 'paramiko'

I have installed python-paramiko, but this doesn't fixes the 
problem.

[Message part 3 (message/rfc822, inline)]

From: Leo Famulari <leo <at> famulari.name>
To: Cayetano Santos <csantosb <at> inventati.org>
Cc: 49979-done <at> debbugs.gnu.org
Subject: Re: bug#49979: Duplicity BackendException: No module named 'paramiko'
Date: Wed, 11 Aug 2021 12:25:17 -0400

On Wed, Aug 11, 2021 at 11:49:01AM +0200, Cayetano Santos wrote:
> Sure. Just issue a
> 
>    guix install duplicity
> 
> and then
> 
>    duplicity /tmp sftp://dummy_user <at> sftp.server/dummy_backup
> 
> you’ll get a
> 
> BackendException: Could not initialize backend: No module named 'paramiko'

> message.

Thanks! I tested by adding python-paramiko to native-inputs [0], changed
the dummy values to something meaningful, and tried your command:

------
$ duplicity /tmp sftp://leo <at> domain/dummy_backup 
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
GnuPG passphrase for decryption: %    
------

I didn't go past that point but it seems to fix the specific bug you
reported. So, I pushed the change:

https://git.savannah.gnu.org/cgit/guix.git/commit/?id=b1c97ff60b8ac8205d878fec3af8d02ffdf601fe

You can do `guix pull --commit=b1c97ff60b8 && guix package --upgrade=duplicity`
to get the new version of the package.

[0] It's unusual for run-time dependencies like paramiko to be a
native-input. Typically, native-inputs are just build-time dependencies.
Maybe there is some room for improvement in our Duplicity package...

https://guix.gnu.org/manual/en/html_node/package-Reference.html

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.