Hello community, here is the log from the commit of package libproxy for openSUSE:Factory checked in at 2020-04-29 20:41:54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/libproxy (Old) and /work/SRC/openSUSE:Factory/.libproxy.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "libproxy" Wed Apr 29 20:41:54 2020 rev:76 rq:798290 version:0.4.15 Changes: -------- --- /work/SRC/openSUSE:Factory/libproxy/libproxy.changes 2020-03-27 00:22:13.312163329 +0100 +++ /work/SRC/openSUSE:Factory/.libproxy.new.2738/libproxy.changes 2020-04-29 20:42:19.183632846 +0200 @@ -1,0 +2,6 @@ +Mon Apr 27 10:10:47 UTC 2020 - Dominique Leuenberger <[email protected]> + +- Add libproxy-pxgsettings.patch: pxgsettings: use the correct + syntax to connect to the changed signal. + +------------------------------------------------------------------- New: ---- libproxy-pxgsettings.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ libproxy.spec ++++++ --- /var/tmp/diff_new_pack.Pd27ro/_old 2020-04-29 20:42:19.675634128 +0200 +++ /var/tmp/diff_new_pack.Pd27ro/_new 2020-04-29 20:42:19.675634128 +0200 @@ -49,6 +49,8 @@ Source99: baselibs.conf # PATCH-FIX-UPSTREAM libproxy-python3.7.patch [email protected] -- Add support for python 3.7 and 3.8, taken from upstream Patch0: libproxy-python3.7.patch +# PATCH-FIX-UPSTREAM libproxy-pxgsettings.patch [email protected] -- pxgsettings: use the correct syntax to connect to the changed signal +Patch1: libproxy-pxgsettings.patch BuildRequires: cmake BuildRequires: gcc-c++ BuildRequires: libmodman-devel @@ -273,6 +275,7 @@ %prep %setup -q -n %{_sourcename} %patch0 -p1 +%patch1 -p1 mkdir build %build ++++++ libproxy-pxgsettings.patch ++++++ >From 29c908647eec8e05674ba1c298d4f1c565d9f872 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Corentin=20No=C3=ABl?= <[email protected]> Date: Sun, 26 Apr 2020 11:54:46 +0200 Subject: [PATCH] pxgsettings: use the correct syntax to connect to the changed signal As it is a detailed signal, it only makes sense to append a :: when there is a specific property to target. It used to be accepted but triggers a runtime warning with latest GLib. --- libproxy/modules/pxgsettings.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libproxy/modules/pxgsettings.cpp b/libproxy/modules/pxgsettings.cpp index 9ed4333..0db5a6a 100644 --- a/libproxy/modules/pxgsettings.cpp +++ b/libproxy/modules/pxgsettings.cpp @@ -158,7 +158,7 @@ int main(int argc, char **argv) { #else gchar** keys = g_settings_list_keys(settings); #endif - g_signal_connect(settings, "changed::", G_CALLBACK (on_value_change), argv[i]); + g_signal_connect(settings, "changed", G_CALLBACK (on_value_change), argv[i]); for (int j=0; keys[j]; on_value_change(settings, keys[j++],argv[i] )); g_strfreev(keys); }
