From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] isync: update to 1.4.0
Date: Sat, 10 Apr 2021 13:20:49 +0200 [thread overview]
Message-ID: <20210410112049.Qdj1oNzkE2MaKcgjr_ZHKKbz8Iywo32SciOTNT2iVWU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28540@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
There is an updated pull request by paper42 against master on the void-packages repository
https://github.com/paper42/void-packages 0001-isync-update-to-1.4.0.patch
https://github.com/void-linux/void-packages/pull/28540
isync: update to 1.4.0
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
ping @leahneukirchen
A patch file from https://github.com/void-linux/void-packages/pull/28540.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-0001-isync-update-to-1.4.0.patch-28540.patch --]
[-- Type: text/x-diff, Size: 1294 bytes --]
From f50f791870da032848038372c89e3b0cae706ff5 Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Tue, 9 Mar 2021 16:16:31 +0000
Subject: [PATCH] isync: update to 1.4.1
---
srcpkgs/isync/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/isync/template b/srcpkgs/isync/template
index 003288d12030..f69f581a45dc 100644
--- a/srcpkgs/isync/template
+++ b/srcpkgs/isync/template
@@ -1,7 +1,7 @@
# Template file for 'isync'
pkgname=isync
-version=1.3.5
-revision=2
+version=1.4.1
+revision=1
build_style=gnu-configure
hostmakedepends="perl pkg-config"
makedepends="openssl-devel libsasl-devel db-devel zlib-devel"
@@ -10,11 +10,10 @@ short_desc="IMAP and MailDir mailbox synchronizer"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="GPL-2.0-or-later"
homepage="http://isync.sourceforge.net/"
+changelog="https://sourceforge.net/p/isync/isync/ci/master/tree/NEWS?format=raw"
distfiles="${SOURCEFORGE_SITE}/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=68f532e5dcd434b02b873d920323ebc9a8a7d87f119f7cc050365dc014cf7655
+checksum=0d36dbb57bb06c8bbe10bb66f40ae543095b143443209b7037167be600420150
post_install() {
vsconf src/mbsyncrc.sample
- vsconf src/compat/isyncrc.sample
- rm -rf ${DESTDIR}/usr/share/doc/isync
}
next prev parent reply other threads:[~2021-04-10 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 23:41 [PR PATCH] " paper42
2021-02-06 0:31 ` sgn
2021-02-06 10:58 ` paper42
2021-02-09 4:10 ` ahesford
2021-02-09 4:10 ` ahesford
2021-04-10 11:20 ` paper42 [this message]
2021-05-21 9:08 ` isync: update to 1.4.1 Eluminae
2021-05-21 14:19 ` [PR PATCH] [Closed]: " leahneukirchen
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=20210410112049.Qdj1oNzkE2MaKcgjr_ZHKKbz8Iywo32SciOTNT2iVWU@z \
--to=paper42@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).