cli: add missing properties (mainly secrets flags, and some others)
build: clean up dbus-glib checks

dbus_glib_global_set_disable_legacy_property_access() was added in dbus-glib
0.88, and since we require 0.94 we can remove this check.
po: updated Italian (it) translation (bgo #692742)
introspection: belatedly add NM_DEVICE_CAP_AP
core: fix setting port attributes

They need to be written to the "bridge_port" directory, not the
"bridge" directory.
core: fix writing blank sysctl values

Sometimes we need to write blank values.
core: don't fail if bond slave is already a slave of the requested master

Would otherwise file if NM was restarted when a bond was active.
core: handle slave deactivation more gracefully

Two things:

1) When the slave was deactivated, nm_device_deactivate() runs before
the master gets the slave's state-changed signal, and thus priv->master
is cleared long before nm_device_notify_enslaved() is called.  Which
would trigger the g_assert (priv->master).

2) If the slave is already deactivated, there's no point in re-queueing
a state change to deactivated.

So just assert that priv->master is valid if the slave is going to be
enslaved, but if the slave is being released, ignore NULL priv->master
which we don't use anyway.  Also ignore redundant state changes.
core: log when last slave is removed
core: ignore carrier changes on enslaved interfaces

It's not very helpful to deactivate a slave of a bond or a bridge
port because the carrier is lost.  Carrier failures are normal
operation when using various bonding failover modes.  For bridge
ports, it's probably not very helpful either.  Given that the
masters are all virtual interfaces and have been explicitly
configured and started by a user, the configuration should
generally be left alone unless explicitly deactivated or changed.
core: preserve errno in nm_utils_do_sysctl()

Callers may need the error to determine their course of action
in response to a failure.
core: update hardware address when slaves change

The hardware address of a device often changes when slaves change,
for example with bond interfaces, which take the hardware address of
their first slave.  Make sure that's always up-to-date.
bond: set slave IFF_UP after releasing it

The kernel bonding code calls "closes" (which clears IFF_UP) the slave
and restores some of its attributes (MAC address, MTU, etc), but doesn't
bring it back up.  This breaks things like carrier detection, and
indeed when the device is closed, its carrier is also cleared, which
leads us to think the device is not available for activation.

To ensure that further events are noticed by the device, and that its
carrier state is accurately represented, make sure the device is still
IFF_UP after it  has been released.
trivial: quiet useless log message

Managed/unmanaged status is conveyed by the immediate state change,
so no need to redundantly log it.
logging: add BRIDGE log domain
bridge: update log domains for LOGD_BRIDGE
core: emit NMDeviceWired carrier change after logging it

Less confusing in the logs to see the change logged before listeners
have a chance to emit other log messages that may depend on the new
carrier state.
core: add IS_MASTER property to NMDevice

We can't just check whether there are slaves or not, because the
master device may be started before any slaves exist, and the
slaves get added later.
core: allow Wired device subclasses to override carrier handling

Bond devices, for example, don't want carrier state to affect
connection state.  Allow subclasses to override the Wired class'
handling if they want.
bond: device availability shouldn't depend on carrier state

Bond master carrier state follows slave carriers, so clearly we
can't depend on carrier when deciding whether we can activate a
bond connection which doesn't yet have any slaves.  Also, when
the bond's carrier goes down, we don't want to deactivate the
connection because this is normal in some failover modes and
could be the user reconfiguring slaves.