This bug was fixed in the package ruby-memory-profiler - 1.1.0-2 Sponsored for Nishit Majithia (0xnishit)
--------------- ruby-memory-profiler (1.1.0-2) unstable; urgency=medium * Team upload. * d/ruby-tests.rake: skip tests failing with ruby3.1 in autopkgtest -- Lucas Kanashiro <[email protected]> Tue, 28 Jan 2025 11:20:09 -0300 ruby-memory-profiler (1.1.0-1) unstable; urgency=medium * Team upload. * New upstream version 1.1.0 * Refresh patches -- Lucas Kanashiro <[email protected]> Mon, 27 Jan 2025 06:58:10 -0300 ruby-memory-profiler (1.0.1-4) unstable; urgency=medium * Team upload. * d/p/Fix-tests.patch: fix FTBFS with Ruby 3.3 * Declare compliance with Debian Policy 4.7.0 -- Lucas Kanashiro <[email protected]> Mon, 23 Dec 2024 16:12:50 -0300 ** Changed in: ruby-memory-profiler (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ruby-memory-profiler (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2132326 Title: Sync ruby-memory-profiler from Debian unstable for resolute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-memory-profiler/+bug/2132326/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
