[DRE-maint] Bug#841543: ruby-carrierwave: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Lucas Nussbaum]

Source: ruby-carrierwave
Version: 0.10.0+gh-2
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):
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
>    dh_testroot -O--buildsystem=ruby
>    dh_prep -O--buildsystem=ruby
>    debian/rules override_dh_auto_install
> make[1]: Entering directory '/<<BUILDDIR>>/ruby-carrierwave-0.10.0+gh'
> chmod +x debian/start_mysqld_and_auto_install.sh
> debian/start_mysqld_and_auto_install.sh
> mysql_install_db: [ERROR] unknown option '--force'
> 2016-10-21 01:26:27 [ERROR]   Unrecognized options
> debian/rules:19: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 1

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/ruby-carrierwave_0.10.0+gh-2_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.