summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * build/meson: merge branch 'heftig/pr/12'Thomas Haller2018-09-124-9/+36
| |\ | | | | | | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/12
| | * meson: Fix vapi buildJan Alexander Steffens (heftig)2018-09-121-3/+2
| | | | | | | | | | | | | | | Apparently vapigen can't find the NetworkManager-1.0.gir belonging to libnm-util.vapi.
| | * meson: Fix libnm-util buildJan Alexander Steffens (heftig)2018-09-121-4/+28
| | | | | | | | | | | | | | | This was broken by e01f7f2c6dccad7a950c1af4c31737a9628e809e. Port the commit's changes from libnm to libnm-util.
| | * meson: Use libexecdir for dnssec-trigger-script fallbackJan Alexander Steffens (heftig)2018-09-121-1/+5
| | | | | | | | | | | | Use an `if` to keep line length down.
| | * gitignore: Fix *.stamp ignoreJan Alexander Steffens (heftig)2018-09-121-1/+1
| |/ | | | | | | ripgrep complains about the invalid `**`.
| * platform/netlink: cleanup error number handlingThomas Haller2018-09-122-60/+82
| | | | | | | | | | | | | | | | | | | | | | Rename variables for the error number. Commonly the naming is: - errno: the error number from <errno.h> itself - errsv: a copy of errno - nlerr: a netlink error number - err: an error code, but not a errno/errsv and not a netlink error number.
| * platform/trivial: adjust coding style in nm-netlink.cThomas Haller2018-09-121-71/+71
| |
| * device: merge branch 'th/dhcp-error-reason'Thomas Haller2018-09-1212-216/+357
| |\ | | | | | | | | | https://github.com/NetworkManager/NetworkManager/pull/199
| | * dhcp: abort DHCP on devices without MAC address earlyThomas Haller2018-09-121-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Internal DHCPv4 client requires a valid MAC address for functioning. Just always require a MAC address to start DHCP, both v4 and v6. We have no MAC address for example on Layer3 devices like tun or wireguard. Also, before "34af574d58 systemd/dhcp: fix assertion starting DHCP client without MAC address", if we tired to start sd_dhcp_client without setting a MAC address, an assertion was triggered.
| | * systemd/dhcp: fix assertion starting DHCP client without MAC addressThomas Haller2018-09-121-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An assertion in dhcp_network_bind_raw_socket() is triggered when starting an sd_dhcp_client without setting setting a MAC address first. - sd_dhcp_client_start() - client_start() - client_start_delayed() - dhcp_network_bind_raw_socket() In that case, the arp-type and MAC address is still unset. Note that dhcp_network_bind_raw_socket() already checks for a valid arp-type and MAC address below, so we should just gracefully return -EINVAL. Maybe sd_dhcp_client_start() should fail earlier when starting without MAC address. But the failure here will be correctly propagated and the start aborted. See-also: https://github.com/systemd/systemd/pull/10054
| | * dhcp: return error reason from DHCP client startThomas Haller2018-09-1210-214/+319
| | |
| | * shared: add nm_errno() and nm_utils_error_set_errno() helperThomas Haller2018-09-121-0/+21
| |/
| * ppp: cleanup logging in impl_ppp_manager_set_ifindex()Thomas Haller2018-09-111-7/+6
| | | | | | | | | | | | It's enough that all code paths in impl_ppp_manager_set_ifindex() log exactly one message. Also, give all messages the same prefix, so that it's clear where they come from.
| * ppp: downgrade warning about repeated SetIfindex calls from ppp pluginThomas Haller2018-09-111-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | In src/ppp/nm-pppd-plugin.c, it seems that pppd can invoke phasechange(PHASE_RUNNING:) multiple times. Hence, the plugin calls SetIfindex multiple times too. In nm-ppp-manager.c, we want to make sure that the ifindex does not change after it was set once. However, calling SetIfindex with the same ifindex is not something worth warning. Just log a debug message and nothing. Maybe the plugin should remember that it already set the ifindex, and avoid multiple D-Bus calls. But it's unclear that that is desired. For now, just downgrade the warning.
| * ppp: avoid strncpy() in ppp plugin nm_phasechange()Thomas Haller2018-09-111-1/+1
| | | | | | | | | | strncpy() is deemed insecure, and it raises at least an eyebrow. While it's save in this case, just avoid it.
| * ppp-manager: avoid crash with nonexisting link in impl_ppp_manager_set_ifindex()Thomas Haller2018-09-111-1/+5
| | | | | | | | Fixes: dd98ada33f33820e0d0874d9aa97e0c2bfc7cdd0
| * ppp-manager: fix pppd not exiting correctly on modem hangupFrederic Danis2018-09-111-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When unplugging an USB 3G modem device, pppd does not exit correctly and we have the following traces: Sep 10 07:58:24.616465 ModemManager[1158]: <info> (tty/ttyUSB0): released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb4/4-1' Sep 10 07:58:24.620314 pppd[2292]: Modem hangup Sep 10 07:58:24.621368 ModemManager[1158]: <info> (tty/ttyUSB1): released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb4/4-1' Sep 10 07:58:24.621835 ModemManager[1158]: <warn> (ttyUSB1): could not re-acquire serial port lock: (5) Input/output error Sep 10 07:58:24.621358 NetworkManager[1871]: <debug> ppp-manager: set-ifindex 4 Sep 10 07:58:24.621369 NetworkManager[1871]: <warn> ppp-manager: can't change the ifindex from 4 to 4 Sep 10 07:58:24.623982 NetworkManager[1871]: <info> device (ttyUSB0): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed') Sep 10 07:58:24.624411 NetworkManager[1871]: <debug> kill child process 'pppd' (2292): wait for process to terminate after sending SIGTERM (15) (send SIGKILL in 1500 milliseconds)... Sep 10 07:58:24.624440 NetworkManager[1871]: <debug> modem-broadband[ttyUSB0]: notifying ModemManager about the modem disconnection Sep 10 07:58:24.626591 NetworkManager[1871]: <debug> modem-broadband[ttyUSB0]: notifying ModemManager about the modem disconnection Sep 10 07:58:24.681016 NetworkManager[1871]: <warn> modem-broadband[ttyUSB0]: failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Simple' on object at path /org/freedesktop/ModemManager1/Modem/0 Sep 10 07:58:26.126817 NetworkManager[1871]: <debug> kill child process 'pppd' (2292): process not terminated after 1502368 usec. Sending SIGKILL signal Sep 10 07:58:26.128121 NetworkManager[1871]: <info> device (ppp0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Sep 10 07:58:26.135571 NetworkManager[1871]: <debug> kill child process 'pppd' (2292): terminated by signal 9 (1511158 usec elapsed) This is due to nm-ppp-plugin waiting on SetIfIndex call until timeout, which is longer than termination process timeout. Calling g_dbus_method_invocation_return_value() on error fixes this. Fixes: dd98ada33f33820e0d0874d9aa97e0c2bfc7cdd0 https://mail.gnome.org/archives/networkmanager-list/2018-September/msg00010.html
| * wifi/iwd: handle new GetOrderedNetworks() return typeAndrew Zaborowski2018-09-111-54/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Station.GetOrderedNetworks dbus method's return type has changed in IWD commit 0a42f63d42be903a46c595693884772c1c84d39f as the last incompatible API change before IWD 0.8 (docs change was made earlier in 0453308134a3aadb6a2ec6a78ea642e19427704c) so that network names and types are no longer included in the reply. Expect this new reply signature although still handle the old signature if we're using the Device interface for IWD <= 0.7 compatibility. It may be good idea to eventually pass the object manager instance from nm-iwd-manager.c to nm-device-iwd.c to avoid using g_dbus_proxy_new_sync and g_dbus_proxy_new_for_bus_sync in act_stage2_config, which possibly generates a lot of DBus property queries. https://github.com/NetworkManager/NetworkManager/pull/197
| * dhcp: fix leak in dhclient's dhclient_start()Thomas Haller2018-09-101-2/+6
| | | | | | | | Fixes: 5d6d5cd136e36ed2815b7c719ada32bc6d22b481
| * device: mark wireguard devices as unmanagedThomas Haller2018-09-101-1/+5
| | | | | | | | | | | | | | | | | | Later we want to fully support wireguard devices. Also, possibly activating a generic profile in a wireguard device would make sense. Anyway, for the moment, just prevent that from happening by explicitly marking the device as unmanaged.
| * device: rename NM_UNMANAGED_LOOPBACK to NM_UNMANAGED_BY_TYPEThomas Haller2018-09-102-6/+6
| | | | | | | | It is generally useful, not only for loopback. Rename.
| * device: detect loopback device explicitlyThomas Haller2018-09-101-2/+11
| | | | | | | | Don't use NM_UNMANAGED_LOOPBACK for that.
| * device: make device incompatible with profiles by defaultThomas Haller2018-09-101-0/+8
| | | | | | | | | | | | | | | | | | Currently, NMDeviceWireguard does neither set connection_type_check_compatible nor implement check_connection_compatible. That means, it appears to be compatible with every connection profile, which is obviously wrong. Allow devices not to implement check_connection_compatible() and avoid the issue by rejecting profiles by default.
| * release: bump version to 1.15.0 (development)1.15.0-devThomas Haller2018-09-084-3/+18
| |
* | release: bump version to 1.14.01.14.0Thomas Haller2018-09-142-3/+3
| |
* | release: update NEWSThomas Haller2018-09-141-6/+5
| |
* | libnm/trivial: whitespaceThomas Haller2018-09-141-8/+8
| | | | | | | | (cherry picked from commit 3b5912f08d1a813fff64ac0e3ef82f9b4fa37763)
* | clients: fix memory leak when parsing routesBeniamino Galvani2018-09-141-2/+11
| | | | | | | | | | | | | | | | The new hash table should destroy elements stolen from the hash table returned by nm_utils_parse_variant_attributes(). Fixes: d0949141203f6a546317277ed788ea114d401dd8 (cherry picked from commit 31bda1b8373c71ecb41d8208aa2bc9c88999d988)
* | libnm: document nm_utils_parse_variant_attributes() returning floating ↵Thomas Haller2018-09-141-1/+3
| | | | | | | | | | | | | | references See-also: https://bugzilla.redhat.com/show_bug.cgi?id=1594887 (cherry picked from commit e645aeb12ccefb1fbe18bb33d046ee649de86da0)
* | libnm: add missing NM_AVAILABLE_IN_1_2 macro for nm_connection_get_setting_tun()Thomas Haller2018-09-141-0/+1
| | | | | | | | (cherry picked from commit a525b12c5a17dba46ae4323d112284e1c6cf4ddc)
* | libnm: add missing NM_AVAILABLE_IN_1_14 macro to new APIThomas Haller2018-09-141-0/+1
| | | | | | | | | | Fixes: df30651b8906cfe6a5cb7aef01a220d1f21b80f3 (cherry picked from commit bbc93a2e3072438f16102463bfa0ed97a3ddb009)
* | autoptr: add missing autoptr cleanup functionsThomas Haller2018-09-141-0/+4
| | | | | | | | (cherry picked from commit c1b647d54f659da3f72b449ead5c24fb338c3533)
* | libnm: drop API nm_connection_get_setting_{6lowpan,sriov,wpan}()Thomas Haller2018-09-147-69/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note that NMSettingEthtool and NMSettingMatch don't have such functions either. We have API nm_connection_get_setting (NMConnection *, GType) nm_connection_get_setting_by_name (NMConnection *, const char *) which can be used generically, meaning: the requested setting type is an argument to the function. That is generally more useful and flexible. Don't add API which duplicates existing functionality and is (arguably) inferiour. Drop it now. This is an ABI/API break for the current development cycle where the 1.14.0 API is still unstable. Indeed it's already after 1.14-rc1, which is ugly. But it's also unlikely that somebody already uses this API/ABI and is badly impacted by this change. Note that nm_connection_get_setting() and nm_connection_get_setting_by_name() are slightly inconvenient in C still, because they usually require a cast. We should fix that by changing the return type to "void *". Such a change may be possibly any time without breaking API/ABI (almost, it'd be an API change when taking a function pointer without casting). (cherry picked from commit a10156f5165f644e344fa5163a5958080a2a7393)
* | vpn: disconnect signal handlers from proxy in NMVpnConnection::dispose()Thomas Haller2018-09-141-0/+3
| | | | | | | | | | | | | | | | We cannot be sure who holds a reference to the proxy, and who is gonna call us back after the VPN connection instance is destroyed. (cherry picked from commit 6ebb9091d272c7af4e1eaab4a110f7de37fb2b4d)
* | vpn: fix assertion during "SecretsRequired" in unexpected stateThomas Haller2018-09-141-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Got this assertion: NetworkManager[12939]: <debug> [1536917977.4868] active-connection[0x563d8fd34540]: set state deactivated (was deactivating) ... NetworkManager[12939]: nm-openvpn[1106] <info> openvpn[1132]: send SIGTERM NetworkManager[12939]: nm-openvpn[1106] <info> wait for 1 openvpn processes to terminate... NetworkManager[12939]: nm-openvpn[1106] <warn> openvpn[1132] exited with error code 1 NetworkManager[12939]: <info> [1536917977.5035] vpn-connection[0x563d8fd34540,2fdeaea3-975f-4325-8305-83ebca5eaa26,"my-openvpn-Red-Hat",0]: VPN plugin: requested secrets; state disconnected (9) NetworkManager[12939]: plugin_interactive_secrets_required: assertion 'priv->vpn_state == STATE_CONNECT || priv->vpn_state == STATE_NEED_AUTH' failed Meaning. We should either ensure that secrets_required_cb() signal callback is disconnected from proxy's signal, or we gracefully handle callbacks at unexpected moments. Do the latter. (cherry picked from commit 92344dd0848f2353b81eab5b0b294eb92aaf59c0)
* | cli: fix reading "vpn.secrets.*" from passwd-fileThomas Haller2018-09-145-9/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to a bug, we required VPN secrets to be prefixed with "vpn.secret." instead of "vpn.secrets.". This was a change in behavior with 1.12.0 release. Fix it, to restore the old behavior. For backward compatibility to the broken behavior, adjust parse_passwords() to treat accept that as well. https://bugzilla.redhat.com/show_bug.cgi?id=1628833 https://github.com/NetworkManager/NetworkManager/pull/201 Fixes: 0601b5d725b072bd3ce4ec60be867898a16f85cd (cherry picked from commit 5815ae8c60961f088e4e54b41ddf8254cb83574a)
* | contrib/rpm: fix mode of ghost ifup/ifdown filesBeniamino Galvani2018-09-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Set the execution bit on /usr/sbin/{ifup,ifdown} ghost files to match the mode of same files installed by initscripts. Otherwise, they will appear as changed according to rpm verify: .M....... g /usr/sbin/ifdown .M....... g /usr/sbin/ifup when the alternatives mechanism is not in place. # ll /usr/sbin/if{up,down} -rwxr-xr-x. 1 root root 1651 Aug 24 06:23 /usr/sbin/ifdown -rwxr-xr-x. 1 root root 5010 Aug 24 06:23 /usr/sbin/ifup https://bugzilla.redhat.com/show_bug.cgi?id=1626517 (cherry picked from commit d8a972c575c44b39dd170ab58d6a8937f7893d3f)
* | contrib/rpm: fix handling of --with test defaultThomas Haller2018-09-141-1/+13
| | | | | | | | | | | | | | | | | | | | | | Seems rpmbuild does not honor the latest occurance with --with test --without test to disable tests. Work around that. Fixes: ad850c4f03a93a21d745b2e46cca78525bdad843 (cherry picked from commit cc8c207120a766946b25d39ab5211840a12d20cb)
* | contrib/rpm: disable tests by default and use fatal-warnings with testsThomas Haller2018-09-142-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In general, when we build a package, we want no compiler warnings and all unit tests to pass. That is in particular true when building a package for the distribution in koji. When builing in koji, we (rightly) cannot pass rpmbuild options, so the default whether tests/compiler-warnings are fatal matter very much. One could argue: let's have the tests/compiler-warnings fatal and fail the build. During a build in koji for a Fedora release, we want them all pass. And if somebody does a manual build, the person can patch the spec file (or use rpmbuild flags). However, note how commit "f7b5e48cdb contrib/rpm: don't force fatal warnings with tests" already disabled fatal compiler warnings. Why? It seems compiler warnings should be even more stable than our unit tests, as long as you target a particular Fedora release and compiler version. So this was done to support rebuilding an SRPM for a different Fedora release, or to be more graceful during early development phase of a Fedora release, where things are not as stable yet. The exactly same reasoning applies to treating unit-tests failures as fatal. For example, a recent iproute2 issue broke unit tests. That meant, with that iproute2 release in build root, the NetworkManager RPM could not be built. Very annoying. Now: - if "test" is enabled, that means both `make check` and compiler warnings are treated fatal. If "test" is disabled, `make check` and compiler warnings are still done, just not fatal. - "test" is now disabled by default via the spec file. They are not fatal when building in koji or when rebuilding the package manually. - tests can be enabled optionally. Note that the "build_clean.sh" script enables them by default. So, a user using this script would need to explicitly "--without test". (cherry picked from commit ad850c4f03a93a21d745b2e46cca78525bdad843)
* | contrib/rpm: always run tests and enable more compiler warnings in package buildThomas Haller2018-09-141-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - always enable more compiler warnings. They are not marked as breaking the build anyway. - also, always build with '--with-tests=yes'. Note that our autotools is actually very nice. Even if you build '--with-tests=no', you still can run `make check` and the tests are build on demand. The only difference here is whether the tests are build during `make` or during `make check`. While little difference, build everything during the `make` step. - when running tests, use `make -k check`. Even if they fail, we want to run the entire test suite. - also running tests are disabled, still run them. But don't let them fail the build. (cherry picked from commit 58b030f39a3241313fd500a67bff5d1b07019b30)
* | build: merge branch 'th/check-gtk-doc-behavior'Thomas Haller2018-09-143-1/+21
|\ \ | | | | | | | | | | | | | | | https://github.com/NetworkManager/NetworkManager/pull/196 (cherry picked from commit aa8a7559a330269f49cdc5ae16743a6ec491b659)
| * | contrib/rpm: add --release option to build_clean.sh scriptThomas Haller2018-09-141-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The correct way to create a tarball for release is ./contrib/fedora/rpm/build_clean.sh -r Just ensure to issue this from a clean shell environment. (cherry picked from commit 5894da67dc040fccd40c014ab73f31e1d9e1e661)
| * | docs/test: add check that gtk-doc contains patch to generate proper ↵Thomas Haller2018-09-141-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | documentation In libnm, we prefer opaque typedefs. gtk-doc needs to be patched to properly generate documentation. Add a check for that. Add a test. By default, this does not fail but just prints a warning. The test can be made failing by setting NMTST_CHECK_GTK_DOC=1. See-also: https://gitlab.gnome.org/GNOME/gtk-doc/merge_requests/2 (cherry picked from commit 02464c052e2f8a1e88b012e0a29f5f66fce310ad)
| * | build: fix error message in configure script about gtk-docThomas Haller2018-09-141-1/+1
|/ / | | | | | | (cherry picked from commit 815834aebcdf4b65311952163a8d38805e950407)
* | contrib/rpm: disable --with-more-asserts for devel-buildsThomas Haller2018-09-141-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The NetworkManager spec file used to determine devel builds as those that have an odd minor version number. In that case, the built package would enable more-asserts. -- By the way, why is '1.13.3-dev' considered a delopment version worthy of more asserts, but a build from the development phase of the next minor release on 'nm-1-12' branch not? Note that during the development phase of Fedora (and sometimes even afterwards), we commonly package development versions from 'master'. For example '1.12.0-0.1', which is some snapshot with version number '1.11.x-dev' (or '1.12-rc1' in this case), but before the actual '1.12.0' release. It's problematic that for part of the devel phase we compile the package for the distribution with more assertions. This package is significanly different and rpmdiff and coverity give different results for them. For example, the binary size of debug packages is larger, so first rpmdiff will complain that the binary sized increased (compare to the previous version) and then later it decreases again. Likewise, coverity finds significantly different issues on a debug build. For example, it sees assertions against NULL and takes that as a hint as to whether the parameter can/shall be NULL. Keeping coverity warnings low is already high effort to sort out false positives. We should not invest time in checking debug builds with coverity, at least not as long as there are more important issues. But more importantly, the --with-more-asserts configure option governs whether nm_assert() is enabled. The only point of existance of nm_assert() -- compared to g_assert(), g_return_*() and assert() -- is that this variant is disabled by default. It's only used for checks that are really really not supposed to fail and/or which may be expensive to do. This is useful for developing and CI, but it's not right to put into the distribution. It really enables assertions that you don't want in such a scenario. Enabling them even for distribution builds defeats their purpose. If you care about an assertion to be usually/always enabled, you should use g_assert() or g_return_*() instead. What this changes, that "devel" builds in koji/brew do not have more-asserts enabled. When manually building the SRPM one still can enable it, for example via $ ./contrib/fedora/rpm/build_clean.sh -w debug Also our CI has an option to build packages with or without more-asserts (defaulting to more asserts already). (cherry picked from commit b4e2f83403e45e039fdaeb825f04324dc7220cb2)
* | po: update Czech (cz) translationAsciiWolf2018-09-131-309/+252
| | | | | | | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/13 (cherry picked from commit 69b4b28bb8388437842010a2ace3e9a797ff3df8)
* | wifi: fix leaking fake AP in NMDeviceWifi's act_stage1_prepare()Thomas Haller2018-09-131-0/+1
| | | | | | | | | | Fixes: 96f40dcdcd8b2df204d64026f0315ff6370048fa (cherry picked from commit ef61d7909f594c4f3ec145d141387956a6d9c73e)
* | libnm: fix memleak in _nm_utils_ssid_to_string_arr()Thomas Haller2018-09-131-1/+1
| | | | | | | | | | Fixes: 5cd4e6f3e68bc4564656f0bb00b5261a8f6adeb7 (cherry picked from commit 54e1f73e0ca2ad87e14f4eacfe532eb444959ba6)
* | dns: dnsmasq: avoid crash when no reverse domains existBeniamino Galvani2018-09-131-4/+6
| | | | | | | | | | | | | | | | | | | | ip_data->domains.reverse can be NULL when the device is being removed and has no IP configuration for a short moment. Fixes: 6409e7719c0341baedfdb063366457e390894ed9 https://bugzilla.gnome.org/show_bug.cgi?id=797022 (cherry picked from commit f0c075f05082e4c77fac75ad06d303e7538e4fc7)
* | build: merge branch 'bg/meson-paths'Beniamino Galvani2018-09-1313-314/+194
|\ \ | | | | | | | | | | | | https://github.com/NetworkManager/NetworkManager/pull/198 (cherry picked from commit 4a1ff8ad8c543a76b2430a79fb8ffee52e8d3f56)
View Lorry Controller Status