Summary: | dev-ruby/rmagick-2.16.0 fails to emerge with imagemagick 7.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steven Green <steven> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jstein, rossi.f, steven |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/rmagick/rmagick/issues/256 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 581800 | ||
Attachments: |
Build Log
emerge --info |
Description
Steven Green
2017-05-25 15:21:45 UTC
Created attachment 474290 [details]
emerge --info
have you installed media-gfx/imagemagick? you can search for files on http://www.portagefilelist.de Yes imagemagick is installed. After the recent update to version 7, an emerge @preserved-rebuild wants to rebuild this Ruby gem which is failing because imagemagick 7 must have changed some of its API, specifically MagickWand. I have locked rmagick to imagemagick-6* for now. Obviously not a long-term solution, but imagemagick-7 appears to require a fairly massive change in the rmagick code and it is not very actively maintained at the moment. upstream is working on supporting imagemagick-7 from version 4.1.0, see also the related issue https://github.com/rmagick/rmagick/issues/256 In portage we have some packages like rmagick which still depends on imagemagick-6 and other software that support only imagemagick-7 (e.g. octave) so it's a mess for the final user. They already have a release candidate 4.1.0-rc2 which seems to work with imagemagick-7, what about adding that to portage? (In reply to Fabio Rossi from comment #5) > upstream is working on supporting imagemagick-7 from version 4.1.0, see also > the related issue https://github.com/rmagick/rmagick/issues/256 > > In portage we have some packages like rmagick which still depends on > imagemagick-6 and other software that support only imagemagick-7 (e.g. > octave) so it's a mess for the final user. They already have a release > candidate 4.1.0-rc2 which seems to work with imagemagick-7, what about > adding that to portage? We try to avoid rc candidates from upstream in the ruby project. Given the overall progress of the porting effort I would expect the 4.1.0 release not to be very far off. Let's give it a few more weeks. (In reply to Hans de Graaff from comment #6) > We try to avoid rc candidates from upstream in the ruby project. Given the > overall progress of the porting effort I would expect the 4.1.0 release not > to be very far off. Let's give it a few more weeks. ok, thanks. In the meantime I have tested installing rmagick 4.1.0_rc2 in my personal overlay and works with imagemagick-7 (at least for my needs where rmagick is used by redmine). The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5bc0c40e167e5a47b9291cb72045699e1e00330 commit a5bc0c40e167e5a47b9291cb72045699e1e00330 Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2020-03-28 07:05:09 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2020-03-28 07:05:35 +0000 dev-ruby/rmagick: add 4.1.0 Closes: https://bugs.gentoo.org/619684 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/rmagick/Manifest | 1 + dev-ruby/rmagick/rmagick-4.1.0.ebuild | 64 +++++++++++++++++++++++++++++++++++ 2 files changed, 65 insertions(+) |