Permissions on files in packages depends on *my* umask

[nik9000]

It looks like I have an unusual umask on my laptop:

[manybubbles@localhost ~]$ umask
0002

I'm not sure how I got it but now that I have it I notice that the packaging tests don't pass:

$ ./gradlew -p qa/vagrant/ packagingTest
...
# Expected privileges: 644, found 664 [/usr/share/elasticsearch/README.textile]

I think we should try and build the same packages regardless of my personal umask setting.

[elasticmachine]

Pinging @elastic/es-core-infra

[nik9000]

It looks like this isn't actually based on the umask. There are other machines and users with the same umask that aren't getting this.

[nik9000]

This isn't caused by my umask:

[manybubbles@localhost elasticsearch]$ ./gradlew -p distribution clean
...
[manybubbles@localhost elasticsearch]$ umask 0022
[manybubbles@localhost elasticsearch]$ umask
0022
[manybubbles@localhost elasticsearch]$ ./gradlew -p qa/vagrant/ packagingTest
...
# Expected privileges: 644, found 664 [/usr/share/elasticsearch/modules/lang-painless/antlr4-runtime-4.5.3.jar]

[nik9000]

I was wrong about it not being my umask. If I git clean -xdf after setting my umask to 0022 then I get further. The tests still fail because my clone of elasticsearch has README.textile as 664 rather than 644. I think the umask that you had when you cloned Elasticsearch influences that one.