public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gwyn Ciesla <gwync@protonmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/duplicity] f45: 3.2.0
Date: Fri, 14 Aug 2026 19:19:49 GMT	[thread overview]
Message-ID: <178673518938.1.4314733688489532926.rpms-duplicity-bcf1d893292a@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/duplicity
Branch : f45
Commit : bcf1d893292a339e84ad3b622a0d4bf3ce1eb606
Author : Gwyn Ciesla <gwync@protonmail.com>
Date   : 2026-08-14T14:19:15-05:00
Stats  : +18/-4 in 4 file(s)
URL    : https://src.fedoraproject.org/rpms/duplicity/c/bcf1d893292a339e84ad3b622a0d4bf3ce1eb606?branch=f45

Log:
3.2.0

---
diff --git a/.gitignore b/.gitignore
index c3013ed..4230db3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -70,3 +70,4 @@
 /duplicity-rel.3.0.6.tar.bz2
 /duplicity-rel.3.0.7.tar.bz2
 /duplicity-rel.3.1.0.tar.bz2
+/duplicity-rel.3.2.0.tar.bz2

diff --git a/duplicity.spec b/duplicity.spec
index 21fb37a..9f48092 100644
--- a/duplicity.spec
+++ b/duplicity.spec
@@ -1,7 +1,7 @@
 %bcond_without check
 
 Name:           duplicity
-Version:        3.1.0
+Version:        3.2.0
 Release:        %autorelease
 Summary:        Encrypted bandwidth-efficient backup using rsync algorithm
 
@@ -24,9 +24,10 @@ URL:            https://duplicity.gitlab.io/
 Source0:        https://gitlab.com/duplicity/duplicity/-/archive/rel.%{version}/duplicity-rel.%{version}.tar.bz2
 # chg:test: Add test case for issue #683.
 # https://gitlab.com/duplicity/duplicity/-/commit/e6671cdf4ed8b21b4a8bd1973bd458f62792cd29
-Patch0:         e6671cdf4ed8b21b4a8bd1973bd458f62792cd29.patch
+#Patch0:         e6671cdf4ed8b21b4a8bd1973bd458f62792cd29.patch
 # Unpin the upper Python bound
-Patch:          allow-python3.15-build.patch
+#Patch:          allow-python3.15-build.patch
+Patch:          pytest9.patch
 
 Requires:       ca-certificates
 Requires:       gnupg >= 1.0.6
@@ -46,6 +47,8 @@ BuildRequires:  python3-devel
 BuildRequires:  pyproject-rpm-macros
 BuildRequires:  librsync-devel >= 0.9.6
 BuildRequires:  python3dist(wheel)
+BuildRequires:  python3dist(pip)
+BuildRequires:  python3dist(build)
 # dependencies for check
 BuildRequires:  gnupg >= 1.0.6
 BuildRequires:  python3dist(setuptools-scm)

diff --git a/pytest9.patch b/pytest9.patch
new file mode 100644
index 0000000..c30af66
--- /dev/null
+++ b/pytest9.patch
@@ -0,0 +1,10 @@
+--- duplicity-rel.3.2.0/pyproject.toml~	2026-08-11 15:50:45.645602462 -0500
++++ duplicity-rel.3.2.0/pyproject.toml	2026-08-14 13:06:08.951845103 -0500
+@@ -196,7 +196,6 @@
+     "--capture=fd",
+     "--disable-warnings",
+     "--failed-first",
+-    "--numprocesses=auto",
+     "--showlocals",
+     "--verbose",
+ ]

diff --git a/sources b/sources
index 96a6f91..20cfeab 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (duplicity-rel.3.1.0.tar.bz2) = 5515c1ab8c67e6b0837a20b05ade7d7361711b2ed19600c38096880f957559af8a09a7f4dd1e352a3d411e759393a119ec9ef56278d7cadd74fa877d1873798c
+SHA512 (duplicity-rel.3.2.0.tar.bz2) = 0ce5f0cfee7b97b4c01610e43cc506edc6af7351b7d8fceb5d54fc01aa0b330dc0023c5dc1494e75f41f7af2cc4f5286ea376ddfe55c59a7e85ebe10803949a5

                 reply	other threads:[~2026-08-14 19:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178673518938.1.4314733688489532926.rpms-duplicity-bcf1d893292a@fedoraproject.org \
    --to=gwync@protonmail.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox