[DRE-maint] Bug#1015327: ruby-mysql2: FTBFS: ERROR: Test "ruby3.0" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory

Tue Jul 19 15:18:39 BST 2022

Source: ruby-mysql2
Version: 0.5.3-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-ruby at lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-mysql2 with ruby3.1 enabled, the build failed.

This does not seem to be related to ruby3.1 though. The C code builds
just fine for ruby3.0 and ruby3.1, but the tests fail due to a bug in
theh script used to run mysql I guess?

Relevant part of the build log (hopefully):
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Install Rubygems integration metadata                                        │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> generating gemspec at /<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0/specifications/mysql2-0.5.3.gemspec
> generating gemspec at /<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/share/rubygems-integration/3.1.0/specifications/mysql2-0.5.3.gemspec
> dh_installchangelogs -pruby-mysql2 /<<PKGBUILDDIR>>/CHANGELOG.md upstream
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Checking Rubygems dependency resolution on ruby3.0                           │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0:/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 ruby3.0 -e gem\ \"mysql2\"
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Run tests for ruby3.0 from debian/ruby-tests.rake                            │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0:/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 ruby3.0 -S rake -f debian/ruby-tests.rake
> ./debian/start_mysqld_and_run.sh ruby3.0 -S rspec
> + mktemp -d
> + MYTEMP_DIR=/tmp/tmp.YafTwmGWe1
> + export MYSQL_UNIX_PORT=/tmp/tmp.YafTwmGWe1/mysql.sock
> + DO_MYSQL_USER=admin
> + DO_MYSQL_PASS=
> + DO_MYSQL_DBNAME=test
> + DO_MYSQL_DATABASE=/test
> + mysqladmin=/usr/bin/mysqladmin --user=admin --socket=/tmp/tmp.YafTwmGWe1/mysql.sock
> + mysql_install_db --no-defaults --datadir=/tmp/tmp.YafTwmGWe1 --force --skip-name-resolve --user=admin
> chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': Permission denied
> Couldn't set an owner to '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool'.
> It must be root, the PAM authentication plugin doesn't work otherwise..
> 
> Installing MariaDB/MySQL system tables in '/tmp/tmp.YafTwmGWe1' ...
> 2022-07-18  8:51:41 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 22. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
> 2022-07-18  8:51:41 0 [ERROR] Plugin 'InnoDB' init function returned error.
> 2022-07-18  8:51:41 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> 2022-07-18  8:51:41 0 [ERROR] Unknown/unsupported storage engine: InnoDB
> 2022-07-18  8:51:41 0 [ERROR] Aborting
> 
> Installation of system tables failed!  Examine the logs in
> /tmp/tmp.YafTwmGWe1 for more information.
> 
> The problem could be conflicting information in an external
> my.cnf files. You can ignore these by doing:
> 
>     shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
> 
> You can also try to start the mysqld daemon with:
> 
>     shell> /usr/sbin/mariadbd --skip-grant-tables --general-log &
> 
> and use the command line tool /usr/bin/mariadb
> to connect to the mysql database and look at the grant tables:
> 
>     shell> /usr/bin/mysql -u root mysql
>     mysql> show tables;
> 
> Try 'mysqld --help' if you have problems with paths.  Using
> --general-log gives you a log in /tmp/tmp.YafTwmGWe1 that may be helpful.
> 
> The latest information about mysql_install_db is available at
> https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
> You can find the latest source at https://downloads.mariadb.org and
> the maria-discuss email list at https://launchpad.net/~maria-discuss
> 
> Please check all of the above before submitting a bug report
> at https://mariadb.org/jira
> 
> rake aborted!
> Command failed with status (1): [./debian/start_mysqld_and_run.sh ruby3.0 -...]
> /<<PKGBUILDDIR>>/debian/ruby-tests.rake:6:in `block in <top (required)>'
> /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed: 

The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/ruby-mysql2_0.5.3-3.1+rebuild1658134272_amd64.log

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2 (in experimental).
If you fail to reproduce, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20220719/57c42ebc/attachment.sig>