Something caught my attention after installing Fedora 22 (which I sadly have seen in older Fedora releases as well). I believe this to be a bug and thus would like to discuss a solution: /usr/share/ghostscript/9.15/Resource/CMap/<poppler links> /usr/share/ghostscript/9.16/Resource/CMap/<empty> Please explain, how ghostscript 9.16 (which clearly knows only about ghostscript 9.16 (and the paths 9.16)) find the correct CMap files when they are stored in 9.15 ?
The poppler data needs to be updated to the right location for 9.16.
OK. Tim, can we do something to make this more robust in the future? options off the top of my head include: * make the data dir that ghostscript uses unversioned (don't need to worry about supporting multiple ghostscripts being installed, so we?) * similar to ^^, add (and use) some unversioned dir to gs search path * give you commit access to poppler-data so that you can bump-n-build it whenever you bump ghostscript version * some_better_idea
poppler-data-0.4.7-4.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/poppler-data-0.4.7-4.fc22
Probably the add-unversion-dir-to-search-path is the better option. jgrulich: what do you think?
Package poppler-data-0.4.7-4.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing poppler-data-0.4.7-4.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10416/poppler-data-0.4.7-4.fc22 then log in and leave karma (feedback).
poppler-data-0.4.7-4.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.