Do not support ruby 3.2
Bug #2052556 reported by
Lucas Kanashiro
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-eb (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
ruby-eb/2.6-4build2 FTBFS with ruby 3.2. The upstream project is apparently dead:
https:/
We have the same upstream release since Trusty! I do not foresee any fix from upstream. To also avoid having unmaintained code in the archive I believe the best way out of this is removing it from Noble, allowing the ruby 3.2 transition to move on.
Since this is a leaf package, the removal is straightforward:
$ reverse-depends src:ruby-eb
No reverse dependencies found
$ reverse-depends src:ruby-eb -a source
No reverse dependencies found
So please, remove src:ruby-eb and its binary from Noble.
To post a comment you must log in.
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)