Your message dated Thu, 26 Jan 2023 23:37:43 +0000 with message-id <e1plbon-00ba8i...@fasolo.debian.org> and subject line Bug#1015310: fixed in ruby-dataobjects-mysql 0.10.17-4 has caused the Debian Bug report #1015310, regarding ruby-dataobjects-mysql: FTBFS: chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': Permission denied to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-dataobjects-mysql Version: 0.10.17-3+rebuild1658134000 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-dataobjects-mysql with ruby3.1 enabled, the build failed. The failure does not seem related to ruby3.1, though. Relevant part of the build log (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > chmod +x debian/start_mysqld_and_auto_install.sh > debian/start_mysqld_and_auto_install.sh > 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.95tQLpTsSm' ... > 2022-07-18 8:46:59 0 [Warning] InnoDB: Retry attempts for writing partial > data failed. > 2022-07-18 8:46:59 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:46:59 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2022-07-18 8:46:59 0 [ERROR] InnoDB: Could not set the file size of > './ibdata1'. Probably out of disk space > 2022-07-18 8:46:59 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:46:59 0 [ERROR] Plugin 'InnoDB' init function returned error. > 2022-07-18 8:46:59 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE > ENGINE failed. > 2022-07-18 8:46:59 0 [ERROR] Unknown/unsupported storage engine: InnoDB > 2022-07-18 8:46:59 0 [ERROR] Aborting > > Installation of system tables failed! Examine the logs in > /tmp/tmp.95tQLpTsSm 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.95tQLpTsSm 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 > > make[1]: *** [debian/rules:13: override_dh_auto_install] Error 1 The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/ruby-dataobjects-mysql_0.10.17-3+rebuild1658134000_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
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: ruby-dataobjects-mysql Source-Version: 0.10.17-4 Done: Daniel Leidert <dleid...@debian.org> We believe that the bug you reported is fixed in the latest version of ruby-dataobjects-mysql, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert <dleid...@debian.org> (supplier of updated ruby-dataobjects-mysql package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 27 Jan 2023 00:01:15 +0100 Source: ruby-dataobjects-mysql Architecture: source Version: 0.10.17-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Daniel Leidert <dleid...@debian.org> Closes: 1015310 Changes: ruby-dataobjects-mysql (0.10.17-4) unstable; urgency=medium . * Team upload. * d/ruby-tests.rake: Only run tests in autopkgtest environment for now. Mysqld won't start in sbuild environment due to overlayfs usage #1009290 (closes: #1015310). * d/rules (override_dh_auto_install): Don't run mysqld test script. Checksums-Sha1: 35f36f996448a973fbdb1d1734298defd6057bde 2360 ruby-dataobjects-mysql_0.10.17-4.dsc 2c71d927b450b79df02a23ba27504270cfde4a36 6032 ruby-dataobjects-mysql_0.10.17-4.debian.tar.xz 919e19396f0473c768d34aa41319cd4c93c5e750 11273 ruby-dataobjects-mysql_0.10.17-4_amd64.buildinfo Checksums-Sha256: 6c8fb69852897aae25c3ff163759ee33b6a88cfb9c458ff046199935e5374a3a 2360 ruby-dataobjects-mysql_0.10.17-4.dsc 6df93047732acd959fd9f1a455fd4306b69e5a74b34b49699d1748166838361d 6032 ruby-dataobjects-mysql_0.10.17-4.debian.tar.xz f49b1943499e8d23ecc5553d83977a5861714f1a8d9045fbd9b4642fa4fd63ba 11273 ruby-dataobjects-mysql_0.10.17-4_amd64.buildinfo Files: 3bfa75bd825de0c01df523a7a21ddfcd 2360 ruby optional ruby-dataobjects-mysql_0.10.17-4.dsc 8b7e2815419e5ab57df857bc53b978c3 6032 ruby optional ruby-dataobjects-mysql_0.10.17-4.debian.tar.xz 9d562d5ce6456981e9aa89f4555f1922 11273 ruby optional ruby-dataobjects-mysql_0.10.17-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPTB2QACgkQS80FZ8KW 0F2jfhAA0XX8/ORPCLYZ4HjQjWQQIW3eC7f3La+Xzj43rmEwX7h+xlZb5YRmjMoh IRuTa5rS30P/3Fn+6qkfmkx/NzFVejQfvv3eowHAhRZaqIwMcl44WFkoOUdtrdsC De2lAQxjtHx/bLw/F8XjwFxTUZRZ5D80H4Sfw3wi12WFCAIS+JyraYrIe2KDknY8 knLVIEfrXvlav4BNt6/KQD0guO6W8yfsGamIb30kUSv1+UwPJTCL6T1+oNVZG4F9 dGF1xtRBiIOU/67Y+oUOsjFb7UC41zpj4y7AHLyBlRy4eK8lnnUiRf2VAqnuL2zw tQMOsc62gFqMtZ0+FKcZibrb3GEZCC42qW/nRf5CW9cEd2tyiCkMtkeYZ7SQZYqd yYCquUXeB8hectqFRiYF3sAuGkDmtIyT9ulRVpH19Jgz+Ls8b+9VOpTzC6wrL7B1 dzViZb9yEtTWbjy3rUhxZeFfJRxPsI3YfZfSLHwditHRj1VbXRQCZRxMJxk3/jL1 aVHVTJ9TCIcZdxF8u7X8JwBmg9vUIrM0JPrjroyLZTjnJzYe/XdxFFV+obJy11AF x+2vPwaFv2JgWaVLmiINK+/hGbH1xOU60AH0kUMZjjK5yEFwRn38A108m5VMGT39 K6BCpO+XPOihz1gUT77whZTvMebG4nRCIcBuWbUL8ywTijcPkZc= =BkcO -----END PGP SIGNATURE-----
--- End Message ---
