From: pascal-huber <pascal-huber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vdirsyncer: update to 0.19.1
Date: Wed, 01 Mar 2023 12:14:28 +0100 [thread overview]
Message-ID: <20230301111428.nKDImDXALYzLVT0kEtGJG4yzFOUJgS_wcBDHkWQrZ1g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42522@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
There is an updated pull request by pascal-huber against master on the void-packages repository
https://github.com/pascal-huber/void-packages vdirsyncer-0.19.1_1
https://github.com/void-linux/void-packages/pull/42522
vdirsyncer: update to 0.19.1
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
- x86_64-musl (crossbuild)
- aarch64 (crossbuild)
- armv7l (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/42522.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vdirsyncer-0.19.1_1-42522.patch --]
[-- Type: text/x-diff, Size: 1639 bytes --]
From c63b6364bcbd4d3c1ed40e47f9f096b157aeedaf Mon Sep 17 00:00:00 2001
From: Pascal Huber <pascal.huber@resolved.ch>
Date: Wed, 1 Mar 2023 11:50:22 +0100
Subject: [PATCH] vdirsyncer: update to 0.19.1
---
srcpkgs/vdirsyncer/template | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/vdirsyncer/template b/srcpkgs/vdirsyncer/template
index f5f6e2f57553..4a901585a5a6 100644
--- a/srcpkgs/vdirsyncer/template
+++ b/srcpkgs/vdirsyncer/template
@@ -1,23 +1,21 @@
# Template file for 'vdirsyncer'
pkgname=vdirsyncer
-version=0.19.0
+version=0.19.1
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools_scm"
depends="python3-atomicwrites python3-click python3-click-log python3-requests
python3-requests-toolbelt python3-aiohttp python3-aiostream"
checkdepends="python3-pytest-xdist python3-pytest-asyncio python3-trustme
- python3-aioresponses python3-pytest-httpserver python3-hypothesis $depends"
+ python3-aioresponses python3-pytest-httpserver python3-hypothesis
+ python3-pytest-cov $depends"
short_desc="Synchronize calendars and addressbooks"
maintainer="Andrew J. Hesford <ajh@sideband.org>"
license="BSD-3-Clause"
homepage="https://vdirsyncer.pimutils.org/"
+changelog="https://github.com/pimutils/vdirsyncer/raw/main/CHANGELOG.rst"
distfiles="${PYPI_SITE}/v/vdirsyncer/vdirsyncer-${version}.tar.gz"
-checksum=8e1e8403a08659e5a4e7fa3e9caaa2e2dce2bf1f98d923029049a34db75a2525
-
-pre_check() {
- vsed -e 's/^addopts/noaddopts/' -i setup.cfg
-}
+checksum=aa76c7725aa5a711f6374bc5cd83be78aae68c74829635a9ed073cd4c09f03ae
post_install() {
vsconf config.example
next prev parent reply other threads:[~2023-03-01 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 10:55 [PR PATCH] " pascal-huber
2023-03-01 11:04 ` [PR PATCH] [Updated] " pascal-huber
2023-03-01 11:14 ` pascal-huber [this message]
2023-03-03 1:46 ` [PR PATCH] [Merged]: " abenson
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=20230301111428.nKDImDXALYzLVT0kEtGJG4yzFOUJgS_wcBDHkWQrZ1g@z \
--to=pascal-huber@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).