Re: Duplicity 3.1.0 Released
Scott Hannahs via Duplicity-talk <[email protected]> Tue, 7 Jul 2026 18:56:19 -0400
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <[email protected]> |
--===============6201133661681526698== Content-Type: multipart/alternative; boundary="Apple-Mail=_2F8599D0-D40F-45F0-99E2-C0F2AA57E028" --Apple-Mail=_2F8599D0-D40F-45F0-99E2-C0F2AA57E028 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 So which versions of gpg will this patch work with? I can adjust the = requirements to suit. I currently have gpg 2.5.21 installed. -Scott > On Jul 1, 2026, at 8:20=E2=80=AFAM, Kenneth Loafman = <[email protected]> wrote: >=20 > It turns out that gpg has changed the way it handles key usage, so = failure or success would end up dependent upon what gpg version you were = running. Originally the encrypt key we were using doubled as a sign key = and that worked until now. I had to use 'gpg --edit-key = 839E6A2856538CCF` to also allow encryption as well as signing. It was = not a lack of password but a lack of usage flag in the key. I took out = the restriction on Docker as well. >=20 > I've attached a gzipped patch to provide the changes. >=20 > ...Thanks, > ...Ken >=20 >=20 >=20 > On Wed, Jul 1, 2026 at 6:03=E2=80=AFAM Kenneth Loafman = <[email protected] <mailto:[email protected]>> wrote: >> Interesting that it would fail now. It ran on Linux, macOS, and = GitLab CI before the release. >>=20 >> I'll look into it. >>=20 >> ...Ken >>=20 >>=20 >>=20 >> On Mon, Jun 29, 2026 at 5:03=E2=80=AFPM Sam James via Duplicity-talk = <[email protected] <mailto:[email protected]>> wrote: >>> Scott Hannahs via Duplicity-talk <[email protected] = <mailto:[email protected]>> writes: >>>=20 >>> > Thanks for the update. Trying to adjust my fink-project build = system for this. I get a couple of failures when running >>> > the suite of tests. I know the pylint and the black tests are not = necessary but I dislike failures in my output. Put it >>> > down to programmer OCD. I am sure the tests all passed on your = system before you released it, but I am curious what is >>> > different on my system that all but these 3 tests would pass. I = am using python 3.10 and pylint 2.14.5. Now updating >>> > pylint (and astroid) to current version. >>> > >>> > [...] >>> > >>> > 3. This is further on a specific test for a code regression number = 908. I am including the long log here because I am >>> > not sure what is relevant. >>> > >>> > = testing/functional/test_regression.py::RegressionTest::test_issue908 >>> > FAILED [ 72%] >>>=20 >>> I'm seeing this as well (https://bugs.gentoo.org/978226) but not = figured >>> out why yet. I'll note that it's skipped in CI (the "Won't work on >>> docker") thing but I'm not sure why, as it seems like it should be = OK in >>> Docker too. In any case, it's not just you, just I didn't have = enough >>> info to report it yet. >>>=20 >>> > =E2=80=94=E2=80=94 >>> > _________________________ RegressionTest.test_issue908 = _________________________ >>> > >>> > self =3D <testing.functional.test_regression.RegressionTest = testMethod=3Dtest_issue908> >>> > >>> > @unittest.skipIf(os.path.exists("/.dockerenv"), "Won't work = on docker") >>> > [...] >>>=20 >>> sam >>> _______________________________________________ >>> Duplicity-talk mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk > <fix_test__Fix_test_issue908_issues_.patch.gz> --Apple-Mail=_2F8599D0-D40F-45F0-99E2-C0F2AA57E028 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">So which versions of gpg will this patch = work with? I can adjust the requirements to suit. I = currently have gpg 2.5.21 = installed.<div><br></div><div>-Scott<br><div><br = id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote = type=3D"cite"><div>On Jul 1, 2026, at 8:20=E2=80=AFAM, Kenneth Loafman = <[email protected]> wrote:</div><br = class=3D"Apple-interchange-newline"><div><div dir=3D"ltr">It turns out = that gpg has changed the way it handles key usage, so failure or success = would end up dependent upon what gpg version you were = running. <span = style=3D"background-color:transparent">Originally the encrypt key we = were using doubled as a sign key and that worked until now. I had = to use 'gpg --edit-key 839E6A2856538CCF` to also allow encryption as = well as signing. It was not a lack of password but a lack of usage = flag in the key. </span><span = style=3D"background-color:transparent">I took out the restriction on = Docker as well.</span><div><br></div><div>I've attached a gzipped patch = to provide the = changes.</div><div><br></div><div>...Thanks,</div><div>...Ken</div><div><b= r></div><div><br></div></div><br><div class=3D"gmail_quote = gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul = 1, 2026 at 6:03=E2=80=AFAM Kenneth Loafman <<a = href=3D"mailto:[email protected]">[email protected]</a>> = wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left:1px solid = rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Interesting that it = would fail now. It ran on Linux, macOS, and GitLab CI before the = release.<div><br></div><div>I'll look into = it.<br><div><br></div><div>...Ken<br><div><br></div><div><br></div></div><= /div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Mon, Jun 29, 2026 at 5:03=E2=80=AFPM Sam James = via Duplicity-talk <<a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>> = wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left:1px solid = rgb(204,204,204);padding-left:1ex">Scott Hannahs via Duplicity-talk = <<a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>> writes:<br> <br> > Thanks for the update. Trying to adjust my fink-project build = system for this. I get a couple of failures when running<br> > the suite of tests. I know the pylint and the black tests are = not necessary but I dislike failures in my output. Put it<br> > down to programmer OCD. I am sure the tests all passed on = your system before you released it, but I am curious what is<br> > different on my system that all but these 3 tests would pass. = I am using python 3.10 and pylint 2.14.5. Now updating<br> > pylint (and astroid) to current version.<br> ><br> > [...]<br> ><br> > 3. This is further on a specific test for a code regression number = 908. I am including the long log here because I am<br> > not sure what is relevant.<br> ><br> > = testing/functional/test_regression.py::RegressionTest::test_issue908<br> > FAILED [ 72%]<br> <br> I'm seeing this as well (<a href=3D"https://bugs.gentoo.org/978226" = rel=3D"noreferrer" target=3D"_blank">https://bugs.gentoo.org/978226</a>) = but not figured<br> out why yet. I'll note that it's skipped in CI (the "Won't work on<br> docker") thing but I'm not sure why, as it seems like it should be OK = in<br> Docker too. In any case, it's not just you, just I didn't have = enough<br> info to report it yet.<br> <br> > =E2=80=94=E2=80=94<br> > _________________________ RegressionTest.test_issue908 = _________________________<br> ><br> > self =3D = <testing.functional.test_regression.RegressionTest = testMethod=3Dtest_issue908><br> ><br> > @unittest.skipIf(os.path.exists("/.dockerenv"), = "Won't work on docker")<br> > [...]<br> <br> sam<br> _______________________________________________<br> Duplicity-talk mailing list<br> <a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a><br> <a href=3D"https://lists.nongnu.org/mailman/listinfo/duplicity-talk" = rel=3D"noreferrer" = target=3D"_blank">https://lists.nongnu.org/mailman/listinfo/duplicity-talk= </a><br> </blockquote></div> </blockquote></div> <span = id=3D"cid:f_mr21hs6p0"><fix_test__Fix_test_issue908_issues_.patch.gz>= ;</span></div></blockquote></div><br></div></div></body></html>= --Apple-Mail=_2F8599D0-D40F-45F0-99E2-C0F2AA57E028-- --===============6201133661681526698== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRHVwbGljaXR5 LXRhbGsgbWFpbGluZyBsaXN0CkR1cGxpY2l0eS10YWxrQG5vbmdudS5vcmcKaHR0cHM6Ly9saXN0 cy5ub25nbnUub3JnL21haWxtYW4vbGlzdGluZm8vZHVwbGljaXR5LXRhbGsK --===============6201133661681526698==--