unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Cayetano Santos <csantosb@inventati.org>
Cc: 49979-done@debbugs.gnu.org
Subject: bug#49979: Duplicity BackendException: No module named 'paramiko'
Date: Wed, 11 Aug 2021 12:25:17 -0400	[thread overview]
Message-ID: <YRP57QxC1nQcNFmO@jasmine.lan> (raw)
In-Reply-To: <yu1wnosmhv7.fsf@inventati.org>

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@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@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




  reply	other threads:[~2021-08-11 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 10:15 bug#49979: Duplicity BackendException: No module named 'paramiko' Cayetano Santos
2021-08-10 22:28 ` Leo Famulari
2021-08-11  9:49   ` Cayetano Santos
2021-08-11 16:25     ` Leo Famulari [this message]
2021-08-11 18:22       ` Cayetano Santos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YRP57QxC1nQcNFmO@jasmine.lan \
    --to=leo@famulari.name \
    --cc=49979-done@debbugs.gnu.org \
    --cc=csantosb@inventati.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).