-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux desktop sync client does not preserve execute permissions #3199
Comments
@dragotin, adding to milestone as it's currently in the top-10. |
I doubt this is in scope for 1.8.2. Supporting file permissions would need updates to client and server and is more like a new feature than a bugfix. It would also need to make sure to work nicely with the different permissions systems that our client platforms (and probably storage backends!) employ. |
So guys just so I am clear, the files as they sync down from the OC server I assume that the changing permissions (i.e. it is no longer has exe permissions) this is expected behavior? @iliyasbasir have you tested this in the lab? Assuming that is the case are we saying this is a feature request? |
rather than expected behaviour I'd call it a missing feature. As said before, we need a way to
That should be scheduled by product management once we have a clear picture of the scope and the functionality. |
Understood and thank you!! We will take the suggested actions with PM!! Thanks for your help!! |
@bboule sorry, it was not said before here, but somewhere else we had this topic as well... don't remember where. |
@ckamm @dragotin this my yesterday evening testing step...still No Luck !
Then,
|
OK guys I have presented the workarounds for this to the customer the workaround is one of the following: 1. Put the software in an archive and inform the user they need to extract to a location other then the OC sync folder. 2. Simply let them download, copy to another location and then add the x flag back. In the meantme @iliyasbasir can you type up the issue in a SF as a feature request? |
can this be closed? |
Can I keep it as a feature enhancement? For tracking purposes. |
Indeed I asked Iliyas to convert or open a new feature request I prefer he close the customer issue and open FR but either way Sent from my iPhone
|
There was an issue already before for the same thing: #820 But we need support for storing metadata on the server. There is a server issue: owncloud/core#6983 It would be nice if the server could allow arbitrary metadata that we can use to store things like local permissions |
@bboule Please update status, can we remove blue? |
What if I chmod locally the file? Don't you need the PROPPATCH to propagate I think if we draft the spec as I proposed earlier then it will be easier On Wed, Nov 16, 2016 at 11:42 AM, Olivier Goffart [email protected]
Best regards, |
@ogoffart Next steps? Should we talk to get an agreement? |
The next step is:
|
Removing from client milestone because it depends on server feature which are not scheduled. |
This is a key feature, missing this makes the synced data just not usable at all for my purposes. |
Does this have a chance of ever happening? This is the one thing that keeps OwnCloud from being a Dropbox killer. They had this on day #1 :( |
Realistically not in 2021, sorry. |
Hello guys at owncloud, 6 years and counting.... no pressure ;-) |
amen. is this really such a big thing that it couldn't be solved in 6 years? |
@moscicki Idea was, your team makes a proposal for the CS3 API's. |
Is there an estimate as two when this might get fixed? |
I am synching 2 macOS systems and same issue overhere. |
Expected behavior
File permission should stay same as own cloud server
Actual Behavior
When Desktop client sync folder from oC; Permission changed for all file inside folder but folder permission stay remain as oC server.
Step to reproduce
Server
Operating system: Ubuntu 13.10
Web server: Apache/2.4.6 (Ubuntu) Server
Database: MySQL server version 5.6.19
PHP version: PHP 5.5.3-1ubuntu2.6 (cli) (built: Jul 7 2014 16:54:32)
ownCloud version: 7.0.5
Storage backend: local
Client configuration - Can you clarify/elaborate what you mean here?
Client version: version 1.8.0
Operating system: Any Linux system (in this case, we'll use Ubuntu 14.04)
OS language: English (US)
Installation path of client: /usr/bin/{redacted}
Logs
s3:Shared/owncloud/support/github-issues/client/3188
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: