Source: gitano Version: 0.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): > Running step "GIVEN a standard instance" > Running step "WHEN testinstance adminkey runs config gitano-admin set > project.archived true" > Running step "THEN server-side gitano-admin.git file cgitrc contains > hide=1" > Running scenario Pushing shallow history > DATADIR is /tmp/tmprTY8Oy/Pushing_shallow_history/datadir > HOME for tests is /tmp/tmprTY8Oy/Pushing_shallow_history/datadir/HOME > Running step "GIVEN a standard instance" > Running step "WHEN testinstance, using adminkey, clones gitano-admin.git > as local-shallow with depth 1" > Running step "WHEN testinstance adminkey runs create remote-shallow.git" > Running step "WHEN testinstance adminkey runs config remote-shallow.git > set git.receive.shallowUpdate true" > Running step "WHEN testinstance, using adminkey, pushes local-shallow to > remote-shallow.git" > Running step "THEN server-side remote-shallow.git file shallow exists" > Failed scenarios: > - Keyrings can gain and lose keys > ERROR: Test suite FAILED in 1 scenarios > Makefile:183: recipe for target '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/gitano_0.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.
