Re: [Duplicity-team] [Duplicity-talk] Duplicity 1.0.1 Released

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

Re: [Duplicity-team] [Duplicity-talk] Duplicity 1.0.1 Released

What do you mean "*They seem unable to load the _rsyncmodule.*"? _librsync.*.so maybe? Are you running *tox* to do the testing? ...Ken On Tue, Oct 18, 2022 at 12:37 PM Scott Hannahs wrote: > Ken, > > I am sure I am confused! Thanks for the pointers setting me straight. > > But your comment

Re: [Duplicity-team] [Duplicity-talk] Duplicity 1.0.1 Released

Scott, I think you are confused. When I refer to *_librsync.so* it is really *_librsync.cpython-39-darwin.so * that I'm referring to. The middle part will change depending on which python and its version it's compiled against. And no, _librsyncmodule.o is

Re: [Duplicity-team] [Duplicity-talk] Duplicity 1.0.1 Released

hey Scott, reads like Fink is way behind current macOS-Development https://www.finkproject.org/download/index.php?phpLang=en are they officially supporting macOS 11+ ? homebrew seems to be more up to speed, so maybe you can connect them on github

Re: [Duplicity-team] [Duplicity-talk] Duplicity 1.0.1 Released

Hi Scott, I would say that all your errors are from not being able to build *_librsync.so* properly. There is one thing that may help in lines 65-76 of *setup.py*. You can supply *LIBRSYNC_DIR* as an env variable, or on the command line as *--librsync-dir=*. I have *export