Arch Linux User Repository

Important: This package depends on libicuuc and needs to be rebuild if the icu package is updated on your system!

getting the following build error:

==> Starting build()...
ERROR at //core/fxcrt/BUILD.gn:139:15: Unable to load "/distro/local/repository/libpdfium-nojs/src/pdfium/base/allocator/partition_allocator/BUILD.gn".
    deps += [ "//base/allocator/partition_allocator:partition_alloc" ]
              ^-----------------------------------------------------
==> ERROR: A failure occurred in build().
    Aborting...

it looks like that BUILD.gn file is missing:

ll /distro/local/repository/libpdfium-nojs/src/pdfium/base/allocator/partition_allocator/BUILD.gn
ls: cannot access '/distro/local/repository/libpdfium-nojs/src/pdfium/base/allocator/partition_allocator/BUILD.gn': No such file or directory

Edit: actually, the entire src/pdfium/base directory is missing

Edit2: error confirmed on clean build also

Edit3: fixing this error caused yet more errors. to fix this one, you have to check out https://chromium.googlesource.com/chromium/src/base, then symlink it into the source tree: ln -sf $srcdir/base base.

source=("git+https://pdfium.googlesource.com/pdfium"
    "git+https://chromium.googlesource.com/chromium/src/build.git"
    "git+https://chromium.googlesource.com/chromium/src/base"
    "git+https://chromium.googlesource.com/chromium/src/third_party/abseil-cpp"
    "libpdfium.pc"
    )

md5sums=('SKIP'
    'SKIP'
    'SKIP'
    'SKIP'
    'feb270967925a0844b1b9a9e15288eb3'
    )

pkgver() {

  cd $srcdir/pdfium

  # Version = branch name/number + number of commits since branch creation
  # + short head
  printf  "%s.r%s.%s" $(git rev-parse --abbrev-ref HEAD | cut -d '/' -f2)\
   $(git rev-list --count main..) $(git rev-parse --short HEAD)

}

prepare() {

  cd "$srcdir/pdfium"

  ln -sf $srcdir/build build
  ln -sf $srcdir/base base
  ln -sf $srcdir/abseil-cpp third_party/abseil-cpp
  ...

this fix gets you to about 57 modules out of 741.

the next error is because of more missing parts in the source tree, specifically googletest. but any attempt to fix it causes a circular include dependency - i haven;t figured out how to resolve it yet and whether or not i should be resolving this.

is there a maintainer for this project who might add something here?

Getting errors when running pkgver:

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: fatal: ambiguous argument 'main..': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Patch:

diff --git a/PKGBUILD b/PKGBUILD
index 532ecc8..35d0600 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -31,7 +31,7 @@ pkgver() {
   # Version = branch name/number + number of commits since branch creation
   # + short head
   printf  "%s.r%s.%s" $(git rev-parse --abbrev-ref HEAD | cut -d '/' -f2)\
-   $(git rev-list --count main..) $(git rev-parse --short HEAD)
+   $(git rev-list --count HEAD..) $(git rev-parse --short HEAD)

 }

@selmf Thanks for the correction in PKGBUILD

@michaldybczak For me, on Arch, construction is easy, and do you sometimes use Manjaro?

@selmf, I updated with pamac and then with yay, in both cases it still showed the package to install. So I installed it manually with "makepkg -i" (with the changed version in PKGBUILD that @robson gave). Still no luck, package hangs on the update list. I guess I will wait for the official solution.

I have auracle-git installed for AUR update notification https://i.postimg.cc/d0tPHj74/screen.png I think it's enough to just edit PKGBUILD and change pkgver to the correct one.

@michaldybczak Some AUR helpers try to guess if a package update is needed by looking at the git head instead of checking which method pkgver() uses. This will result in the behavior you describe.

@robson Thank you for your comment. It seems that my package is suffering from a subtle bug caused by pdfium's switch from master to main branch. For older source checkouts, master is present and - it seems - no longer receives updates from upstream. This results in pkgver() miscalculating the amount of unique commits on the release branch. I'm looking into the problem right now, but it seems the best way to fix this is to delete the stale pdfium sources and rebuild with a clean checkout.

@robson, I followed your advice, and it didn't help. The package is still showing up on the update list, although it was just updated.

Change pkgver from 5060.r443.558516c323 to 5060.r1.558516c323

Good morning, I have a problem with this package, it is always asking to update, any solution to this problem?

thanks for your help! it's really appreciated! I will follow your guidance and post here any solution I may find! thnx!