[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention

In Debian 9 Stretch, works as it should. -- 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/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is

[Touch-packages] [Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 Check out my alternative workaround from duplicate bug #1628591. In my opinion, it's cleaner. I haven't heard of vconfig to be deprecated. Anyway... it's funny how we must do workarounds for basic

[Touch-packages] [Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 ** This bug has been marked a duplicate of bug 1628591 ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are

[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention

As a workaround, you could add "vlan-raw-device", like this: auto enp0s8 iface enp0s8 inet manual auto enp0s8.7 iface enp0s8.7 inet static vlan-raw-device enp0s8 address x.x.x.x/y It's a pity that such a project doesn't pay more attention to basic features... -- You received this bug

[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention

** Summary changed: - ifup and ifdown dont work for vlan devices when raw ethernet device name does not meet regular conventions + ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty

Thank you, Janitor ! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in

[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty

** Summary changed: - Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty + Security issues (solved in Debian) - affecting icu52 in trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu.

[Touch-packages] [Bug 1684298] [NEW] Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty

*** This bug is a security vulnerability *** Public security bug reported: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International