Bug#1015328: Starting ruby3.1 transition: important bugs now marked as serious

[Antonio Terceiro]

severity 1015305 serious
severity 1015309 serious
severity 1015310 serious
severity 1015322 serious
severity 1015327 serious
severity 1015328 serious
severity 1015329 serious
severity 1015334 serious
thanks

Hi,

We are about to start the ruby3.1 transition. I will coordinate this
with the release team, and ruby3.1 should be enabled in unstable soon.
Before that, you can test things by installing ruby-all-dev from
experimental.

The following bugs are the current blockers, so the most important ones
to be fixed. If you can, please help by fixing them:

#1015305
puma: FTBFS: ERROR: Test "ruby3.1" failed.
https://bugs.debian.org/1015305

#1015309
ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: actual = YAML.load(regexp.to_yaml)
https://bugs.debian.org/1015309

#1015310
ruby-dataobjects-mysql: FTBFS: chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': Permission denied
https://bugs.debian.org/1015310

#1015322
ruby-kyotocabinet: FTBFS: kccommon.h:19:8: error: expected identifier or ‘(’ before string constant
https://bugs.debian.org/1015322

#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
https://bugs.debian.org/1015327

#1015328
ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed.
https://bugs.debian.org/1015328

#1015329
ruby-prof: FTBFS: ERROR: Test "ruby3.1" failed.
https://bugs.debian.org/1015329

#1015334
ruby-stackprof: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
https://bugs.debian.org/1015334
-------------- 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-grass-devel/attachments/20220912/1469248a/attachment.sig>