Comments
nonamedotc
I am checking. i emailed the EPEL mailing list.
Alright, I am going to push this to stable.
SELInux rules are beyond the scope of this specific package, IMO. What do you think?
I am not sure if I want to go about changing selinux booleans ...
I am not sure if this is even allowed in packaging guidelines
In Fedora, this value is on.
$ getsebool selinuxuser_execmod
selinuxuser_execmod --> on
This may upto selinux policy maintainers to address and not nextcloud-client.
@marcovr - this may be due to differences in SELinux rules between epel and fedora. Not sure what nextcloud-client can do.
Right. I forgot about comps. I will do it as soon as I can.
Works nicely for me.
Thanks Germano.
This update has been unpushed.
We held this back because there were syncing issues with nextcloud server 23.x.
It is my understanding that nextcloud upstream has fixed it by disabling bulk upload. It may be safe to push this to stable.
@salimma do you agree?
If you are running nextcloud server v23.0, this bug may be applicable to you with client 3.4.1
This update has been unpushed.
With pyside2 included, everything works.
This update has been unpushed.
This update has been unpushed.
Would you be able to file bugs upstream?
This update has been unpushed.
Thread 1 "nextcloud" received signal SIGSEGV, Segmentation fault.
0x00007fffebd9da7f in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
This is what I see from gdb. :(
Can you please file a bug report on this with any details that you can obtain?
@germano There was no need to unpush this update. This is useful to get wider testing.
I am getting this built and will submit an update in the next day or two. It will be direct update to v3.6.0.
Sorry for the delay.