Package Details: watchman 4.9.0-1

Git Clone URL: (read-only)
Package Base: watchman
Description: An inotify-based file watching and job triggering command line utility
Upstream URL:
Licenses: Apache
Submitter: mithaler
Maintainer: FredBezies
Last Packager: flacks
Votes: 56
Popularity: 0.353068
First Submitted: 2013-06-19 17:23
Last Updated: 2017-08-23 18:32

Dependencies (2)

Required by (3)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

benj commented on 2016-08-02 16:02

If you are using this for ember-cli you might need to increase the amount of inotify watchers:

"echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system"


jlesquembre commented on 2015-12-13 15:32

@vith I forgot about watchman-wait and watchman-make, since I don't use them. I created a new package, python2-pywatchman [1], where these 2 commands are included. It makes more sense to me, to have an extra package for the python stuff. Feel free to comment if you have different thoughts about it.


jlesquembre commented on 2015-12-13 15:21

@mtorromeo yes, I'm not using a service unite, nevertheless, thanks for pointing to RuntimeDirectory, I didn't know about it

mtorromeo commented on 2015-12-13 01:29

Nevermind, I didn't see that you are not setting up a service unit.

mtorromeo commented on 2015-12-13 01:28

@jlesquembre: you don't need tmpfiles.d for this. Just use "RuntimeDirectory=watchman" [1]


vith commented on 2015-12-12 23:59

Ah cool, didn't know about tmpfiles.d.

Still, do you realize you aren't just excluding python bindings but also two cli commands that depend on the bindings? /usr/bin/watchman-wait /usr/bin/watchman-make

I ended up not using watchman in the end anyway so I no longer have a horse in this race, but seems like it'd make more sense to just include the python stuff.

jlesquembre commented on 2015-12-12 16:56

Just updated the package, now is compiled without python, if you want the python bindings, install pywatchman (only python2 for now)

@vith Thanks for pointing the problem with /usr/var/run, it should be fixed. Now a directory is created at /run. It's tmpfs, but systemd handles it, if you are curious, take a look to the following links:

vith commented on 2015-12-11 22:58

Also there are still a few more namcap warnings

❯ namcap watchman-4.2.0-1-x86_64.pkg.tar.xz
watchman W: File (usr/var/) exists in a non-standard directory.
watchman W: File (usr/var/run/) exists in a non-standard directory.
watchman W: File (usr/var/run/watchman/) exists in a non-standard directory.
watchman W: File (usr/var/run/watchman/.not-empty) exists in a non-standard directory.
watchman W: File (usr/var/run/watchman) has the world writable bit set.
watchman W: File (usr/var/run/watchman) is setuid or setgid.

But I don't know if they should be ignored or what should be done. You'd think watchman should use /var/run -> /run but it's tmpfs so if it really needs those permissions to be done by the package installation then that's going to break on reboot; I haven't tested this. Is it an upstream issue? Related

vith commented on 2015-12-11 22:43

@jlesquembre pywatchman seems to be included in this package, but all the python stuff is broken because it's using python3 bin/paths.

Just try running `watchman-make --help`.

This worked for me:

jlesquembre commented on 2015-12-11 15:42


Not really, only if you compile it with the --with-python option, which is not the case. If you want to install the python bindings install pywatchman:

Current version seems to be only python 2 compatible