Description of problem: The official build of impressive contains unneeded dependency: Requires: pdftk < 2.0 This dependency blocks the pdftk update. I could not find any good reason for such dependency. Version-Release number of selected component (if applicable): impressive-0.10.4-2.fc20 Expected results: The given dependency should be removed.
Now this is funny for several reasons: - There is no pdftk update in Fedora. - What is worse, pdftk is even retired in F20 and rawhide. Not by my choice, but (according to pftk maintainers) because of licensing issues with pdftk 2 (or rather its dependency iText). - Therefore, I removed the pdftk dependency for impressive in rawhide back in March. - "pdftk 1.44 or 1.45" is what the impressive manual on their website says. Now if that is not a "good reason"... So, which pdftk update are you talking about? I don't mind pushing the dependency removal to F20, now that pdftk is retired there, also. That would help people install it and get their pdftk from somewhere else.
As pdftk-1.44-11.fc19 (from official /20/Everything/ repository) cannot maintain bookmarks, I have built my own packages: http://www.bf.lu.lv/ftp/Linux/Fedora/repo/20/x86_64/os/packages/pdftk-2.02-K01.fc20.x86_64.rpm http://www.bf.lu.lv/ftp/Linux/Fedora/repo/20/SRPMS/packages/pdftk-2.02-K01.fc20.src.rpm (https://bugzilla.redhat.com/show_bug.cgi?id=980240) Of course, in the first place new impressive packages were rebuilt: http://www.bf.lu.lv/ftp/Linux/Fedora/repo/20/noarch/os/packages/impressive-0.10.5-K01.fc20.noarch.rpm http://www.bf.lu.lv/ftp/Linux/Fedora/repo/20/SRPMS/packages/impressive-0.10.5-K01.fc20.src.rpm A have left comment about iText in https://bugzilla.redhat.com/show_bug.cgi?id=1016241
AFAIK, impressive does not need pdftk at build time, only at run time. Can you confirm that impressive work with pdftk-2? The original impressive website http://impressive.sourceforge.net/manual.php still claims that pdftk 1.44 or 1.45 is required. Besides, I support your request to keep pdftk in Fedora. Let's work on that. (I'll recheck what I can do with impressive's packaging.)
I am running Fedora 20 x64. The packages are installed: impressive.noarch 0.10.5-K01.fc20 @bf.lu.lv-noarch pdftk.x86_64 2.02-K01.fc20 @bf.lu.lv The impressive operates as expected.
Follow-up info: As of svn r176 (which is in impressive 0.11.0a), pdftk 2 is allowed now. I'll package that up for F20 and F21 asap and remove the strict version requirement. Let's all help together and get pdftk2 into Fedora (or rpmfusion, at least).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.