FS#76307 - [duplicity] does not report version correctly after update to 1.0.1

Attached to Project: Community Packages
Opened by Chris Lea (chrislea) - Thursday, 27 October 2022, 02:30 GMT
Last edited by George Rawlinson (rawlinsong) - Saturday, 13 May 2023, 07:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To George Rawlinson (rawlinsong)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Additional info:
* package version(s): 1.0.1
* config and/or log files etc.: N/A
* link to upstream bug report, if any: N/A

Steps to reproduce:

Duplicity updated to version 1.0.1 today via a standard pacman -Syu.

Expected output:

```
[chl@idril ~]$ duplicity --version
duplicity 1.0.1
```

Actual output:

```
[chl@idril ~]$ duplicity --version
duplicity $version
```

This does not happen if I install duplicity via pip directly. The version not being reported breaks deja-dup backups on Gnome (screenshot attached).
   Screenshot from 2022-10-26 19... (18.2 KiB)
This task depends upon

Closed by  George Rawlinson (rawlinsong)
Saturday, 13 May 2023, 07:51 GMT
Reason for closing:  Fixed
Comment by Chris Lea (chrislea) - Thursday, 27 October 2022, 02:33 GMT
Apologies, I was looking at the wrong source repository. This **does** happen when you build sources from https://gitlab.com/duplicity/duplicity
Comment by Chris Lea (chrislea) - Thursday, 27 October 2022, 03:07 GMT
I have opened a ticket with the upstream project: https://gitlab.com/duplicity/duplicity/-/issues/150
Comment by George Rawlinson (rawlinsong) - Thursday, 27 October 2022, 04:11 GMT
I can confirm this issue, thanks for bringing it to our attention.

Upstream has a non-standard build process, so I'll leave this open until upstream have responded.

I'll push a quickfix to the repos soon.
Comment by Chris Lea (chrislea) - Thursday, 27 October 2022, 15:34 GMT
Upstream has provided a response: https://gitlab.com/duplicity/duplicity/-/issues/150#note_1151056577

It looks like you now need to clone a specific branch/tag, run a setup.py command to create a versioned tarball, and then use that tarball to build the package from. Sorry, I wish I had better news. :-/
Comment by Chris Lea (chrislea) - Thursday, 27 October 2022, 16:25 GMT
The attached PKGBUILD skips checksum or signature checking (apologies, I'm not sure how to do that since I don't know if they have signed commits), but it does produce a working package for me. This may be garbage but posting in case any of it is perhaps helpful for you.
   PKGBUILD (1.4 KiB)

Loading...