Your message dated Sun, 05 Aug 2018 13:19:25 +0000
with message-id <[email protected]>
and subject line Bug#905372: fixed in network-manager 1.12.2-2
has caused the Debian Bug report #905372,
regarding network-manager-strongswan FTBFS: error: macro "G_UNAVAILABLE" passed
3 arguments, but takes just 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
905372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905372
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: network-manager-strongswan
Version: 1.4.4-1
Severity: serious
Tags: ftbfs
User: [email protected]
Usertags: rebootstrap
network-manager-strongswan fails to build from source. A build on amd64
ends with:
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libnm -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2
-DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -pthread -I/usr/include/libnma
-I/usr/include/libnm -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-DUIDIR=\"/usr/share/gnome-vpn-properties/strongswan\" -DG_DISABLE_DEPRECATED
-DGDK_DISABLE_DEPRECATED -Wall -Werror -std=gnu89 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wshadow -Wmissing-declarations -Wmissing-prototypes
-Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter
-Wno-sign-compare -fno-strict-aliasing -c nm-strongswan.c -fPIC -DPIC -o
.libs/libnm_vpn_plugin_strongswan_la-nm-strongswan.o
| In file included from /usr/include/libnm/NetworkManager.h:46,
| from nm-strongswan.c:37:
| /usr/include/libnm/nm-device-ovs-port.h:45:1: error: macro "G_UNAVAILABLE"
passed 3 arguments, but takes just 2
| NM_AVAILABLE_IN_1_12_2
| ^~~~~~~~~~~~~~~~~~~~~~
| /usr/include/libnm/nm-device-ovs-port.h:46:1: error: expected ';' before
'const'
| const GPtrArray *nm_device_ovs_port_get_slaves (NMDeviceOvsPort *device);
| ^~~~~
| In file included from /usr/include/libnm/NetworkManager.h:47,
| from nm-strongswan.c:37:
| /usr/include/libnm/nm-device-ovs-bridge.h:45:1: error: macro "G_UNAVAILABLE"
passed 3 arguments, but takes just 2
| NM_AVAILABLE_IN_1_12_2
| ^~~~~~~~~~~~~~~~~~~~~~
| /usr/include/libnm/nm-device-ovs-bridge.h:46:1: error: expected ';' before
'const'
| const GPtrArray *nm_device_ovs_bridge_get_slaves (NMDeviceOvsBridge *device);
| ^~~~~
| make[3]: *** [Makefile:559: libnm_vpn_plugin_strongswan_la-nm-strongswan.lo]
Error 1
| make[3]: Leaving directory '/<<PKGBUILDDIR>>/properties'
| make[2]: *** [Makefile:533: all-recursive] Error 1
| make[2]: Leaving directory '/<<PKGBUILDDIR>>'
| make[1]: *** [Makefile:423: all] Error 2
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:4: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
The reproducible people see a similar failure:
https://tests.reproducible-builds.org/debian/rbuild/buster/i386/network-manager-strongswan_1.4.4-1.rbuild.log.gz
Since their failure is in buster, this suggests that some dependency has
changed and made network-manager-strongswan fail. I don't know which one
though.
Helmut
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.12.2-2
We believe that the bug you reported is fixed in the latest version of
network-manager, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated network-manager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 05 Aug 2018 15:00:41 +0200
Source: network-manager
Binary: network-manager network-manager-dev libnm0 libnm-dev gir1.2-nm-1.0
network-manager-config-connectivity-debian
Architecture: source
Version: 1.12.2-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Description:
gir1.2-nm-1.0 - GObject introspection data for the libnm library
libnm-dev - GObject-based client library for NetworkManager (development file
libnm0 - GObject-based client library for NetworkManager
network-manager - network management framework (daemon and userspace tools)
network-manager-config-connectivity-debian - NetworkManager configuration to
enable connectivity checking
network-manager-dev - network management framework (development files)
Closes: 905372
Changes:
network-manager (1.12.2-2) unstable; urgency=medium
.
* Fix compile error due to NM_AVAILABLE_IN_1_12_2 macro (Closes: #905372)
Checksums-Sha1:
01449131acdf84c385d976988ee5067b395b107f 3168 network-manager_1.12.2-2.dsc
36d69cf0e97df0e1e3d0476c27ac4d1222c688ad 43932
network-manager_1.12.2-2.debian.tar.xz
71716c7c0f80bc3709ec62188ea83eb8df8fd19d 11618
network-manager_1.12.2-2_source.buildinfo
Checksums-Sha256:
990d911295efb58b6efc6bc326aaa9440a22e252a9ff38a01b148bfa6257428e 3168
network-manager_1.12.2-2.dsc
04116eb5c8a5bac87bb4b3feac5b24af4819ef77b1624fb5186a54f7a7892184 43932
network-manager_1.12.2-2.debian.tar.xz
69b370c8a92ee796c1dd488290c2bfad96bca153e62e2da9b41281ab5a1b9c74 11618
network-manager_1.12.2-2_source.buildinfo
Files:
0c33aa2d4a9000e6cf672982b3c7deb3 3168 net optional network-manager_1.12.2-2.dsc
106355bfd6592ec326145f52432e33ee 43932 net optional
network-manager_1.12.2-2.debian.tar.xz
e2179b464b285d723cf6669adf4ff5be 11618 net optional
network-manager_1.12.2-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAltm9TsACgkQauHfDWCP
ItwyNA//Tubpy5IyR84LbFNl+cxtjbkcPnF3S711TGgDww6R4XDZij4b/F/nxzlv
pYMjQ459prQDogZS0Hkf2VzgSFQjfFUjGDWNTsTDpCFIl+5r5yFBghD1q+TcLmQt
SqSiYAPPBzQnBxn+gcvCeizPezyhpGZHDx7SVvYkiaVJ3huwhuhbVu3RQERyFUnX
8WTtT25A0AMMyvVy2mjwXqiRX4pexhh42qivdme2l+pQoiKYTXdt85G/AAfvK/Kg
D4jfCk1tJtUQ+SCD1mmZU228EONJcQ9uBLJ9KESoIIWmr11raDo2nxsmcAMz/O00
/Q7zhgWssOUZd6rKEp6dTMAr+GzVephC+x/+nHsIueb29m9fWuQlaiLJeWB12Y4/
6F6CsA5uLxVA85aoSzRZa7mjWDQ3x4+66a9b5/LpxHyrqO16O4nXpH1xMU28PqrI
MgX+/nA1xHxKED9WTBrX49ZBZHv/gcku1q+si0sIR/s/HekzEhvVovPsWZ2Izo37
v143KqECE9/v4QFAm6qKfDEc9J7SBfn11XyrZMzLGMiEa/WhjPmXzB1JEPXHbOX7
tcLBpE32rYlixfnqQiigAbhIyu4MXyOfr1dnzQ5DvwLrUg7iyC73ugdxXM/IPveX
PMarU68vpmOjlTSpqCQ871U/q5dwjeAYKqZELFI60reehA6ZVqo=
=U+KE
-----END PGP SIGNATURE-----
--- End Message ---
