I checked this case confirming all you stated in the removal request.
LGTM
Furthermore the use-case of this explains why it might have been abandoned.
It is a less common (except in Japan) cd-rom book type.
And cd-roms have gotten way more rare these days right :-)
This does not remove all ability to access those.
There are eblook and a few go bindings left. But TBH, those just as much depend on an never changed library from src:eb. So there might be more cleanup needed down the road, yet OTOH no need to take things away if not being a problem.
But here blocking ruby 3.2 I think it is justifiable.
Removing packages from noble:
ruby-eb 2.6-4build2 in noble
ruby-eb 2.6-4build2 in noble amd64
ruby-eb 2.6-4build2 in noble arm64
ruby-eb 2.6-4build2 in noble armhf
ruby-eb 2.6-4build2 in noble ppc64el
ruby-eb 2.6-4build2 in noble riscv64
ruby-eb 2.6-4build2 in noble s390x
Comment: not compatible with ruby 3.2 (LP: #2052556)
I checked this case confirming all you stated in the removal request.
LGTM
Furthermore the use-case of this explains why it might have been abandoned.
It is a less common (except in Japan) cd-rom book type.
And cd-roms have gotten way more rare these days right :-)
This does not remove all ability to access those.
There are eblook and a few go bindings left. But TBH, those just as much depend on an never changed library from src:eb. So there might be more cleanup needed down the road, yet OTOH no need to take things away if not being a problem.
But here blocking ruby 3.2 I think it is justifiable.
Removing packages from noble:
ruby-eb 2.6-4build2 in noble
ruby-eb 2.6-4build2 in noble amd64
ruby-eb 2.6-4build2 in noble arm64
ruby-eb 2.6-4build2 in noble armhf
ruby-eb 2.6-4build2 in noble ppc64el
ruby-eb 2.6-4build2 in noble riscv64
ruby-eb 2.6-4build2 in noble s390x
Comment: not compatible with ruby 3.2 (LP: #2052556)