Re: [Duplicity-talk] Warnings from duplicity on package versions

[Kenneth Loafman]

Hi Scott,

What you are getting is normal for the number of packages we include and the version restrictions on them (some are range restrictions).  I did some work to minimize the noise, but it's impossible to remove all warnings without removing some backends.  It seems to work OK even with the warnings so I stopped trying.

One helpful and noisy tool is pipdeptree which will give you exactly what you need to trace dependencies.  Just ran it on a clean venv populated using requirements.txt and there's just a couple of complaints as below.  We've never had a complaint about novaclient and sphinx works as is, so I just let things be.  

...Ken

$ pipdeptree
Warning!!! Possibly conflicting dependencies found:
* python-novaclient==2.27.0
 - pbr [required: >=1.6,<2.0, installed: 5.11.1]
------------------------------------------------------------------------
Warning!! Cyclic dependencies found:
* sphinxcontrib-serializinghtml => Sphinx => sphinxcontrib-serializinghtml
* sphinx => sphinxcontrib-serializinghtml => Sphinx
------------------------------------------------------------------------
2to3==1.0

<snip long tree>

On Sat, Oct 14, 2023 at 11:52 AM Scott Hannahs via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

On Oct 13, 2023, at 11:37 AM, Scott Hannahs <sth@p-hall.net> wrote:

Since I am on MacOS and using the fink package manager, I will check the requirements.txt.  I don’t think I updated things since moved to duplicity version 2.1

FYI, here is my experience with dependencies.  I chose Python 3.10 as the version of python to use.  This is not the current system python which is 3.9.6 so I install a bunch of standard python tools for version 3.10.  This set of dependencies works and passes all tests but there may be some extra inclusions that are not needed.  This is certainly more than are in the “requirements.txt”.  Adding chardet to the top level solved the version conflicts I was having along with updating the version of requests.

Secondary dependencies are handled by the installers for those items and so are not included and these are only top level dependencies.

I currently have as dependencies on MacOS for running duplicity and install some of the backends:

Depends: <<

        python310,

        librsync-shlibs (>= 0.9.7-1002),

        gnupg2,

        setuptools-tng-py310,

        fasteners-py310,

        intltool40,

        paramiko-py310,

        pycrypto-py310,

        pexpect-py310,

        future-py310,

        chardet-py310,

        ncftp,

        lftp,

        par2,

        boto3-py310,

        requests-oauthlib-py310

<<

And to build duplicity:

BuildDepends: <<

        fink (>= 0.24.12-1),

        librsync (>= 0.9.7-1002)

gcc12

<<

For testing duplicity:

    TestDepends: <<

        pylint-py310,

        future-py310,

        librsync-bin,

        mock-py310,

        pluggy-py310,

        py-py310,

        tox-py310

<<

-Scott

_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk