From: freshprince <freshprince@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] synapse: update to 1.28.0.
Date: Mon, 01 Mar 2021 11:41:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29151@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
There is a new pull request by freshprince against master on the void-packages repository
https://github.com/freshprince/void-packages synapse-1.28.0
https://github.com/void-linux/void-packages/pull/29151
synapse: update to 1.28.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
-->
A patch file from https://github.com/void-linux/void-packages/pull/29151.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-synapse-1.28.0-29151.patch --]
[-- Type: text/x-diff, Size: 1084 bytes --]
From 77e112d047212eb8127a00c95d76db7b4e5f973a Mon Sep 17 00:00:00 2001
From: David Flatz <david@upcs.at>
Date: Mon, 1 Mar 2021 11:40:29 +0100
Subject: [PATCH] synapse: update to 1.28.0.
---
srcpkgs/synapse/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/synapse/template b/srcpkgs/synapse/template
index f25d1f9f5838..e9ffab6b7075 100644
--- a/srcpkgs/synapse/template
+++ b/srcpkgs/synapse/template
@@ -1,6 +1,6 @@
# Template file for 'synapse'
pkgname=synapse
-version=1.27.0
+version=1.28.0
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -19,7 +19,7 @@ license="Apache-2.0"
homepage="https://github.com/matrix-org/synapse"
changelog="https://raw.githubusercontent.com/matrix-org/synapse/develop/CHANGES.md"
distfiles="https://github.com/matrix-org/synapse/archive/v${version}.tar.gz"
-checksum=d87ba2187210eff0571106315421a81b9bf5c5101deb5e6f849921ad28ff3f5a
+checksum=509c5241ae6621b397d769cc9665a8f86983b2e8f17d63795721601600d8132c
system_accounts="synapse"
synapse_homedir="/var/lib/synapse"
next reply other threads:[~2021-03-01 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:41 freshprince [this message]
2021-03-01 19:46 ` [PR PATCH] [Merged]: " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29151@inbox.vuxu.org \
--to=freshprince@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).