| Summary: | Create a nextcloud-client package. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Xuo <xuoy> |
| Component: | New RPM package request | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | fri, geiger.david68210, lists.jjorge, mageia, xuoy |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Xuo
2016-09-27 21:03:07 CEST
nexcloud is already on Cauldron and replaces owncloud: http://svnweb.mageia.org/packages?view=revision&revision=1036847 CC:
(none) =>
geiger.david68210 Yes, but this bug report is about owncloud-client, not owncloud itself. I hadn't heard if nextcloud had forked the client and was wondering about that. Assignee:
bugsquad =>
mageia Hi, That's great that nextcloud is integrated in Cauldron. I hope it will be available for Margeia 6. Yes, I was talking about the desktop client, not about nextcloud itself. Nextcloud has forked the owncloud desktop client. I could compile it from the source files but it is easier if a package is available (and I get an error at the end of the compilation even though I can run the executable). Regards. Xuo. CC:
(none) =>
xuoy I would hope that the two clients would be compatible and that we would be able to just package one or the other and not need both. I see that owncloud-client 2.2.4 has been released: https://owncloud.org/changelog/desktop/ I don't know if nextcloud-client contains all of their fixes and enhancements. Hi, I understand what you mean. The version 1.8.3 of owncloud-client (available in Mageia 6) is compatible with the current version of NextCloud. So no nextcloud-client is necessary. But someone using nextcloud will try to find first a nextcloud client desktop before thinking about using the owncloud one. Moreover, the user could prefer using the nextcloud release than the owncloud one after what happened between the OwnCloud company and some of its developpers. This is just a suggestion. Owncloud-client is a possible workaround. Regards. Xuo. Hi, Following last Cauldron update, I saw that owncloud-client was automatically replaced by nextcloud-client. 1- is it the intent ? why not have the 2 packages ? 2- nextcloud client won't start: $ nextcloud nextcloud: error while loading shared libraries: libocsync.so.0: cannot open shared object file: No such file or directory 3- the icon is missing in the menu entry thanks a lot, CC:
(none) =>
mageia Yep same problem here. Missing a dep or wrong name? (the part "ocsync" sound like the old for owncloud client ?) About what is intended, see https://wiki.mageia.org/en/OwnCloud#News CC:
(none) =>
fri Weird. I do have lib64ocsync installed, and it provide /usr/lib64/nextcloud/libocsync.so.0 Icon and shared libraries should be fixed now in next nextcloud-client update! nextcloud-client-2.2.4-5 OK, now it starts, but have problems: In the middle of configuring shares to sync it segfaulted :( I had configured three shares which it verified synced OK, when i was adding a fourth it just disappeared when i had selected share on server. In terminal from where i started it it said segmentation fault. And i never saw an icon in systray. Is there some debug mode? Rebooted... it works currently :) I also found the icon... Is it possible to make the icon not hide, instead per default be shown? (Plasma system tray) I have dropbox set to automatically show, and it shows always when dropbox runs. But when NExtcloud is set to show automatically (as it was) is is NOT shown. User have to change it to always show (if he want to see it) BTW, IMO it is not optimal that dropbox, owncloud, and nextcloud is shown by exact same "cloud" icon, but that maybe is a Plasma directive? Now i see what happened when it segfaulted: I had in setup selected a local (and remote) folder which contain the swedish letter "Ã¥". Now i see it have created new local folder with that name but where "Ã¥" is replaced with "?". It is empty, and now after just restarting it it is syncing the folder i specified. This is a regression against owncloud client 2.2.4 we had recently. Is this is an upstream bug internal in nextcloud, or could it be a packaging bug? This bug is fixed for months, closing. To any cloud users, there is a client update to test : https://bugs.mageia.org/show_bug.cgi?id=21015 and a server upgrade : https://bugs.mageia.org/show_bug.cgi?id=22026 Status:
NEW =>
RESOLVED |