Remove from Noble

[Lucas Kanashiro]

ruby-defaults/1:3.2~ubuntu1 is now in the release pocket (the default is ruby3.2) and ruby3.1 (source and binaries) should be removed from Noble. There is no package depending on it in Noble at the moment:

$ reverse-depends -r noble src:ruby3.1
$ reverse-depends -r noble src:ruby3.1 -a source
Reverse-Build-Depends
=====================
* ruby3.1 (for ruby3.1)

Please remove the ruby3.1 source package and its binaries.

[Christian Ehrhardt  (paelzer)]

I confirmed that there is no dependency left.
At the same time ruby3.2 is indeed in main and the dependency for all ruby components.

[Christian Ehrhardt  (paelzer)]

Interestingly there are three (3) in noble right now:
 ruby3.1 | 3.1.2-7ubuntu4 | noble-updates/universe | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 ruby3.1 | 3.1.2-7ubuntu5 | noble/universe | source, arm64, armhf, i386, ppc64el, riscv64, s390x
 ruby3.1 | 3.1.2-7ubuntu6 | noble-proposed/universe | source, amd64, i386, ppc64el, riscv64, s390x

- 6 is the CVE-2024-3094 rebuild
- 5 is the t64 rebuild
- 4 is a change to fix tests

AFAICS neither of those would hold back a removal for a completed transition.
I'm just back from PTO and it seems beta freeze was delayed, but I need to check ...

[Christian Ehrhardt  (paelzer)]

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 ...

[Christian Ehrhardt  (paelzer)]

Now that things are frozen (and this isn't seeded nor depended on and thereby should not cause further issues) the build in -updates could be removed as well.

Removing packages from noble-updates:
 ruby3.1 3.1.2-7ubuntu4 in noble
  libruby3.1 3.1.2-7ubuntu4 in noble amd64
  libruby3.1 3.1.2-7ubuntu4 in noble arm64
  libruby3.1 3.1.2-7ubuntu4 in noble armhf
  libruby3.1 3.1.2-7ubuntu4 in noble i386
  libruby3.1 3.1.2-7ubuntu4 in noble ppc64el
  libruby3.1 3.1.2-7ubuntu4 in noble riscv64
  libruby3.1 3.1.2-7ubuntu4 in noble s390x
  ruby3.1 3.1.2-7ubuntu4 in noble amd64
  ruby3.1 3.1.2-7ubuntu4 in noble arm64
  ruby3.1 3.1.2-7ubuntu4 in noble armhf
  ruby3.1 3.1.2-7ubuntu4 in noble i386
  ruby3.1 3.1.2-7ubuntu4 in noble ppc64el
  ruby3.1 3.1.2-7ubuntu4 in noble riscv64
  ruby3.1 3.1.2-7ubuntu4 in noble s390x
  ruby3.1-dev 3.1.2-7ubuntu4 in noble amd64
  ruby3.1-dev 3.1.2-7ubuntu4 in noble arm64
  ruby3.1-dev 3.1.2-7ubuntu4 in noble armhf
  ruby3.1-dev 3.1.2-7ubuntu4 in noble i386
  ruby3.1-dev 3.1.2-7ubuntu4 in noble ppc64el
  ruby3.1-dev 3.1.2-7ubuntu4 in noble riscv64
  ruby3.1-dev 3.1.2-7ubuntu4 in noble s390x
  ruby3.1-doc 3.1.2-7ubuntu4 in noble amd64
  ruby3.1-doc 3.1.2-7ubuntu4 in noble arm64
  ruby3.1-doc 3.1.2-7ubuntu4 in noble armhf
  ruby3.1-doc 3.1.2-7ubuntu4 in noble i386
  ruby3.1-doc 3.1.2-7ubuntu4 in noble ppc64el
  ruby3.1-doc 3.1.2-7ubuntu4 in noble riscv64
  ruby3.1-doc 3.1.2-7ubuntu4 in noble s390x
Comment: Transition to ruby3.2 completed (LP: #2059975)
Remove [y|N]? y
1 package successfully removed.