[PKG-Openstack-devel] Bug#844827: swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4)

[Lucas Nussbaum]

Source: swift
Version: 2.10.0-3
Severity: serious
Tags: stretch sid
User: debian-qa at 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-exec, dh-python, dh-systemd, openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, python-nosexcover, python-openssl, python-openstack.nose-plugin, python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> Filtered Build-Depends: debhelper (>= 9), dh-exec, dh-python, dh-systemd, openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, python-nosexcover, python-openssl, python-openstack.nose-plugin, python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> dpkg-deb: building package 'sbuild-build-depends-swift-dummy' in '/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive/sbuild-build-depends-swift-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override file:
> dpkg-scanpackages: warning:   sbuild-build-depends-swift-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive ./ Sources [622 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-Rc7xQs/apt_archive ./ Packages [702 B]
> Fetched 2287 B in 0s (203 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install swift 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-swift-dummy : Depends: python-xattr (>= 0.4) 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/swift_2.10.0-3_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.