[Touch-packages] [Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
bump! definitely a repeatable issue albeit sporadically. lost another system on reboot - no default gateway installed although it's set in /e/n/i. have to manually add route via rc.local and symlink /etc/resolv.conf.d/resolv.conf original to tail as workarounds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
i think this affects more than just "bond" interfaces, and more than just the gateway setting from /etc/network/interfaces. i think dns- settings are also affected as experienced on 4 of my systems. note bug #1628552 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
yes i think all of them. the interface appears to always be configured correctly. however, sometimes the default gateway is not set, other times the dns- settings are not set, and still other times neither are set. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
note see package ifupdown bug #1573272. it would seem related but note that dns- settings are also problematic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
well i've now been able to restart 3 of the 4 systems about 5-10x each through the day. all have had their gateway and dns- settings from /e/n/i reliably set. that is, until now. i've got one system that did not get gateway or dns- settings. is there a way to check for a failure status code tied to ifup or resolvconf runs during startup? $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address x.y.105.96 netmask 255.255.252.0 # network x.y.104.0 broadcast x.y.107.255 gateway x.y.107.250 # dns-* options are implemented by the resolvconf package, if installed dns-nameserver x.y.105.44 dns-nameserver x.y.147.98 dns-search r.mydomain s.mydomain t.mydomain $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN note: i have since removed the comments from base & tail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
thank you. that of course worked (apologies for not fully understanding the parsing of the base file). interestingly enough, with that search addition in the base file, now the settings from /etc/network/interfaces are now showing up in resolv.conf (bogus.com is appended to the other dns-search settings) and on 3 successive startups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628552] [NEW] on startup gateway & dns- options in /etc/network/interfaces are not always set
Public bug reported: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Also affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
