From: ndowens <ndowens@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] duplicity: update to 0.8.17
Date: Sun, 15 Nov 2020 00:04:36 +0100 [thread overview]
Message-ID: <20201114230436.VdCnEmf8ZgL4vF8O9HL2D-bPxT8ML7eOIAxArpdIhDY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26369@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
There is an updated pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages duplicity
https://github.com/void-linux/void-packages/pull/26369
duplicity: update to 0.8.17
A patch file from https://github.com/void-linux/void-packages/pull/26369.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-duplicity-26369.patch --]
[-- Type: text/x-diff, Size: 1405 bytes --]
From 6c34713e9347ed43f4e4f7cb77c9f53b99640dc1 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens@artixlinux.org>
Date: Fri, 13 Nov 2020 23:48:40 -0600
Subject: [PATCH] duplicity: update to 0.8.17
[ci skip]
---
srcpkgs/duplicity/template | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/srcpkgs/duplicity/template b/srcpkgs/duplicity/template
index ff421ea456f..22bec8d95ba 100644
--- a/srcpkgs/duplicity/template
+++ b/srcpkgs/duplicity/template
@@ -1,7 +1,7 @@
# Template file for 'duplicity'
pkgname=duplicity
-version=0.8.16
-revision=2
+version=0.8.17
+revision=1
build_style=python3-module
hostmakedepends="gettext python3-setuptools"
makedepends="python3-devel librsync-devel"
@@ -12,19 +12,13 @@ license="GPL-2.0-or-later"
homepage="http://duplicity.nongnu.org/"
changelog="http://duplicity.nongnu.org/vers8/CHANGELOG"
distfiles="http://launchpad.net/duplicity/${version%.*}-series/${version}/+download/duplicity-${version}.tar.gz"
-checksum=2cfcd212834979751310d9df1a954b949f86b084efd5ad1f97dd744780ef9d1b
+checksum=a273b1e74d8d0b7825572f51be9c8284e579961e01f4fc1473048e95dce49984
post_extract() {
chmod 0644 bin/*.1
}
-do_check() {
- # Disable as tests don't work
- # tests look for pytest,instead of pytest{2,3}
- :
-}
-
post_install() {
- # drop doc
- rm -rf ${DESTDIR}/usr/share/doc
+ # Remove docs
+ rm -r ${DESTDIR}/usr/share/doc
}
next prev parent reply other threads:[~2020-11-14 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 5:49 [PR PATCH] " ndowens
2020-11-14 5:50 ` [PR PATCH] [Closed]: " ndowens
2020-11-14 21:43 ` [PR REVIEW] " ahesford
2020-11-14 22:25 ` [PR PATCH] [Updated] " ndowens
2020-11-14 23:01 ` [PR REVIEW] " ericonr
2020-11-14 23:04 ` ndowens
2020-11-14 23:04 ` ndowens [this message]
2020-11-14 23:05 ` ndowens
2020-11-14 23:06 ` ericonr
2020-11-14 23:06 ` ericonr
2020-11-14 23:43 ` ndowens
2020-11-15 0:32 ` ndowens
2020-11-15 1:55 ` [PR PATCH] [Updated] " ndowens
2020-11-15 1:56 ` [PR PATCH] [Closed]: " ndowens
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=20201114230436.VdCnEmf8ZgL4vF8O9HL2D-bPxT8ML7eOIAxArpdIhDY@z \
--to=ndowens@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).