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



>mer. 11 août 2021 at 00:28, Leo Famulari ...

> On Tue, Aug 10, 2021 at 12:15:44PM +0200, Cayetano Santos wrote:
>>
>> 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.
>
> I don't use Duplicity. Can you give instructions to reproduce 
> this?
>
> It's likely that paramiko needs to be added as a dependency of 
> the
> duplicity package, but we should test that first.

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.




  reply	other threads:[~2021-08-11 12:06 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 [this message]
2021-08-11 16:25     ` Leo Famulari
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=yu1wnosmhv7.fsf@inventati.org \
    --to=csantosb@inventati.org \
    --cc=49979@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).