Re: Requirements for testing phase of duplicity
Scott Hannahs via Duplicity-talk <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <[email protected]> |
Ken, Thanks for info. I have also been using a very old copy of librsync since I first started using duplicity. Is there a versioning issue with more recent versions or is it seamless compatibility? The current version seems to be V2.3.4. https://github.com/librsync/librsync/releases/tag/v2.3.4 -Scott > On Feb 16, 2025, at 7:37 PM, Scott Hannahs <[email protected]> wrote: > > I understand that pip is great for you python dudes, but I am writing a fink package that is multi-lingual and thus am trying to replicate that so I need the internals of the packaging. > > is it black==24.8 or black >= 24.8 the current version is 25.1.0 > > > >> On Feb 16, 2025, at 3:40 PM, Kenneth Loafman <[email protected]> wrote: >> >> Yes, rdifff, pylint, and black==24.8 are needed. >> >> pylint and black may be avoided by just running "pytest testing/unit testing/functional" from the root directory. >> >> As I said, before, use pip to install requirements.*. >> >> ...Ken >> >> >> On Sun, Feb 16, 2025 at 12:05 PM Scott Hannahs via Duplicity-talk <[email protected] <mailto:[email protected]>> wrote: >>> Just to verify that I am not doing a lot of extra work here….. >>> >>> I believe the the complete testing phase of installing duplicity now requires a separate installation of rdiff, pylint, and black? >>> >>> Is this true. I really do like testing a backup program installation completely. >>> >>> -Scott >>> >>> >>> _______________________________________________ >>> Duplicity-talk mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk > _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk