On 11/07/2019 10:07, Leon Romanovsky wrote: > On Thu, Jul 11, 2019 at 09:35:59AM +0300, Gal Pressman wrote: >> On 10/07/2019 22:23, Jason Gunthorpe wrote: >>> Benjamin, >>> >>> Can you confirm that something like this fixes these build problems? >>> >>> diff --git a/debian/rules b/debian/rules >>> index 07c9c145ff090c..facb45170eacfc 100755 >>> --- a/debian/rules >>> +++ b/debian/rules >>> @@ -63,6 +63,7 @@ ifneq (,$(filter-out $(COHERENT_DMA_ARCHS),$(DEB_HOST_ARCH))) >>> test -e debian/$$package.install.backup || cp debian/$$package.install debian/$$package.install.backup; \ >>> done >>> sed -i '/mlx[45]/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install >>> + sed -i '/efa/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install >>> endif >>> DESTDIR=$(CURDIR)/debian/tmp ninja -C build-deb install >>> >>> >>> >>> On Wed, Jul 10, 2019 at 11:37:01AM -0000, Debian buildds wrote: >>>> * Source package: rdma-core >>>> * Version: 24.0-1 >>>> * Architecture: armel >>>> * State: failed >>>> * Suite: sid >>>> * Builder: antheil.debian.org >>>> * Build log: https://buildd.debian.org/status/fetch.php?pkg=rdma-core&arch=armel&ver=24.0-1&stamp=1562758620&file=log >>>> >>>> Please note that these notifications do not necessarily mean bug reports >>>> in your package but could also be caused by other packages, temporary >>>> uninstallabilities and arch-specific breakages. A look at the build log >>>> despite this disclaimer would be appreciated however. >> >> Was this error supposed to be reported by travis as well? I'm pretty sure all >> tests passed. > > Did you get any build failure email from debian? I didn't. I didn't, who is supposed to get these?