Closed martinlindhe closed 9 years ago
The problem is that the tool tries to find pdf-explode in PATH, making it inpossible to test without installing.
forgot to mention, this is on Debian sid,
the issue remains (that is, it is not possible to run the script without installing, since it looks for pdf-explode in PATH)
when running the installed pdf-sanitize (since #4 got fixed), the above problem goes away (pdf-explode is found in path), so this bug can be closed i guess
instead i hit different error, which i opened as bug #8
Thanks for reporting this! Sorry I've completely ignored it for so long. I can reproduce this, and am working on a fix.
Fixed!
thanks! will retry when i get some time
Testing the scripts on Debian sid.
See my previous bug report about build_deb.sh, i am testing from the git checkout.
$ ./pdf-sanitize ~/e-books/First\ Aid\ Made\ Easy.pdf Traceback (most recent call last): File "./pdf-sanitize", line 26, in
subprocess.call(['pdf-explode', input_filename])
File "/usr/lib/python2.7/subprocess.py", line 522, in call
return Popen(_popenargs, *_kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory