Please ensure that the watchman release has the required watchman-*-linux.zip
asset attached before you mark this package out of date.
Upstream's CI often fails to build one or more assets and we have to skip releases.
Git Clone URL: | https://aur.archlinux.org/watchman-bin.git (read-only, click to copy) |
---|---|
Package Base: | watchman-bin |
Description: | An inotify-based file watching and job triggering command line utility |
Upstream URL: | https://facebook.github.io/watchman/ |
Licenses: | MIT |
Conflicts: | watchman |
Provides: | watchman |
Submitter: | heftig |
Maintainer: | heftig |
Last Packager: | heftig |
Votes: | 21 |
Popularity: | 0.97 |
First Submitted: | 2020-10-22 15:35 (UTC) |
Last Updated: | 2025-04-24 17:06 (UTC) |
Please ensure that the watchman release has the required watchman-*-linux.zip
asset attached before you mark this package out of date.
Upstream's CI often fails to build one or more assets and we have to skip releases.
They seem to have fixed it without warning. And been releasing every release or so.
https://github.com/facebook/watchman/releases/tag/v2025.04.14.00
Sorry. I flagged as outdated and read the comment after.
I opened an issue in their repo.
Not out of date.
https://github.com/facebook/watchman/releases/tag/v2025.02.10.00 does not have the required watchman-*-linux.zip
asset and can't be packaged.
This used to happen just sometimes and we then skipped that release, but since April 2024, upstream's builds have been consistently broken and they don't seem interested in fixing it.
Something went wrong...
==> Starting prepare()...
patchelf: getting info about '--add-rpath': No such file or directory
==> ERROR: A failure occurred in prepare().
Aborting...
-> error making: watchman-bin
I managed to build the latest watchman
from the source, and it solved the crashing problem.
You can find my PKGBUILDs at https://github.com/Xinkai/watchman-PKGBUILDs/
I will wait for a while before publishing these on AUR because the changeset required is too large for what could be a short-term issue.
v2021.08.23.00 is currently the last release for which Facebook has provided binaries.
Should be fixed now.
I can reproduce it building with devtools. Investigating...
It works fine for me:
> ldd /usr/bin/watchman
linux-vdso.so.1 (0x00007ffefe9d2000)
libgflags.so.2.2 => /usr/lib/watchman/libgflags.so.2.2 (0x00007fcda92fe000)
libglog.so.0 => /usr/lib/watchman/libglog.so.0 (0x00007fcda90c2000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007fcda8db4000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fcda8dad000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fcda8d8c000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fcda8baf000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007fcda8a68000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fcda8a4e000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007fcda8881000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fcdb4c0d000)
Pinned Comments
heftig commented on 2025-04-24 17:09 (UTC)
Please ensure that the watchman release has the required
watchman-*-linux.zip
asset attached before you mark this package out of date.Upstream's CI often fails to build one or more assets and we have to skip releases.