Comment 12 for bug 1676547

I upgraded a Xenial system to Yakkety, then enabled -proposed and installed the new version of network-manager.

bdmurray@clean-xenial-amd64:~$ apt-cache policy network-manager
network-manager:
  Installed: 1.2.6-0ubuntu1
  Candidate: 1.2.6-0ubuntu1.1
  Version table:
     1.2.6-0ubuntu1.1 500
        500 http://192.168.10.7/ubuntu yakkety-proposed/main amd64 Packages
 *** 1.2.6-0ubuntu1 500
        500 http://192.168.10.7/ubuntu yakkety-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1.2.4-0ubuntu1 500
        500 http://192.168.10.7/ubuntu yakkety/main amd64 Packages
bdmurray@clean-xenial-amd64:~$ sudo apt-get install network-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  network-manager
1 upgraded, 0 newly installed, 0 to remove and 52 not upgraded.
Need to get 1,996 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu yakkety-proposed/main amd64 network-manager amd64 1.2.6-0ubuntu1.1 [1,996 kB]
Fetched 1,996 kB in 0s (82.5 MB/s)
(Reading database ... 188256 files and directories currently installed.)
Preparing to unpack .../network-manager_1.2.6-0ubuntu1.1_amd64.deb ...
Unpacking network-manager (1.2.6-0ubuntu1.1) over (1.2.6-0ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up network-manager (1.2.6-0ubuntu1.1) ...
Processing triggers for systemd (231-9ubuntu4) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.10-1ubuntu1.1) ...
bdmurray@clean-xenial-amd64:~$ sudo shutdown -r now
Connection to clean-xenial-amd64.local closed by remote host.
Connection to clean-xenial-amd64.local closed.

After the reboot I had network connectivity.

 $ ssh clean-xenial-amd64.local
Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-49-generic x86_64)

Setting to verification-done.