This bug was fixed in the package openvswitch -
1.4.2+git20120612-2ubuntu1
---
openvswitch (1.4.2+git20120612-2ubuntu1) quantal; urgency=low
* Fix openvswitch-switch startup with 3.5 kernel module name, allowing
use of openvswitch without openvswitch-datapath-dkms (LP:
This bug was fixed in the package openvswitch -
1.4.2+git20120612-2ubuntu1
---
openvswitch (1.4.2+git20120612-2ubuntu1) quantal; urgency=low
* Fix openvswitch-switch startup with 3.5 kernel module name, allowing
use of openvswitch without openvswitch-datapath-dkms (LP:
Found some advice on upstream mailing list:
http://openvswitch.org/pipermail/discuss/2012-May/007357.html
I'll try a cherry pick of this commit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
Found some advice on upstream mailing list:
http://openvswitch.org/pipermail/discuss/2012-May/007357.html
I'll try a cherry pick of this commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021078
Ben Pfaff
Any advice from upstream on how to deal with this? When will a version
of openvswitch be released which directly supports the 3.5 kernel module
naming? or we could carry a patch in Ubuntu in the interim if that
works OK.
Help appreciated.
--
You received this bug notification
Ben Pfaff
Any advice from upstream on how to deal with this? When will a version
of openvswitch be released which directly supports the 3.5 kernel module
naming? or we could carry a patch in Ubuntu in the interim if that
works OK.
Help appreciated.
--
You received this bug notification
