Yeah :-/ It was bad for a while even with 3.1 and I agree we have - for
now - to follow Debian with the removal.
0.6 to 0.23 sounds like quite a jump.
But if that happens to be completed before more intense freezes and this being
a tail package (and not changing behavior or many others) I think it would be
great to sync the new version in before noble is released. ... "if it is
available in time"
Until then, ack to the removal. We only have 0.6.0-2 in noble, nothing
in proposed. And it only has a binary of the same name.
Removing packages from noble:
ruby-gruff 0.6.0-2 in noble
ruby-gruff 0.6.0-2 in noble amd64
ruby-gruff 0.6.0-2 in noble arm64
ruby-gruff 0.6.0-2 in noble armhf
ruby-gruff 0.6.0-2 in noble i386
ruby-gruff 0.6.0-2 in noble ppc64el
ruby-gruff 0.6.0-2 in noble riscv64
ruby-gruff 0.6.0-2 in noble s390x
Comment: not compatible with ruby-rmagick/5.3.0 (and thereby indirectly with
ruby 3.2) (LP: #2055344)
Remove [y|N]? y
1 package successfully removed.
** Changed in: ruby-gruff (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/2055344
Title:
Do not support ruby-rmagick 5.3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gruff/+bug/2055344/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
