Re: [Duplicity-talk] duplicity -V prints duplicity $version

[Kenneth Loafman]

I've seen this and will take care of it.

Just FYI, duplicity source is unversioned in a conventional meaning.  It is instead SCM versioned by the tags in the git repo.  A database guru once taught me a good lesson, "Duplicated data is not duplicate data!".  If you think about it, it's true for code versioning as well.  One source.

...Ken

On Mon, Mar 20, 2023 at 9:35 AM edgar.soldin--- via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

On 20.03.2023 15:31, Markus Schönhaber via Duplicity-talk wrote:
> Thanks for answering me so fast!

np

> 20.03.23, 15:11 +0100 edgar.soldin--- via Duplicity-talk:
>
>> on the other hand,
>>
>> version copying is done during distro creation. so maybe Ken just skipped the step when releasing the source builds?
>>
>> anyway. for now you may create the tar yourself as documented here
>>    https://gitlab.com/duplicity/duplicity/-/blob/main/README-REPO.md#getting-a-versioned-copy-of-duplicity
>
> Yes, that worked for me.

nice

>
>> On 20.03.2023 15:06, edgar.soldin@web.de wrote:
>
>>> nope, just replicated the issue. seems like setup is not patching/"VersionedCopy"-ing '__init.py__' anymore.
>>>
>>> would you mind opening an issue on https://gitlab.com/duplicity/duplicity/-/issues ?
>
> Do you still think that's necessary?
>

well, the release tar balls are faulty just now. but the maintainer Ken was in CC earlier so up to you. he should be informed ;)

..sunny regards ede

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