Package Details: libpdfium-nojs 3770.r1.6ce1d13248-1

Git Clone URL: (read-only)
Package Base: libpdfium-nojs
Description: Open-source PDF rendering engine.
Upstream URL:
Keywords: pdf
Licenses: BSD
Conflicts: libpdfium-bin
Provides: libpdfium
Submitter: selmf
Maintainer: selmf
Last Packager: selmf
Votes: 5
Popularity: 0.047925
First Submitted: 2017-07-30 18:14
Last Updated: 2019-06-07 16:28

Latest Comments

1 2 Next › Last »

selmf commented on 2019-06-19 15:13

@steinbuch It never was removed from upstream (

steinbuch commented on 2019-06-19 14:25

Do you know when the third_party directory ( ) was removed from upstream?

selmf commented on 2019-04-26 16:02

The patch was upstreamed so it is no longer necessary. I've updated the package.

Nefas commented on 2019-04-26 08:58

There is an issue with some patches:

patching file pdfium/third_party/
Hunk #1 succeeded at 413 (offset 19 lines).
patching file pdfium/core/fxcodec/codec/codec_int.h
Hunk #1 FAILED at 10.
1 out of 1 hunk FAILED -- saving rejects to file pdfium/core/fxcodec/codec/codec_int.h.rej
patching file pdfium/core/fxcodec/codec/ccodec_jpxmodule.cpp
Reversed (or previously applied) patch detected!  Assume -R? [n]


patching file pdfium/core/fxcodec/codec/cjpx_decoder.h
Hunk #1 FAILED at 13.
1 out of 1 hunk FAILED -- saving rejects to file pdfium/core/fxcodec/codec/cjpx_decoder.h.rej
patching file pdfium/
Reversed (or previously applied) patch detected!  Assume -R? [n]

The patch always fail.

selmf commented on 2019-02-04 06:36

No, as it turns out I did update the checksum correctly, but forgot to commit the updated openjpeg.patch too. Hopefully finally fixed now ;)

FrederickZh commented on 2019-02-04 04:47

@selmf I think the md5 should be 126d768d83a44217ce6d702cc64939e8? Currently in PKGBUILD it's 30fb763082245a1368aa6c68d61660ab.

selmf commented on 2019-02-03 17:17

Ugh. Yes, sorry about that. Fixed.

dramm commented on 2019-02-02 17:24

It seems that a checksum needs to be updated.

==> Validating source files with md5sums...
    pdfium ... Skipped
    build ... Skipped
    buildtools ... Skipped
    libpdfium.pc ... Passed
    openjpeg.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!

selmf commented on 2019-02-01 15:33

Yeah, that can happen. This package tracks the stable channel of Chromium, so whenever a new version is released there is some chance of breakage. When I introduced this mechanism this didn't happen too often, but it is getting more frequent. I probably should remove it and just manually track the "good" versions ;)

I've updated the patches, so compilation should work again.

m8D2 commented on 2019-02-01 03:41

Hi,I got this error:

patching file pdfium/third_party/
Hunk #1 succeeded at 394 (offset 27 lines).
patching file pdfium/core/fxcodec/codec/codec_int.h
patching file pdfium/core/fxcodec/codec/ccodec_jpxmodule.cpp
Hunk #1 FAILED at 17.
Hunk #2 FAILED at 515.
Hunk #3 succeeded at 550 (offset 1 line).
2 out of 3 hunks FAILED -- saving rejects to file pdfium/core/fxcodec/codec/ccodec_jpxmodule.cpp.rej
patching file pdfium/core/fxcodec/codec/cjpx_decoder.h
patching file pdfium/
Hunk #1 succeeded at 20 (offset -1 lines).
Hunk #2 succeeded at 76 (offset -1 lines).
==> ERROR: A failure occurred in prepare().
Error making: libpdfium-nojs