Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

2016-06-10 Thread Russell Bryant
On Fri, Jun 10, 2016 at 4:38 PM, Ben Pfaff wrote: > On Thu, Jun 09, 2016 at 04:07:13AM -0400, Russell Bryant wrote: > > I uploaded "2.6.0.dev1". This was to enable OpenStack CI to start > running > > tests using the version of the Python library that includes Py

Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

2016-06-10 Thread Russell Bryant
On Thu, Jun 9, 2016 at 11:04 PM, Joe Stringer wrote: > On 9 June 2016 at 08:50, Terry Wilson wrote: > > On Thu, Jun 9, 2016 at 3:07 AM, Russell Bryant wrote: > >> The real solution to making this less awkward would be to split the > Python > >> library out of the

Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

2016-06-09 Thread Russell Bryant
On Thu, Jun 9, 2016 at 11:50 AM, Terry Wilson wrote: > On Thu, Jun 9, 2016 at 3:07 AM, Russell Bryant wrote: > > The real solution to making this less awkward would be to split the > Python > > library out of the OVS git tree so that it can be released independently > of

Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

2016-06-09 Thread Russell Bryant
hat it's a dev snapshot of what will eventually (presumably) be 2.6.0. I know OVS generates 2.5.90, but I don't find that appropriate to use, as it isn't 2.5 at all. Regarding the debian issue, I don't see a need to package anything new beyond 2.5.x. It just won't include Python 3 support yet. The real solution to making this less awkward would be to split the Python library out of the OVS git tree so that it can be released independently of OVS itself. That way a proper verison could be released that includes Python 3 support. -- Russell Bryant