Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Hi Klement, It’s okay :-) Just open a ticket, cherry-pick the patch and append the jira ticket id to the subject. That should be enough. Cheers, Florin > On Oct 5, 2017, at 8:11 AM, Klement Sekera -X (ksekera - PANTHEON > TECHNOLOGIES at Cisco) wrote: > > Oh shoot, I

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Oh shoot, I never really learned the process.. Looking at the other email, I've already screwed this up on multiple levels as I did not file a JIRA and committed to master instead of release throttle. How do we proceed in these cases? Quoting Billy McFall (2017-10-05 17:08:50) >Klement, >

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Klement, Thank you for the path "drop python3 dependency" on master ( https://gerrit.fd.io/r/#/c/8584/), it will make ours lives downstream much easier. I don't see the patch on stable/1710. Is there a plan to cherry pick to 1710? (Sorry if it already there, just didn't see it.) Thanks, Billy

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

> I don't know about CSIT, but "make test" tests use python API bindings, > which internally uses old C API bindings (vapiclient). Unless we want > to remove old C API, there is little motivation to rework python API > binding as it contains more or less the same logic as the new C/C++ API >

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

I thought of a solution, but it a purely technological one that ignores any business relationship details, as they are above my pay grade: if VPP were part of the EPEL distribution rather than directly part of RHEL/CentOS, then there would be no problems! Burt On Mon, Sep 25, 2017 at 7:31 AM,

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Posted from iPhone. Forgive top posting, and terse writing style.. --Thomas F Herbert SDN Group Office of Technology Red Hat > On Sep 25, 2017, at 1:03 PM, Klement Sekera -X (ksekera - PANTHEON > TECHNOLOGIES at Cisco) wrote: > > Quoting Thomas F Herbert (2017-09-25

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Quoting Thomas F Herbert (2017-09-25 13:31:55) >On 09/25/2017 05:02 AM, Marco Varlese wrote: > > Thanks for the thorough explanation Klement!Based on that, I think (2) is > still the better option for the current situation... > > Tom, how would that sound to you? > > > "Klement Sekera

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

On 09/25/2017 05:02 AM, Marco Varlese wrote: Thanks for the thorough explanation Klement!Based on that, I think (2) is still the better option for the current situation... Tom, how would that sound to you? "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)"

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Thanks for the thorough explanation Klement!Based on that, I think (2) is still the better option for the current situation... Tom, how would that sound to you? >>> "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)" >>> 09/25/17 10:40 AM >>> Quoting Marco

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Quoting Marco Varlese (2017-09-25 10:26:50) > Hi Klement, > > >>> "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)" > >>> 09/25/17 9:33 AM >>> > > At the time of creating this patch, epel was part of Makefile and > > python34 was installed as dependency from that

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

Hi Klement, >>> "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)" >>> 09/25/17 9:33 AM >>> > At the time of creating this patch, epel was part of Makefile and > python34 was installed as dependency from that repo. > (see

Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

At the time of creating this patch, epel was part of Makefile and python34 was installed as dependency from that repo. (see https://gerrit.fd.io/r/#/c/6983/53/Makefile) At later time, the epel stuff disappeared and with it also the possibility to add python34 as a centos dependency - commit

[vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19

All: Commit 8f2a4ea, Gerrit, https://gerrit.fd.io/r/#/c/6983/ "Add new C API" introduces a dependency on Python 3 and breaks downstream builds for Centos. Unfortunately, neither RHEL nor Centos currently support Python 3. Most VPPers are probably building with EPEL repo so this problem