~awe/network-manager/+git/ubuntu:add-configure-hook

Last commit made on 2018-12-18
Get this branch:
git clone -b add-configure-hook https://git.launchpad.net/~awe/network-manager/+git/ubuntu
Only Tony Espy can upload to this branch. If you are Tony Espy please log in for upload directions.

Branch merges

Branch information

Name:
add-configure-hook
Repository:
lp:~awe/network-manager/+git/ubuntu

Recent commits

4e3e7e4... by Tony Espy

[snap] Do not fail on error when calling snapctl

The service should run even when some interfaces are not connected.

The original commit is a9d3cd6 from the nm 1.2 snap:

https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager

6b48e58... by Tony Espy

[snap] Do not exit on bad configuration

Do not exit when bad snap configuration values are detected, as that
would imply we finish with error and the service would not start.

The original commit is c907e9d from the nm 1.2 snap:

https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager

1a4e88b... by Tony Espy

[snap] Add the configure hook from the 1.2 snap

ca61fdd... by Tony Espy

Merge remote-tracking branch 'abeato/add-missing-deps' into snap-1.10

f5ffc91... by Alfonso Sanchez-Beato

Add some missing dependencies to the snap

41e3168... by Tony Espy

Merge remote-tracking branch 'awe/install-refresh-checks' into snap-1.10

ff5a236... by Tony Espy

[snap] prevent install on classic or core16

Prevent this snap from being installed on classic or
Ubuntu Core 16 systems. The snap has build configure options
which differ from the Debian package, and doesn't yet offer
the same features (i.e. no support for dispatcher scripts).
Likewise, until the snap supports configuration of DNS
resolv.conf behavior, it shouldn't be installable on UC16.

d1bf7f1... by Tony Espy

Merge remote-tracking branch 'awe/fix-apparmor-denial' into snap-1.10

d36d0db... by Tony Espy

[snap] Re-enable strict mode

22339a9... by Tony Espy

[snap] Add hardware-observe plug

This gets rid of Apparmor denials when NetworkManager
introspects devices on startup. These denials can lead
to NM mis-categorizing devices (ie. WiFi devices are
thought to be Ethernet).