| Yeah, I have the same CPAN issues as PyPi. That is one reason I like fink is that it does a source installation that is fairly easy to update and it isolates all its packages to a separate directory tree.
I agree that leading zero has been there for a long time. However, I would move to 1.0.0 in the next major release instead of jumping to 8.X.X which may confuse people about where all those intermediate versions were. There used to be feature list for versions back in launchpad? Has duplicity been moved to gitlab vs. launchpad these days?
Skip 0.9 and make this 1.0.0? Duplicity 0.9-series seriesThis series will feature the full transition from Python 2 to Python 3 native code, no python-future support.
-Scott
PyPI is to Python as CPAN is to Perl.
I personally avoid most distro packages and go straight to the source, but that's just me. My experience has been that the distro repo is way far behind what's needed for current software.
As to substantial upgrade, yes, but with duplicity it's almost as though the leading zero was not there. Been thinking about moving to 8.23.0 instead of 0.8.23 so I could have a point release.
...Ken
That is one of the issues with the fink package system, it predated pip and so one package manager will fight with the other. But it is fairly easy to write an installer for well behaved packages. I thought I had looked at boto3 and it was trying to use only standard installed packages. Have botocore all setup and just found that jmespath needs to be installed. I will also add s3transfer.
It does seem like a substantial upgrade for a point release!
-Scott
> On May 27, 2022, at 6:17 AM, edgar.soldin--- via Duplicity-talk <duplicity-talk@nongnu.org> wrote:
>
> hey Scott,
>
> boto3 says it needs botocore, jmespath, s3transfer
> https://github.com/boto/boto3/blob/1.23.9/requirements.txt
>
> not using fink i do not know how or if they are distributed by it. maybe you can try to get python pip running and use that for dependencies?
>
> good luck.. ede
>
>
> On 26.05.2022 17:13, Scott Hannahs via Duplicity-talk wrote:
>> I am still trying to get 0.8.23 running on Mac OS. I moved the dependency from boto to boto3 and it build and ran the local tests. BUT when I tried to use s3 it mentioned that botocore was missing?
>>
>> Maybe the changed syntax will fix this but I somehow doubt it. AFAICT I need to install botocore as separate from boto3?
>>
>> Note: I am using fink as my package manager for installing duplicity.
>>
>> -Scott
>>
>>> On May 26, 2022, at 02:21, Rinck Sonnenberg via Duplicity-talk <duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:
>>>
>>> Hi all,
>>>
>>> for those struggling with the changed S3 behavior in duplicity/boto3 regarding the --s3-endpoint-url, I thought I'd give an example. I took my some trial and error to figure out what needed to go where.
>>>
>>> So if previously (before 0.8.23) you were using a destination like:
>>> duplicity --s3-use-new-style --s3-european-buckets /mypath s3://s3.eu-west-1.amazonaws.com/my-bucket-name/ <http://s3.eu-west-1.amazonaws.com/my-bucket-name/>
>>>
>>> the new syntax (0.8.23+) should be something like:
>>> duplicity --s3-use-new-style --s3-european-buckets --s3-endpoint-url https://s3.eu-west-1.amazonaws.com/ <https://s3.eu-west-1.amazonaws.com/> /mypath s3://my-bucket-name/ <s3://my-bucket-name/>
>>>
>>> Hopefully that will save someone some headaches! :-)
>>>
>>> Regards,
>>> Rinck
>>>
>>>
>>>
>>> On Thu, Mar 24, 2022 at 4:55 PM Kenneth Loafman via Duplicity-talk <duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:
>>>
>>> We made the following changes and released them in *0.8.23.dev15* development version on GitLab, Launchpad PPA, Snapcraft (edge), and PyPi. If you use the release/stable version, please use this for planning purposes. *This will be part of 0.8.23 in a month or so.*
>>>
>>> Since some users use the dev version, here are the changes:
>>>
>>> * boto3 backend is now default s3:// backend. It does not support s3:/// <s3:///> but needs --s3-endpoint-url instead
>>> * boto3 supports --s3-unencrypted-connection option now
>>> * boto backend now usable via boto+s3:// or boto+gs:// only
>>> * boto's s3+http:// scheme was removed, use boto+s3:// instead
>>> * boto supports --s3-endpoint-url. --s3-use-deep-archive options now
>>> * changes are documented in man page
>>>
>>> I would suggest that if/when this breaks things, please consult the man page. There are a bunch of much needed updates that will see you through.
>>>
>>> ...Thanks,
>>> ...Ken
>>>
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk <https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> Duplicity-talk@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
|