Your message dated Fri, 21 Jan 2022 21:33:53 +0000
with message-id <[email protected]>
and subject line Bug#1002087: fixed in ruby-mysql2 0.5.3-3.1
has caused the Debian Bug report #1002087,
regarding ruby-mysql2: FTBFS: ERROR: Test "ruby2.7" failed: expected
Mysql2::Error with message matching /Lost connection to MySQL server/, got
#<Mysql2::Error::ConnectionError: Lost connection to server during query> with
backtrace:
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 [email protected]
immediately.)
--
1002087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002087
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-mysql2
Version: 0.5.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> expected Mysql2::Error with message matching /Lost connection to MySQL
> server/, got #<Mysql2::Error::ConnectionError: Lost connection to server
> during query> with backtrace:
> # ./lib/mysql2/client.rb:131:in `_query'
> # ./lib/mysql2/client.rb:131:in `block in query'
> # ./lib/mysql2/client.rb:130:in `handle_interrupt'
> # ./lib/mysql2/client.rb:130:in `query'
> # ./spec/mysql2/client_spec.rb:575:in `block (4 levels) in <top
> (required)>'
> # ./spec/mysql2/client_spec.rb:574:in `block (3 levels) in <top
> (required)>'
> # ./spec/mysql2/client_spec.rb:574:in `block (3 levels) in <top
> (required)>'
>
> Finished in 5.35 seconds (files took 0.09954 seconds to load)
> 315 examples, 1 failure, 6 pending
>
> Failed examples:
>
> rspec ./spec/mysql2/client_spec.rb:566 # Mysql2::Client#query should detect
> closed connection on query read error
>
> Randomized with seed 37489
>
> + cleanup
> + /usr/bin/mysqladmin --user=user42 --socket=/tmp/tmp.VABRYgsgta/mysql.sock
> shutdown
> 2021-12-20 19:03:32 0 [Note] /usr/sbin/mysqld (initiated by: user42[user42] @
> localhost []): Normal shutdown
> 2021-12-20 19:03:32 0 [Note] Event Scheduler: Purging the queue. 0 events
> 2021-12-20 19:03:32 0 [Note] InnoDB: FTS optimize thread exiting.
> 2021-12-20 19:03:32 0 [Note] InnoDB: Starting shutdown...
> 2021-12-20 19:03:32 0 [Note] InnoDB: Dumping buffer pool(s) to
> /tmp/tmp.VABRYgsgta/ib_buffer_pool
> 2021-12-20 19:03:32 0 [Note] InnoDB: Buffer pool(s) dump completed at 211220
> 19:03:32
> 2021-12-20 19:03:32 0 [Note] InnoDB: Removed temporary tablespace data file:
> "ibtmp1"
> 2021-12-20 19:03:32 0 [Note] InnoDB: Shutdown completed; log sequence number
> 168856; transaction id 479
> 2021-12-20 19:03:32 0 [Note] /usr/sbin/mysqld: Shutdown complete
>
> + rm -rf /tmp/tmp.VABRYgsgta
> rake aborted!
> Command failed with status (1): [./debian/start_mysqld_and_run.sh ruby2.7
> -...]
> /<<PKGBUILDDIR>>/debian/ruby-tests.rake:6:in `block in <top (required)>'
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `<top
> (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/ruby-mysql2_0.5.3-3_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!
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
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-mysql2
Source-Version: 0.5.3-3.1
Done: Paul Gevers <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ruby-mysql2, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers <[email protected]> (supplier of updated ruby-mysql2 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 21 Jan 2022 21:31:08 +0100
Source: ruby-mysql2
Architecture: source
Version: 0.5.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<[email protected]>
Changed-By: Paul Gevers <[email protected]>
Closes: 1002087
Changes:
ruby-mysql2 (0.5.3-3.1) unstable; urgency=medium
.
* Error message changed with mariadb-10.6 (Closes: #1002087)
Checksums-Sha1:
b6a66923f2f4aa20d25cfdc26a04a9c3695d1288 1961 ruby-mysql2_0.5.3-3.1.dsc
366517cb40f8f0294eece1bcb636674bd6446e4d 8480
ruby-mysql2_0.5.3-3.1.debian.tar.xz
Checksums-Sha256:
e2207d2e6a0aece1e41901fc793eb554e3a01d87f96e7b47a0c87ad273729565 1961
ruby-mysql2_0.5.3-3.1.dsc
2858bff5dd676d4efb76db34dd0b3b779a93cdfe1184283fea74bcf657d3317f 8480
ruby-mysql2_0.5.3-3.1.debian.tar.xz
Files:
e9577a72e7c42ea0f465224f58bad42a 1961 ruby optional ruby-mysql2_0.5.3-3.1.dsc
3db9224b8422992acab95d997e94b1f4 8480 ruby optional
ruby-mysql2_0.5.3-3.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmHrIi4ACgkQnFyZ6wW9
dQoXwAgAsky/MvTDq0DbSmdyJP2hlJf65NG/9J5/hZ1oqjofgXydaZw49TO4BJSL
eD7//7QTH0Qt+MaPQ0d8KuKtiV4kqOlOJKXCJyevxgoMf5TJbKvVE3QJdp0uVhTt
7nn5VvqzcdoxZAfHdArRh+VdhlLGCNHaMAKSHffZDOQ4+cNsU3DWlPqtrcXX8eeK
+tMMFM8t+LF+AeANczKAoPgaf2wuwEMJ7U9CcwIRAjoTpgKFhfoznbrmGTO8eR2i
qsw9pOjnwsY2KRfOXrigZZidSqz04GhqQTtNzzXZwBIiAGKfP+6z4eY4cZY4+g5E
M5QKn78AUIJpQE41Vc4Qow2mmeIhmA==
=2rJm
-----END PGP SIGNATURE-----
--- End Message ---
