After double checking that we are indeed not (yet) in the freeze I think it would help to clear that now.
Removing packages from noble-proposed: ruby3.1 3.1.2-7ubuntu6 in noble libruby3.1 3.1.2-7ubuntu6 in noble amd64 libruby3.1 3.1.2-7ubuntu6 in noble i386 libruby3.1 3.1.2-7ubuntu6 in noble ppc64el libruby3.1 3.1.2-7ubuntu6 in noble riscv64 libruby3.1 3.1.2-7ubuntu6 in noble s390x ruby3.1 3.1.2-7ubuntu6 in noble amd64 ruby3.1 3.1.2-7ubuntu6 in noble i386 ruby3.1 3.1.2-7ubuntu6 in noble ppc64el ruby3.1 3.1.2-7ubuntu6 in noble riscv64 ruby3.1 3.1.2-7ubuntu6 in noble s390x ruby3.1-dev 3.1.2-7ubuntu6 in noble amd64 ruby3.1-dev 3.1.2-7ubuntu6 in noble i386 ruby3.1-dev 3.1.2-7ubuntu6 in noble ppc64el ruby3.1-dev 3.1.2-7ubuntu6 in noble riscv64 ruby3.1-dev 3.1.2-7ubuntu6 in noble s390x ruby3.1-doc 3.1.2-7ubuntu6 in noble amd64 ruby3.1-doc 3.1.2-7ubuntu6 in noble arm64 ruby3.1-doc 3.1.2-7ubuntu6 in noble armhf ruby3.1-doc 3.1.2-7ubuntu6 in noble i386 ruby3.1-doc 3.1.2-7ubuntu6 in noble ppc64el ruby3.1-doc 3.1.2-7ubuntu6 in noble riscv64 ruby3.1-doc 3.1.2-7ubuntu6 in noble s390x Comment: Transition to ruby3.2 completed (LP: #2059975) Remove [y|N]? y 1 package successfully removed. Removing packages from noble: ruby3.1 3.1.2-7ubuntu5 in noble libruby3.1 3.1.2-7ubuntu5 in noble arm64 libruby3.1 3.1.2-7ubuntu5 in noble armhf libruby3.1 3.1.2-7ubuntu5 in noble i386 libruby3.1 3.1.2-7ubuntu5 in noble ppc64el libruby3.1 3.1.2-7ubuntu5 in noble riscv64 libruby3.1 3.1.2-7ubuntu5 in noble s390x ruby3.1 3.1.2-7ubuntu5 in noble arm64 ruby3.1 3.1.2-7ubuntu5 in noble armhf ruby3.1 3.1.2-7ubuntu5 in noble i386 ruby3.1 3.1.2-7ubuntu5 in noble ppc64el ruby3.1 3.1.2-7ubuntu5 in noble riscv64 ruby3.1 3.1.2-7ubuntu5 in noble s390x ruby3.1-dev 3.1.2-7ubuntu5 in noble arm64 ruby3.1-dev 3.1.2-7ubuntu5 in noble armhf ruby3.1-dev 3.1.2-7ubuntu5 in noble i386 ruby3.1-dev 3.1.2-7ubuntu5 in noble ppc64el ruby3.1-dev 3.1.2-7ubuntu5 in noble riscv64 ruby3.1-dev 3.1.2-7ubuntu5 in noble s390x ruby3.1-doc 3.1.2-7ubuntu5 in noble amd64 ruby3.1-doc 3.1.2-7ubuntu5 in noble arm64 ruby3.1-doc 3.1.2-7ubuntu5 in noble armhf ruby3.1-doc 3.1.2-7ubuntu5 in noble i386 ruby3.1-doc 3.1.2-7ubuntu5 in noble ppc64el ruby3.1-doc 3.1.2-7ubuntu5 in noble riscv64 ruby3.1-doc 3.1.2-7ubuntu5 in noble s390x Comment: Transition to ruby3.2 completed (LP: #2059975) Remove [y|N]? y 1 package successfully removed. Interestingly/Sadly the one in -updates could not be removed. Thanks to Łukasz I didn't went crazy, learning that Steve mentioned such an issue as well. William mentioned that when a series is in "In Development", the -updates pocket is immutable. The expectation is that we we'll be able to remove stuff from -updates when we freeze noble, which hopefully we can do todayish? Keeping the bug open for that last element to be removed ... ** Changed in: ruby3.1 (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059975 Title: Remove from Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.1/+bug/2059975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs