Bug 276865 - sysutils/duplicity: Update to 2.2.2 to fix arguments passed by sysutils/duply
Summary: sysutils/duplicity: Update to 2.2.2 to fix arguments passed by sysutils/duply
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Nuno Teixeira
URL:
Keywords:
Depends on: 272134
Blocks:
  Show dependency tree / graph
 
Reported: 2024-02-07 09:54 UTC by FiLiS
Modified: 2024-04-02 16:16 UTC (History)
2 users (show)

See Also:

Attachments
patch to upgrade port to version 2.2.2 (842 bytes, patch)
2024-02-07 09:54 UTC, FiLiS 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description FiLiS 2024-02-07 09:54:19 UTC 
Created attachment 248226 [details]
patch to upgrade port to version 2.2.2

There seems to be a new version of duplicity which unbreaks some duply functionality where duplicity complains about unneeded options passed to duplicity. 
https://duplicity.us/stable/CHANGELOG.html says

---
Fix
...
Invalid option error using `–[gpg|par2|rsync|ssh]-options ‘…’ [Kenneth Loafman]

https://gitlab.com/duplicity/duplicity/-/issues/795
---
Comment 1 Nuno Teixeira freebsd_committer freebsd_triage 2024-02-07 11:10:06 UTC 
[build-system]
requires = [
    ..
    "setuptools-scm>=8.0",
    ..
Waiting on update.
Comment 2 FiLiS 2024-02-07 11:35:01 UTC 
there's also a few more things I noticed. bin/duplicity was moved to duplicity/__main__.py, so SHEBANG_FILES needs changing, and patch-setup.py seems not to work anymore, I don't know if it is related to the setuptools-scm change as well.
Would be interesting, if it would also work with the devel/py-setuptools_scm7 port if you patch pyproject.toml
Comment 3 FiLiS 2024-02-29 10:49:55 UTC 
(In reply to Nuno Teixeira from comment #1)
the setuptools_scm port is now updated to 8.0.4
Comment 4 commit-hook freebsd_committer freebsd_triage 2024-02-29 11:05:00 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=85fdc9028d22ddb59eeb669ad2c5e6fd80e43664

commit 85fdc9028d22ddb59eeb669ad2c5e6fd80e43664
Author:     Nuno Teixeira <eduardo@FreeBSD.org>
AuthorDate: 2024-02-29 11:02:05 +0000
Commit:     Nuno Teixeira <eduardo@FreeBSD.org>
CommitDate: 2024-02-29 11:04:16 +0000

    sysutils/duplicity: Update to 2.2.2

    ChangeLog:      https://duplicity.gitlab.io/stable/CHANGELOG.html
    PR:             276865
    Reported by:    FiLiS <freebsdbugs@filis.org>

 sysutils/duplicity/Makefile             | 9 ++++-----
 sysutils/duplicity/distinfo             | 6 +++---
 sysutils/duplicity/files/patch-setup.py | 8 ++++----
 3 files changed, 11 insertions(+), 12 deletions(-)
Comment 5 Nuno Teixeira freebsd_committer freebsd_triage 2024-02-29 11:07:46 UTC 
testunit and basic backup/verify/restore operation works OK.

Please let me know how sysutils/duply is doing.
Comment 6 FiLiS 2024-02-29 16:31:16 UTC 
(In reply to Nuno Teixeira from comment #5)
looking good, thank you!
duplicity still chokes on a few unexpected duply commands (GPG_OPTS things), but that seems to rather be an issue for duply or duplicity itself, not port related.
I filed an issue (https://sourceforge.net/p/ftplicity/bugs/141/) with duply for now.
Comment 7 Nuno Teixeira freebsd_committer freebsd_triage 2024-04-02 16:16:37 UTC 
(In reply to FiLiS from comment #6)

Closing this one now.

Thanks