[PKG-Openstack-devel] Bug#841591: migrate: FTBFS: Tests failures

Lucas Nussbaum lucas at debian.org
Fri Oct 21 13:19:40 UTC 2016


Source: migrate
Version: 0.10.0-5
Severity: serious
Tags: stretch sid
User: debian-qa at 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):
> # work even without python-migrate being installed
> mkdir -p debian/bin
> cp debian/migrate-for-tests debian/bin/migrate
> sed -i "s#REPLACE_THIS_PATH#/<<PKGBUILDDIR>>#" debian/bin/migrate
> # Create a minimalist egg-info, so that "import migrate"
> # works and gets the correct version
> mkdir -p sqlalchemy_migrate-0.10.0.egg-info
> echo "Metadata-Version: 1.1" >sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
> echo "Name: sqlalchemy-migrate" >>sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
> echo "Version: 0.10.0" >>sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
> # Launch the actual tests
> /<<PKGBUILDDIR>>/debian/test.sh
> ===> Preparing MySQL temp folder
> mysql_install_db: [ERROR] unknown option '--force'
> 2016-10-21 01:06:35 [ERROR]   Unrecognized options
> debian/rules:58: 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/migrate_0.10.0-5_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.



More information about the Openstack-devel mailing list