A few things were noted about that fix that made it not acceptable, but it’s unclear if this fix will be accepted in any state. So that’s what I’m asking here: Will any 32-bit specific fixes be accepted for nextcloud server?
This must be annoying for you. I will discuss this with the director of engineering to clear this up. I am unfortunately out of office from tomorrow on for two weeks but I will discuss this with him on my return and I will keep you closely informed. I also gave the link to your post to him.
Hello hello,
So I discussed this situation with the relevant developers and the director of engineering. We agreed to accept pull requests for 32 bit fixes from the community if the PR’s seem of a good quality and will pose little risk for causing problems. (Please note we do not test the PR’s ourselves locally against 32 bit because we don’t have those test environments anymore, so an accepted PR doesn’t mean we really guarantee the intended functionality, and if the PR’s do cause problems and we reject it, we can’t dig to give more specific pointers on how to improve the PR.) I hope this is good with you?
I want to set up a Raspberry Pi Zero W as a NextCloud client sink, meaning that it should regularly sync from server to client, so that rdiff-backup or a similar tool creates a backup.
If I can achieve the sync with “native webdav”, I’m all in!
On the other hand I also would like to better understand the inner workings of NextCloud, and the nextcloudcmd CLI command seems to be appropriate.
So my current goal is to compile nextcloudcmd for 32bit ARMv6.
I’m glad for this option, because compiling nextcloudcmd is a major effort, starting with the fact that Qt5 is not only used for the GUI but the networking too. I cannot even compile it on Ubuntu, and crosscompiling or compiling on the Raspi will be much more difficult.
To all: which NexCloud client do you use on 32-bit arm devices, and how did you install it?