fi \ done convert: no images defined `gnome-mime-chemical_16.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_22.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_24.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_32.png' @ error/convert.c/ConvertImageCommand/3273. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-20190726-194018 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * emerge -qpvO sci-chemistry/chemical-mime-data [ebuild N ] sci-chemistry/chemical-mime-data-0.1.94-r3
Created attachment 584800 [details] emerge-info.txt
Created attachment 584802 [details] emerge-history.txt
Created attachment 584804 [details] environment
Created attachment 584806 [details] etc.portage.tbz2
Created attachment 584808 [details] logs.tbz2
Created attachment 584810 [details] sci-chemistry:chemical-mime-data-0.1.94-r3:20190727-072116.log
Created attachment 584812 [details] temp.tbz2
Can confirm this problem,been around for a while,has the effect of closing off some programs selected by kde-meta.
(In reply to Geoff Madden from comment #8) > Can confirm this problem,been around for a while,has the effect of closing > off some programs selected by kde-meta. ... which breaks installation instead of simple emerge kde-meta, I've spent two days writing individual kde packages to emerge command :-( and because I've messed with the png flag, I thought I broke something myself and didn't look here before spending some more time rebuilding half of the system to make sure everything is right with graphic files processing guys, if fixing this is beyond your capability (would take more time than available or whatever), please, could you at least temporarily drop the kalzium dependecy from kdeedu, so that one unimportant toy app doesn't break the whole desktop?
This bug is caused by the fact that the imagemagick's 'convert' tool internally calls 'inkscape' (which definitely shouldn't) to convert an image from the SVG format. Just install inkscape, and the bug will be gone...
be warned that inkscape version 1.0_beta1 won't compile ninja fails at 1024/1024 with the message a sub command failed. but version 0.94 does compile up ok
I have imagemagick with the svg flag enabled and inkscape installed. This package failing to compile is blocking kde-apps-meta for me.
When trying to install kde-apps/kde-apps-meta I kept running into these errors: convert: no images defined `gnome-mime-chemical_16.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_22.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_24.png' @ error/convert.c/ConvertImageCommand/3273. convert: no images defined `gnome-mime-chemical_32.png' @ error/convert.c/ConvertImageCommand/3273. As others suggested, so I went to install the previous version package: emerge "="sci-chemistry/chemical-mime-data-0.1.94-r2 The quotations is because I'm using zsh, but besides that in the asked me to add this use flag: media-gfx/imagemagick xml Afterwards it installed successfully.
(In reply to Darwin from comment #12) > I have imagemagick with the svg flag enabled and inkscape installed. This > package failing to compile is blocking kde-apps-meta for me. See if my response works for you.
(In reply to Michael T. B from comment #13) > When trying to install kde-apps/kde-apps-meta I kept running into these > errors: > > convert: no images defined `gnome-mime-chemical_16.png' @ > error/convert.c/ConvertImageCommand/3273. > convert: no images defined `gnome-mime-chemical_22.png' @ > error/convert.c/ConvertImageCommand/3273. > convert: no images defined `gnome-mime-chemical_24.png' @ > error/convert.c/ConvertImageCommand/3273. > convert: no images defined `gnome-mime-chemical_32.png' @ > error/convert.c/ConvertImageCommand/3273. > > As others suggested, so I went to install the previous version package: > > emerge "="sci-chemistry/chemical-mime-data-0.1.94-r2 > > The quotations is because I'm using zsh, but besides that in the asked me to > add this use flag: > > media-gfx/imagemagick xml > > Afterwards it installed successfully. emerge media-gfx/imagemagick with USE='xml' first fixes the problem for me. The ebuild should depend on media-gfx/imagemagick with the useflag 'xml'. This should fix the bug.
it already depends on imagemagick with xml USE flag
I just ran into this. It seems to me the dependency is broken behind the scenes. This: || ( gnome-base/librsvg media-gfx/imagemagick[xml,png,svg] ) is happy with imagemagick[-xml] as long as you have libsrvg installed. Which you probably have on a desktop. And then the build process goes along, expects [xml], gets [-xml] and drops the ball.
