In cherry picking some fixes back to stable/1901, I've found that the builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found. Which looks like there is some upstream issue with a dependency no longer being available for libboost. Digging deeper, it would appear that we are tripping on SUSE_NAME=Tumbleweed: https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131 ifeq ($(OS_ID),opensuse) ifeq ($(SUSE_NAME),Tumbleweed) RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0 libboost_thread1_68_0-devel-1.68.0 gcc RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv endif ifeq ($(SUSE_ID),15.0) RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6 else RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6 RPM_SUSE_PYTHON_DEPS += python-virtualenv endif endif So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and being asked to install the wrong packages even though they are OSLEAP 15 boxes. Note: this same Makefile fragment is identical on master where the corresponding jobs are succeeding. Do any of the OpenSuse folks have ideas as to what could be happening here? Ed
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366 Mute This Topic: https://lists.fd.io/mt/30154873/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
