Source: datalad Version: 0.3.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161021 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): > > Installed /<<PKGBUILDDIR>> > Processing dependencies for datalad==0.3.1 > Searching for gitdb2>=2.0.0 > Reading https://pypi.python.org/simple/gitdb2/ > Download error on https://pypi.python.org/simple/gitdb2/: [Errno 111] > Connection refused -- Some packages may not be found! > Couldn't find index page for 'gitdb2' (maybe misspelled?) > Scanning index of all packages (this may take a while) > Reading https://pypi.python.org/simple/ > Download error on https://pypi.python.org/simple/: [Errno 111] Connection > refused -- Some packages may not be found! > No local packages or working download links found for gitdb2>=2.0.0 > error: Could not find suitable distribution for > Requirement.parse('gitdb2>=2.0.0') > Makefile:16: recipe for target 'bin' failed > make[2]: *** [bin] Error 1 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules:27: recipe for target 'override_dh_auto_test' failed If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/datalad_0.3.1-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.
