Paul, Good first thing to check... I've pushed https://gerrit.fd.io/r/#/c/17916/
to cause the opensuse jobs to cat the /etc/os-release as you suggested, and rechecked: https://gerrit.fd.io/r/#/c/17884/ to see what happens :) Ed On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra < pvi...@vinciconsulting.com> wrote: > Can we confirm that they are truly osleap15? > > An osleap box reports correctly for me: > > docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash > > *ee4938c281e4:/ #* cat /etc/os-release > > NAME="openSUSE Leap" > > VERSION="15.0 Beta" > > ID="opensuse" > > ID_LIKE="suse" > > VERSION_ID="15.0" > > PRETTY_NAME="openSUSE Leap 15.0 Beta" > > ANSI_COLOR="0;32" > > CPE_NAME="cpe:/o:opensuse:leap:15.0" > > BUG_REPORT_URL="https://bugs.opensuse.org"; > HOME_URL="https://www.opensuse.org/"; > > On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke <hagb...@gmail.com> wrote: > >> 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/1594641 >> Group Owner: vpp-dev+ow...@lists.fd.io >> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [ >> pvi...@vinciconsulting.com] >> -=-=-=-=-=-=-=-=-=-=-=- >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12368): https://lists.fd.io/g/vpp-dev/message/12368 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] -=-=-=-=-=-=-=-=-=-=-=-
