(original) (raw)

On 01Apr2019 15:44, Steve Dower <steve.dower@python.org> wrote:
\>On 01Apr2019 1535, Cameron Simpson wrote:
\>>On 01Apr2019 09:12, Steve Dower <steve.dower@python.org> wrote:
\>>>On 30Mar2019 1130, Gregory P. Smith wrote:
\>>>>I wouldn't expect it to be the case in a CI environment but I
\>>>>believe a umask can be overridden if the filesystem is mounted
\>>>>and configured with acls set? (oh, hah, Ivan just said the same
\>>>>thing)
\>>>
\>>>Yep, it appears this is the case. The Pipelines team got back to
\>>>me and it seems to be a known issue - the workaround they gave me
\>>>was to run "sudo setfacl -Rb /home/vsts" at the start, so I've
\>>>merged that in for now (to master and 3.7).
\>>
\>>Could that be done \_without\_ sudo to just the local directory
\>>containing the test tar file? If that works then you don't need any
\>>nasty privileged sudo use (which will just break on platforms
\>>without sudo anyway).
\>
\>I tried something similar to that and it didn't work. My guess is it's
\>to do with the actual mount point? (I also tried without sudo at
\>first, and when I didn't work, I tried it with sudo. I hear that's how
\>to decide whether you need it or not ;) )
\>
\>In any case, it only applies to the Azure Pipelines build definition,
\>so there aren't any other platforms where it'll be used.

Ok then.

Curious: is the sudo now in the build setup? I'm just thinking that this
isn't a tarfile specific fix but a "get correct POSIX umask semantics"
fix, so it should apply to the entire environment.

Or am I naive?