Re: CentOS/Rocky 9 Installation Err - B2 and Duplicity

"edgar.soldin--- via Duplicity-talk" <[email protected]>
Newsgroups gmane.comp.sysutils.backup.duplicity.general
Message-ID <[email protected]>
On 15.02.2025 03:59, MRob via Duplicity-talk wrote:
>
>
>>> b2sdk 2.8.0
>>> b2 4.3.0
>>> duplicity 0.8.23
>>
>> this is a very outdated unmaintained version of duplicity. consider upgrading using python venv or the like.
>
> I see there is version 3.0.3.2 in pip?
> https://pypi.org/project/duplicity

yeah. it's supposed to be 3.0.4 . i informed Ken the maintainer. for your purpose 3.0.3.2 will be fine though.

> I try to first see about get new version of duplicity:
> pip install duplictiy
> ERROR: Could not find a version that satisfies the requirement duplictiy (from versions: none)
> ERROR: No matching distribution found for duplictiy

duplic*i*ty?

> Maybe i hav to use pipx?
> pip install pipx ---> success, but errors building duplicity because missing Python.h and librsync.h because hadnt installed *dev packages.
>
> dnf install python3-devel librsync-devel
> pipx install duplicity
> Now duplicity is working. Thank you

pipx (essentially pip with venvs) merely creates a python virtual environment for every app and installs it therein.

> A note about installation documentation: it say this is important, but its only error "no such option: --update"
> python3 -m pip install --update pip pipx

where did you find that? README says `--upgrade` for some time now
  https://gitlab.com/duplicity/duplicity/-/blob/dev/README.md?ref_type=heads#1-update-packaging-to-current-version

> Dunno if yuo care but I did install patch you gave below before I changed version. In case it is helpful:
>
>> if you are stuck with your ancient duplicity version you may apply this patch manually
>>  https://gitlab.com/duplicity/duplicity/-/merge_requests/250/diffs
>> and `duplicity -v9 ...` should output the issue for b2sdk failing to import.
>
> The file was bits different, there are 4 errs-- last one for import b2 instead of b2sdk. ANwayz, heres the trace it caused (sorry i didnt use -v9 so maybe not helpful. I can renstall duplicity from dnf if you want to have this feedbakc):
>
> Traceback (innermost last):
>    File "/usr/bin/duplicity", line 87, in <module>
>      with_tempdir(main)
>    File "/usr/bin/duplicity", line 70, in with_tempdir
>      fn()
>    File "/usr/lib64/python3.9/site-packages/duplicity/dup_main.py", line 1567, in main
>      action = commandline.ProcessCommandLine(sys.argv[1:])
>    File "/usr/lib64/python3.9/site-packages/duplicity/commandline.py", line 1244, in ProcessCommandLine
>      config.backend = backend.get_backend(args[0])
>    File "/usr/lib64/python3.9/site-packages/duplicity/backend.py", line 223, in get_backend
>      obj = get_backend_object(url_string)
>    File "/usr/lib64/python3.9/site-packages/duplicity/backend.py", line 209, in get_backend_object
>      return factory(pu)
>    File "/usr/lib64/python3.9/site-packages/duplicity/backends/par2backend.py", line 61, in __init__
>      self.wrapped_backend = backend.get_backend_object(parsed_url.url_string)
>    File "/usr/lib64/python3.9/site-packages/duplicity/backend.py", line 209, in get_backend_object
>      return factory(pu)
>    File "/usr/lib64/python3.9/site-packages/duplicity/backends/b2backend.py", line 83, in __init__
>      log.Debug("".join(traceback.format_exception(None, e1, e1.__traceback__)))
>   UnboundLocalError: local variable 'traceback' referenced before assignment
>
> My b2sdk is in
> /usr/local/lib/python3.9/site-packages/b2sdk

yeah, no. that is no use. looks like your patching was flawed and even if not the patch only prints debug output when verbosity is set to debug as well ;)

regardless, good to hear you got a recent duplicity running. that should help you along.

sunny regards from frosty germany ..ede/duply.net

_______________________________________________
Duplicity-talk mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.