Looks like an issue in the RPM packaging. The .spec file for the -devel package
includes the line:
%{_includedir}/*
Which will include the dpdk dir if it exists at that build time. The dpdk devel
package is usually built elsewhere so I am surprised the vpp build dir has
this, but I guess something touches the directory on the vpp-devel build. You
should open a bug report at https://jira.fd.io ; I've also cc'ed the person who
has worked the most on the RPM packaging in case he can enlighten us.
Last thing, did you build the packages from source yourself, or use one of our
pre-built packages from a repository?
Thanks,
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of wanghongbo
Sent: Tuesday, November 21, 2017 8:49
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] There was a conflict between
vpp-devel-17.10-release.x86_64.rpm and vpp-dpdk-devel-17.08-vpp2.x86_64.rpm
hi all:
The vpp-devel-17.10-release.x86_64.rpm conflicted with
vpp-dpdk-devel-17.08-vpp2.x86_64 when I installed the rpm package. Should I
used the rpm -force parameter. Thank you very much!
[root@localhost rpm]# ls
Makefile vpp-17.10.0
vpp-api-lua-17.10-release.x86_64.rpm vpp-lib-17.10-release.x86_64.rpm
vpp.spec
RPMS vpp-17.10-release.x86_64.rpm
vpp-api-python-17.10-release.x86_64.rpm vpp-plugins-17.10-release.x86_64.rpm
SOURCES vpp-api-java-17.10-release.x86_64.rpm
vpp-devel-17.10-release.x86_64.rpm vpp.service
[root@localhost rpm]# rpm -ivh *.rpm
Preparing... ################################# [100%]
file /usr/include/dpdk from install of vpp-devel-17.10-release.x86_64
conflicts with file from package vpp-dpdk-devel-17.08-vpp2.x86_64
[root@localhost rpm]# rpm -qa | grep vpp
vpp-dpdk-devel-17.08-vpp2.x86_64
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
