From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] telepathy-mission-control: update to 5.16.6.
Date: Fri, 12 Aug 2022 19:20:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38638@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
There is a new pull request by TinfoilSubmarine against master on the void-packages repository
https://github.com/TinfoilSubmarine/void-packages update/telepathy-mission-control
https://github.com/void-linux/void-packages/pull/38638
telepathy-mission-control: update to 5.16.6.
Only python3 is needed as headers are not needed to build.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/38638.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/telepathy-mission-control-38638.patch --]
[-- Type: text/x-diff, Size: 3347 bytes --]
From 4c57e9eb8200a016b5570e2fcdf7c971f5cfcd35 Mon Sep 17 00:00:00 2001
From: Joel Beckmeyer <joel@beckmeyer.us>
Date: Fri, 12 Aug 2022 13:13:20 -0400
Subject: [PATCH] telepathy-mission-control: update to 5.16.6.
Only python3 is needed as headers are not needed to build.
---
.../patches/account-Fix-property-name.patch | 28 -------------------
srcpkgs/telepathy-mission-control/template | 6 ++--
2 files changed, 3 insertions(+), 31 deletions(-)
delete 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
deleted file mode 100644
index 051ffaad3a63..000000000000
--- a/srcpkgs/telepathy-mission-control/patches/account-Fix-property-name.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-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
---- a/src/mcd-account.c
-+++ b/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 f539aa07f1c8..c0916a93b0f3 100644
--- a/srcpkgs/telepathy-mission-control/template
+++ b/srcpkgs/telepathy-mission-control/template
@@ -2,11 +2,11 @@
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.5
+version=5.16.6
revision=1
build_style=gnu-configure
configure_args="--disable-static --enable-gnome-keyring --disable-schemas-compile"
-hostmakedepends="pkg-config python-devel intltool libxslt glib-devel"
+hostmakedepends="pkg-config python3 intltool libxslt glib-devel"
makedepends="libglib-devel telepathy-glib-devel NetworkManager-devel libgnome-keyring-devel"
depends="telepathy-glib>=0.22"
short_desc="Account manager and channel dispatcher for the Telepathy framework"
@@ -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=4c6b433b8b9079fd7df3e29aefcad6755a2081a9a634ffb6b33936c7d0d8bd03
+checksum=2df8ae3995e919a7670e01aa3568215ef0777e34961ace1cac1c6477cb297a45
telepathy-mission-control-devel_package() {
depends="telepathy-glib-devel>=0.22 ${sourcepkg}>=${version}"
next reply other threads:[~2022-08-12 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 17:20 TinfoilSubmarine [this message]
2022-08-12 17:23 ` [PR REVIEW] " classabbyamp
2022-08-12 18:43 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-08-12 18:47 ` [PR PATCH] [Merged]: " classabbyamp
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-38638@inbox.vuxu.org \
--to=tinfoilsubmarine@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).