I attempted to integrate this into my fink building package for MacOS. However when running the test portion of the install as I had for previous versions, I got a massive number of failures. It seems that the test is using a command line argument that is changed/deleted? There is a massively long output log full of this message repeating the duplicity usage message. See below the signature.
2.2.1 and 2.2.1 should behave the same. Both test the CLI to make sure that options not valid for a command would create an error. Massive output. I'll try to suppress it.
I think this all worked for Duplicity 2.2.1 but something seems to have gone terribly awry. The test commands are:
%p/bin/python3.10 setup.py test
<<
Instead of 'setup.py test' use 'pytest' by itself. pyproject.toml has the pytest config defined, setup.py test does not. I should remove it completely.
Lots of changes like these are due to the rapid changes being made in PyPA (Python Packaging Authority). Sucks, but we have to live with it.
Let me know how it goes. I run everything here through pytest and it works correctly. Noisy but correct.
...Ken