duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Duplicity 1.0.1 Released


From: Kenneth Loafman
Subject: Re: [Duplicity-talk] Duplicity 1.0.1 Released
Date: Tue, 18 Oct 2022 16:32:35 -0500

Scott,

If you run "tox -py38" it will automatically build the appropriate version for testing purposes and test it.  If it has problems building it will stop.  The shebang line is python3 and is the correct way to do it.  Manual builds are not needed at all.

...Ken

On Tue, Oct 18, 2022 at 3:39 PM Scott Hannahs <sth@p-hall.net> wrote:


On Oct 18, 2022, at 1:43 PM, Kenneth Loafman <kenneth@loafman.com> wrote:

What do you mean "They seem unable to load the _rsyncmodule."?  _librsync.*.so maybe?

that was just reading the back trace from the failure.  It all got fixed when I managed to use a single version of python.  I probably should have deleted the comment since it was fixed.  But the line “from . import _librsync” was failing.  Which is what led me down the wrong path.  See below.


...command: "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/bin/duplicity" "full" "/var/folders/6b/85yg9bp94rv55dzbdp78thp40000kr/T/testfiles/dir1" "file:///var/folders/6b/85yg9bp94rv55dzbdp78thp40000kr/T/testfiles/output" "--volsize" "1" "--skip-volume=1" "-v0" "--no-print-statistics" "--allow-source-mismatch" "--archive-dir=/var/folders/6b/85yg9bp94rv55dzbdp78thp40000kr/T/testfiles/cache" < /dev/null
...cwd: /private/var/folders/6b/85yg9bp94rv55dzbdp78thp40000kr/T
...output:
b'Traceback (most recent call last):'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/bin/duplicity", line 37, in <module>'
b'    from duplicity.dup_main import main'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/dup_main.py", line 50, in <module>'
b'    from duplicity import commandline'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/commandline.py", line 43, in <module>'
b'    from duplicity import backend'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/backend.py", line 44, in <module>'
b'    from duplicity import dup_temp'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/dup_temp.py", line 34, in <module>'
b'    from duplicity import path'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/path.py", line 49, in <module>'
b'    from duplicity import librsync'
b'  File "/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/librsync.py", line 36, in <module>'
b'    from . import _librsync'
b"ImportError: cannot import name '_librsync' from 'duplicity' (/opt/sw/src/fink.build/duplicity-1.0.1-1/duplicity-1.0.1/duplicity/__init__.py)"
...return_val: 1

Are you running tox to do the testing?
Yes.  I think I ended up building duplicity in python 3.9 and running tox in python 3.8.  Thus it could not find the correct libraries?  Now tox passed all the tests.  Mostly I needed to change the references from python3 to python3.8 in the executable.

-Scott



reply via email to

[Prev in Thread] Current Thread [Next in Thread]