Arch Linux

Description:
It looks like the gocryptfs package got moved to community from the AUR on Dec 1. After I upgraded to the community version (1.6-2), the mounted file system is no longer supports permission changes. Reverting back to a cached AUR build (1.6-1) results in chmod working correctly again.

Attempting to use chmod within the mounted FS in 1.6-2 results in:
bash-4.4$ touch foo
bash-4.4$ chmod 600 foo
chmod: changing permissions of 'foo': Operation not supported

And if fuse debugging is enabled, the relevant line in the log is:
Serialize 161: SETATTR code: 95=operation not supported value: {A0.000000000 {M00 SZ=0 L=0 0:0 B0*0 i0:0 A 0.000000000 M 0.000000000 C 0.000000000}}

I am not familiar enough with fuse to know where to look to keep debugging. The only thing I see in the PKGBUILD that may be related is that the one in community does not do a `go get -d github.com/hanwen/go-fuse/fuse` step while the one in AUR did. Maybe it's because the build server has a different version of the go-fuse package?

Additional info:
gocryptfs 1.6-2
fuse 2.9.8

Steps to reproduce:
- mount an encrypted gocryptfs system, using default options
- try to run chmod on any file in the unencrypted mount
- Basic unix permissions used to work, now fails with code 95