This bug has been fixed in f9b5d595322c0f3463cdf6fb2cf168a259b738a9 which
will be released with 0.8,21.

fix:dev:Fixed Catch-22 in pyrax_identity.hubic.  Debian bug #996577

Name error on backend HubiC (Baseidentity).  Cannot avoid importing
pyrax since HubicIdentity requires pyrax.base_identity.BaseIdentity.

On Fri, Oct 15, 2021 at 1:06 PM BertrandB21 <dbbug.bertra...@dfgh.net>
wrote:

> Package: duplicity
> Version: 0.8.17-1+b1
> Severity: normal
>
> Dear Maintainer,
>
> Since the change of stable version i gopt an error on duplicty,
> I try wiht last version of pyrax
>
> the error :
> File
> "/usr/lib/python3/dist-packages/duplicity/backends/pyrax_identity/hubic.py",
> line 35, in <module>
>     class HubicIdentity(BaseIdentity):
>  NameError: name 'BaseIdentity' is not defined
>
> -- System Information:
> Debian Release: 11.1
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
> 'stable-security')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-9-amd64 (SMP w/1 CPU thread)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages duplicity depends on:
> ii  gnupg              2.2.27-2
> ii  libc6              2.31-13+deb11u2
> ii  librsync2          2.3.1-1
> ii  python3            3.9.2-3
> ii  python3-fasteners  0.14.1-2
> ii  python3-future     0.18.2-5
> ii  python3-lockfile   1:0.12.2-2.2
>
> Versions of packages duplicity recommends:
> ii  python3-oauthlib  3.1.0-2
> ii  python3-paramiko  2.7.2-1
> ii  python3-pexpect   4.8.0-2
> ii  python3-urllib3   1.26.5-1~exp1
> ii  rsync             3.2.3-4+deb11u1
>
> Versions of packages duplicity suggests:
> pn  lftp                 <none>
> pn  ncftp                <none>
> pn  par2                 <none>
> pn  python3-boto         <none>
> ii  python3-pip          20.3.4-4
> ii  python3-swiftclient  1:3.10.1-2
> pn  tahoe-lafs           <none>
>
> -- no debconf information
>
>

Reply via email to