Source: networking-mlnx Version: 1:9.0.0~b1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +------------------------------------------------------------------------------+ > | Install package build dependencies > | > +------------------------------------------------------------------------------+ > > > Setup apt archive > ----------------- > > Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, > openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), > python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, > python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), > python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= > 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), > python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, > python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), > python-testresources, python-testscenarios, python-testtools (>= 1.4.0), > python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= > 0.0.18) > Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, > openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), > python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, > python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), > python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= > 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), > python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, > python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), > python-testresources, python-testscenarios, python-testtools (>= 1.4.0), > python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= > 0.0.18) > dpkg-deb: building package 'sbuild-build-depends-networking-mlnx-dummy' in > '/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive/sbuild-build-depends-networking-mlnx-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-networking-mlnx-dummy > dpkg-scanpackages: info: Wrote 1 entries to output Packages file. > Ign:1 copy:/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive ./ InRelease > Get:2 copy:/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive ./ Release [963 B] > Ign:3 copy:/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive ./ Release.gpg > Get:4 copy:/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive ./ Sources [620 B] > Get:5 copy:/<<BUILDDIR>>/resolver-mNH6jQ/apt_archive ./ Packages [703 B] > Fetched 2286 B in 0s (210 kB/s) > Reading package lists... > W: No sandbox user '_apt' on the system, can not drop privileges > Reading package lists... > > Install networking-mlnx build dependencies (apt-based resolver) > --------------------------------------------------------------- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-networking-mlnx-dummy : Depends: python-neutron (>= > 2:9.0.0~rc1) but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2016/11/18/networking-mlnx_9.0.0~b1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.