Re: Duplicity 3.0.5 Released
Kenneth Loafman via Duplicity-talk <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <CAD-_Ma2xF_DmfeUBQtthn2WnFjMY4OP1q1=E4b0S5z0iDFonaw@mail.gmail.com> |
You would need to clone the "main" branch, or go to releases <https://gitlab.com/duplicity/duplicity/-/releases> and download from there, tar, zip, etc.. I stopped putting it in the pip stuff (sdist) because it more than doubled the size and was never used. ...Ken On Thu, Jul 10, 2025 at 10:54 AM Scott Hannahs via Duplicity-talk < [email protected]> wrote: > Ken, > > I load the tarball and build from that. Then optionally run the testing > phase which is more of a package maintainer’s process to make sure that the > build is a completley functional package. If the tests are still there in > the tarball which should be the same as the repository clone? Then I can > run pytest then I am fine. > > This is my test script: > > TestScript: << > > #!/bin/sh -ev > > ulimit -n 8192 > > %p/bin/pytest-3.10 -p no:xdist -p no:hypothesis -p no:randomly > > << > > Testing has its own set of dependencies > > TestDepends: << > > pytest-py310, > > pytest-cov-py310, > > pytest-runner-py310, > > coverage-py310, > > pycodestyle-py310, > > pylint-py310 > > << > > And that has been working with little changes for a long while. But I > think I can switch to a repository clone. Is there a branch/tag for the > release rather than the working master? > > -Scott > > On Jul 10, 2025, at 05:05, Kenneth Loafman <[email protected]> wrote: > > Have you just tried cloning the repo then testing that? > > ...Ken > > > On Wed, Jul 9, 2025 at 8:29 PM Scott Hannahs <[email protected]> wrote: > >> >> >> On Jun 20, 2025, at 06:38, Kenneth Loafman via Duplicity-talk < >> [email protected]> wrote: >> >> Hello, >>> >>> PyPI tarball doesn't include /testing. Is there any plans to add it >>> again? >>> >>> Thanks >>> >>> No plans at this point. It was removed intentionally since most users >> do not use it at all. >> >> …Ken >> >> >> I have made the testing phase as part of the fink package manaager >> (macOS) script for awhile. It has caught some >> build/installation/dependency error. It is useful in testing an >> installation. >> > > _______________________________________________ > Duplicity-talk mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/duplicity-talk > _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk