Arch Linux User Repository

I updated this package to the new beta version, which no longer depends on python2 libraries.

I tested it in a few different scenarios, and there is a bug regarding the new python3 code and the pdftk backend. I reported it upstream and it's fixed in the SVN. The next version will work fine with pdftk but, meanwhile, I switched to mupdf, which seems to work every time.

@Tio: Impressive needs to be launched specifying a file. Something like

impressive slides.pdf

In any case, "command line parse error: no playable files specified" means that impressive couldn't find any presentation file. Try launching it from the same folder, something like the example above, to verify there aren't any white spaces in the path.

It works now to install but I get this error when I try to run it:

Welcome to Impressive version 0.12.1
pygame 1.9.5
Hello from the pygame community. https://www.pygame.org/contribute.html
command line parse error: no playable files specified
use `/usr/bin/impressive -h' to get help
or visit http://impressive.sourceforge.net/ for full documentation

Well, I installed java-commons-lang (which is a opt-dep of pdftk) and everything works fine now, without the java errors.

I tried impressive with the new pdftk from community and using the default backend (Xpdf/Poppler) but it doesn't seem to work with PDF v1.5 (from pdflatex) while it works just fine with PDF v1.4 (from Impress). There are some java errors while running it, but they appear whether the presentation works or not.

Then I tried a different backend, so I installed mupdf-tools, and it works fine with every version of PDF. I don't know what changed with the new pdftk (since it used to work before), but maybe this package could depend on mupdf-tools instead of pdftk for better compatibility.

Manjaro Gnome it gets stuck on "preparing" - I am using pamac to try and install.

@pat-s, could you change the dependency to pdftk?

pdftk-bin provides pdftk, so the user can choose between having pdftk or pdfk-bin if you put pdftk has a dependency. I myself prefer compiling pdftk from source (I'm also the maintainer for pdftk.)

Cheers,

@GeoffreyFrogeye
I see the point. I moved from pdftk to pdftk-bin because of @gersons argument. I have no real preference here. But the cumbersome build process of pdftk maybe favors pdftk-bin a little bit more? Both pkgs are used by ~ the same amount of users.

I would advise against using pdftk-bin as a dependency. pdftk-bin provides pdftk, so if the dependency is on pdftk and one has installed pdftk-bin, this package will still be able to be installed. On the other hand, if we keep the pdftk-bin dependency, one that has pdftk installed won't be able to install this package.

@gerson Thanks. I'll tackle this after I am back from vacation. Hit me up again in case I forget.

pdktk depends on gcc6, which makes it quite cumbersome. It is better to install pdftk-bin. Could we set pdftk-bin as the default instead of pdftk?