0.8.21: hubic backend still broken

[az]

this is a forward of debian bug 1002675, which lives over there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002675

the submitter reports that, while the baseidentity gotcha is gone,
the hubic backend now fails with

Connection failed, please check your credentials: TypeError __init__()
got an unexpected keyword argument 'username'

[Kenneth Loafman (kenneth-loafman)]

1) I'm certain the 'username' keyword comes from the pyrax code itself, not duplicity. Would need a complete -v9 log file to chase down where, however,

2) From the pypi.or site: "DEPRECATED: Pyrax is no longer being developed or supported. See openstacksdk and the rackspacesdk plugin in order to interact with Rackspace’s OpenStack-based public cloud.", plus,

3) given your comment: "i'll forward your new bug report upstream, but don't hold your breath:
the hubic service seems to be mostly if not quite entirely dead for
multiple years now, so interest in supporting that is not likely to be high."

I'm putting this down as an incomplete, low priority, bug.

[fab (fab128)]

Dear all,

I'll be more than happy to solve this bug by myself, provided that I
knew how to get the relevant informations, i.e. the file and the line
number where the error comes from.

Unfortunately, the duplicity -v9 command does not give me what I am
expecting (see output below).

What am I doing wrong ?

Thanks in advance for your help.

Output of duplicity -v9:

GPG binary is gpg, version (2, 2, 27)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.boxbackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.gdrivebackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.idrivedbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.megav2backend Succeeded
Import of duplicity.backends.megav3backend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rclonebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.s3_boto3_backend Succeeded
Import of duplicity.backends.s3_boto_backend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Connection failed, please check your credentials: TypeError a bytes-like
object is required, not 'str'

Le 30/12/2021 à 06:10, Alexander Zangerl a écrit :
> fabrice, upstream has reported that the problem you're encountering
> is pretty much certainly not coming from duplicity but pyrax - which is
> deprecated and no longer being maintained.
>
> upstream requests the log of a duplicity run with full -v9 logging/debugging
> on in order to track this down any further. if you can provide such a log
> the chances of getting this sorted out will rise a bit.
>
> regards
> az
>
>

[Launchpad Janitor (janitor)]

[Expired for Duplicity because there has been no activity for 60 days.]