rubygems ftbfs in the jammy release pocket

This bug was fixed in the package rubygems - 3.3.15-1

---------------
rubygems (3.3.15-1) unstable; urgency=medium

  * New upstream release.
  * Add ruby-test-unit (>= 3.3.9~) as b-d (Closes: 1008361) (LP: #1976264)
  * d/ruby-tests.skip: add more tests trying to execute commands on the system
  * Declare compliance with Debian Policy 4.6.1

 -- Lucas Kanashiro <email address hidden> Thu, 02 Jun 2022 16:23:32 -0300

Hello Matthias, or anyone else affected,

Accepted rubygems into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rubygems/3.3.5-2ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

As you can see here

https://launchpad.net/ubuntu/+source/rubygems/3.3.5-2ubuntu1/+build/23839164

the package built fine, so the FTBFS was fixed. I tagged this bug as block-proposed so we avoid triggering an update to users just because of this. Once we have a new update in Jammy we land this in the -updates pocket.