From: mnabid <mnabid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telepathy-mission-control: update to 5.16.5.
Date: Sat, 25 Apr 2020 03:53:37 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21320@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
There is a new pull request by mnabid against master on the void-packages repository
https://github.com/mnabid/void-packages telepathy-mission-control
https://github.com/void-linux/void-packages/pull/21320
telepathy-mission-control: update to 5.16.5.
A patch file from https://github.com/void-linux/void-packages/pull/21320.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-telepathy-mission-control-21320.patch --]
[-- Type: text/x-diff, Size: 2924 bytes --]
From 06bfc1a79e4243b0ef6f1f17faaab1b31e41aca1 Mon Sep 17 00:00:00 2001
From: Nafis <mnabid.25@outlook.com>
Date: Sat, 25 Apr 2020 07:36:17 +0600
Subject: [PATCH] telepathy-mission-control: update to 5.16.5.
---
.../patches/account-Fix-property-name.patch | 28 +++++++++++++++++++
srcpkgs/telepathy-mission-control/template | 4 +--
2 files changed, 30 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/telepathy-mission-control/patches/account-Fix-property-name.patch
diff --git a/srcpkgs/telepathy-mission-control/patches/account-Fix-property-name.patch b/srcpkgs/telepathy-mission-control/patches/account-Fix-property-name.patch
new file mode 100644
index 00000000000..f32752fd1d9
--- /dev/null
+++ b/srcpkgs/telepathy-mission-control/patches/account-Fix-property-name.patch
@@ -0,0 +1,28 @@
+From d8dab08fe8db137c6bbd8bbdc3d9b01d98c48910 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
+Date: Thu, 19 Dec 2019 13:37:49 +0100
+Subject: [PATCH] account: Fix property name
+
+Spaces are not valid characters in property names, and never were.
+Until recently GLib silently fixed up the name by replacing the
+space with '-', but now tightened up the validation.
+---
+ src/mcd-account.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git src/mcd-account.c src/mcd-account.c
+index 8009110e..de5c61cf 100644
+--- src/mcd-account.c
++++ src/mcd-account.c
+@@ -3442,7 +3442,7 @@ mcd_account_class_init (McdAccountClass * klass)
+
+ g_object_class_install_property
+ (object_class, PROP_CONNECTIVITY_MONITOR,
+- g_param_spec_object ("connectivity monitor",
++ g_param_spec_object ("connectivity-monitor",
+ "Connectivity monitor",
+ "Connectivity monitor",
+ MCD_TYPE_CONNECTIVITY_MONITOR,
+--
+2.24.1
+
diff --git a/srcpkgs/telepathy-mission-control/template b/srcpkgs/telepathy-mission-control/template
index 43c41c5d674..f539aa07f1c 100644
--- a/srcpkgs/telepathy-mission-control/template
+++ b/srcpkgs/telepathy-mission-control/template
@@ -2,7 +2,7 @@
pkgname=telepathy-mission-control
reverts="5:5.16.4_1 5:5.16.1_2 5:5.16.1_1 5:5.16.0_2 5:5.16.0_1 5:5.15.1_1
5:5.14.1_1 2:5.14.1_1 1:5.14.1_1"
-version=5.16.4
+version=5.16.5
revision=1
build_style=gnu-configure
configure_args="--disable-static --enable-gnome-keyring --disable-schemas-compile"
@@ -14,7 +14,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="LGPL-2.1-or-later"
homepage="http://telepathy.freedesktop.org"
distfiles="${homepage}/releases/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=9769ddac7ad8aad21f6db854016792162b57e6fa0b0aed8d823d76a71fe7e6cb
+checksum=4c6b433b8b9079fd7df3e29aefcad6755a2081a9a634ffb6b33936c7d0d8bd03
telepathy-mission-control-devel_package() {
depends="telepathy-glib-devel>=0.22 ${sourcepkg}>=${version}"
next reply other threads:[~2020-04-25 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 1:53 mnabid [this message]
2020-04-25 2:03 ` [PR PATCH] [Updated] " mnabid
2020-04-25 11:50 ` [PR PATCH] [Merged]: " Piraty
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-21320@inbox.vuxu.org \
--to=mnabid@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).