Filesystem::touch() not working with different owners (utime/atime issue)
merged branch fabpot/moved_filesystem_3 (PR #7752)

This PR was submitted for the master branch but it was merged into the 2.1 branch instead (closes #7752).

Discussion
----------

Filesystem::touch() not working with different owners (utime/atime issue)

This PR was submitted on the symfony/Filesystem read-only repository and moved automatically to the main Symfony repository (closes symfony/Filesystem#3).

Case: I have 2 users, www-data and myself. I have a command script that makes a lock file in /var/lock/.../ something. This command is called from a post request by FOS and ran in the background.  Whever one of the 2 methods (web/cli manually) is used, the other user won't have permissions to use the Filesystem::touch(). The reason this won't work is the second parameter.

What touch() does:
$touch param: The touch time. If time is not supplied, the current system time is used.
$atime param: If present, the access time of the given filename is set to the value of atime. Otherwise, it is set to the value passed to the time parameter. If neither are present, the current system time is used.

So the current code is basically copying this. However, if the second parameter is null it is still present and will cause the same problem. Note that all files and folders related are set to 0777 and have the owner of www-data. I'm accessing them under my own account here:

Interactive shell

php > var_dump(touch('/var/lock/tripolis/ontw/dev/2140191804.lock', null));
PHP Warning:  touch(): Utime failed: Operation not permitted in php shell code on line 1

Warning: touch(): Utime failed: Operation not permitted in php shell code on line 1
bool(false)
php > var_dump(touch('/var/lock/tripolis/ontw/dev/2140191804.lock'));
bool(true)

If I were to pass it without second parameter, let it be time() or null (Filesystem uses time() by default if not present), it DOES work. However, Filesystem::touch() ALWAYS gives a parameter to touch. This parameter is exactly the same value as what the function itself would do in php. Let it be that in my case there is an issue with the atime. I'm not exactly sure how it works but it's not tracked or usable in my case. Because parameter 2 exists, parameter 3 is set. Parameter 3 is not allowed and therefore causes Filesystem::touch() to throw an exception.

Commits
-------

e3a0fe6 Filesystem::touch() not working with different owners (utime/atime issue)
[Validator] added missing estonian translation of messages
merged branch kgilden/trans_et (PR #7769)

This PR was merged into the 2.1 branch.

Discussion
----------

[Validator] added missing estonian translation of messages

| Q             | A
| ------------- | ---
| Fixed tickets | -
| License       | MIT

Commits
-------

efff50a [Validator] added missing estonian translation of messages
Removed trailing whitespace
merged branch pborreli/patch-9 (PR #7770)

This PR was merged into the 2.1 branch.

Discussion
----------

Removed trailing whitespace

Commits
-------

20d6fd8 Removed trailing whitespace
[Validator] added missing estonian translation of messages
merged branch kgilden/2.2 (PR #7776)

This PR was merged into the 2.2 branch.

Discussion
----------

[Validator] added missing estonian translation of messages

| Q             | A
| ------------- | ---
| Fixed tickets | -
| License       | MIT

This commit adds missing Estonian translation of messages introduced in 2.2. It's a follow-up to #7769.

Commits
-------

633b63b [Validator] added missing estonian translation of messages
Merge branch '2.1' into 2.2

* 2.1:
  Removed trailing whitespace
  [Validator] added missing estonian translation of messages
  Filesystem::touch() not working with different owners (utime/atime issue)

Conflicts:
	src/Symfony/Component/Validator/Resources/translations/validators.et.xlf
Merge branch '2.2'

* 2.2:
  [Validator] added missing estonian translation of messages
  Removed trailing whitespace
  [Validator] added missing estonian translation of messages
  Filesystem::touch() not working with different owners (utime/atime issue)