We do have it as a dependency because we want to make sure the plugin still builds. However, given that most of those who use tls use the openssl engine, we might consider not having mbedtls as a dependency for the packages that we push to packagecloud ...
On a separate note, what centos do we run in the container? It seems that even python3 has some dependency errors. I guess that once we align the vagrant version with it, things should just work. Florin > On Apr 11, 2019, at 1:55 PM, Ed Kern (ejk) <e...@cisco.com> wrote: > > > >> On Apr 11, 2019, at 2:22 PM, Florin Coras <fcoras.li...@gmail.com >> <mailto:fcoras.li...@gmail.com>> wrote: >> >> Are we building rpms on a host that has mbedtls installed? > > Yes the centos container has mbedtls installed….has for quite some time since > it is a listed > prerequisite straight out of the Makefile. > > Ed > > > > >> Just uninstalling it should disable the tlsmbedtls plugin, which is what we >> pretty much want. >> >> Florin >> >>> On Apr 11, 2019, at 1:00 PM, Dave Wallace <dwallac...@gmail.com >>> <mailto:dwallac...@gmail.com>> wrote: >>> >>> Tom/Billy, >>> >>> Do you know what the current status is with the VPP rpm's on master/19.04? >>> >>> I'm trying to install the VPP 19.04 packages from packagecloud.io >>> <http://packagecloud.io/> on a centos7 Vagrant/virtualbox VM (using >>> .../vpp/extras/vagrant/Vagrantfile) to verify that the packages are >>> correct. The 19.01 packages install fine, but the 19.04 and master >>> packages fail with the following dependency errors: >>> >>> --> Finished Dependency Resolution >>> Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) >>> Requires: libmbedtls.so.10()(64bit) >>> Error: Package: vpp-devel-19.04-rc1~b4.x86_64 (fdio_1904) >>> Requires: /usr/bin/python3 >>> Error: Package: vpp-19.04-rc1~b4.x86_64 (fdio_1904) >>> Requires: /usr/bin/python3 >>> Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) >>> Requires: libmbedx509.so.0()(64bit) >>> Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) >>> Requires: libmbedcrypto.so.2()(64bit) >>> You could try using --skip-broken to work around the problem >>> You could try running: rpm -Va --nofiles --nodigest >>> >>> Thanks, >>> -daw- >>> -=-=-=-=-=-=-=-=-=-=-=- >>> Links: You receive all messages sent to this group. >>> >>> View/Reply Online (#12768): https://lists.fd.io/g/vpp-dev/message/12768 >>> <https://lists.fd.io/g/vpp-dev/message/12768> >>> Mute This Topic: https://lists.fd.io/mt/31034762/675152 >>> <https://lists.fd.io/mt/31034762/675152> >>> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> >>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub >>> <https://lists.fd.io/g/vpp-dev/unsub> [fcoras.li...@gmail.com >>> <mailto:fcoras.li...@gmail.com>] >>> -=-=-=-=-=-=-=-=-=-=-=- >> >> -=-=-=-=-=-=-=-=-=-=-=- >> Links: You receive all messages sent to this group. >> >> View/Reply Online (#12769): https://lists.fd.io/g/vpp-dev/message/12769 >> <https://lists.fd.io/g/vpp-dev/message/12769> >> Mute This Topic: https://lists.fd.io/mt/31034762/675649 >> <https://lists.fd.io/mt/31034762/675649> >> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> >> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub >> <https://lists.fd.io/g/vpp-dev/unsub> [e...@cisco.com >> <mailto:e...@cisco.com>] >> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12772): https://lists.fd.io/g/vpp-dev/message/12772 Mute This Topic: https://lists.fd.io/mt/31034762/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
