for mga6 core release that is

AND 

It would be good if also put in backport in mga5 !
When done i will edit https://wiki.mageia.org/en/OwnCloud#Client_upgrading

Priority: Normal => High
CC: (none) => lists.jjorge, luigiwalser, zombie_ryushu
Whiteboard: (none) => MGA5TOO

There are "a ton of bugfixes", crash fixes, and lot more (i would suspect some security enhancement too)
https://owncloud.org/changelog/desktop/

(i could not find *nextcloud* client changelog but i guess it is same source still, + branding? )

Would be great if it could sneak in to mga6 release if not too late...

José ?

Yes. The major difference seems to be that NextCloud works with KDE 5 Plasma Wallet while OwnCloud Client seems to use the KDE 4 Wallet. Which means Plasma users can use the Pam KDE 5 Wallet module to authenticate if they are using Kerberos.

BTW, is it possible to make it use its own logo for the Plasma system tray- same it use for the program ( oOo ) ?

Currently at least all Nextcloud, ownCloud, and Dropbox clients confusingly use same symbol, while i.e Syncthing thanfully use its own.

Mageia 6 has been released and NextCloud has not been updated.

We are now at the end of july and every time i log in, a popup window invites me to upgrade to NextCloud 2.3.1 using my distrib package tools. But there is still no 2.3.1 available.

CC: (none) => magnux77

Mageia has a policy, it does not provide updates if they do not fix security or reproductible bugs.

If you read the client changelog at https://owncloud.org/changelog/desktop/ you will see there are lots of crashes in the first 2.3.x releases.

Still, we can provide it as a backport. If the maintainer agrees, I volunteers to do it.

Status: NEW => ASSIGNED

We've updated owncloud-client to the latest stable before.  Compatibility with web services is one of reasons we make exceptions to the policy, so I think this qualifies.  You shouldn't need to do it as a backport.

I think it should have similar treatment as i.e Firefox.
Because of stability, compatibility, and security.
(and possibly the server part too)

Ping for this update please.

Client shows a nag message each login that an update is available and to check the repository. Should be reason enough to update.

Current stable is 2.3.2
Mga6 has 2.2.4 from September 2016.

As this has come to a general agreement, I have submitted 2.3.2 version to updates_testing.

Please, keep it testing for some days to ensure we have no new crashes.

Assignee: mageia => qa-bugs

Thanks Jose. It doesn't start though.

$ nextcloud
nextcloud: symbol lookup error: nextcloud: undefined symbol: _ZN3OCC7Utility12platformNameEv

Was Cauldron also updated? I'll set the bug version if so.

Hmm missed updating a library. Rebooting again.

Segfaults.


$ rpm -qa | grep next
lib64nextcloudsync0-2.3.2-1.mga6
nextcloud-client-2.3.2-1.mga6

$ nextcloud
Segmentation fault (core dumped)

(In reply to claire robinson from comment #13)
> $ rpm -qa | grep next
> lib64nextcloudsync0-2.3.2-1.mga6
> nextcloud-client-2.3.2-1.mga6
> 
> $ nextcloud
> Segmentation fault (core dumped)

I should have sent the file list, you missed lib64ocsync0.

To test in i586, I did :

urpmi --searchmedia testing nextcloud-client libocsync0 libnextcloudsync0

Then it works nicely.

Version: Cauldron => 6
Whiteboard: MGA5TOO MGA6TOO => (none)

I have removed mga5 from our target : we are too near it's EOL to waste testing in this.

That was it José thanks. Seems fine so far.

I'll report back in a few days mga6 64.

Tested under Mate and Plasma mga6 64

OK across several reboots and suspends.

Whiteboard: (none) => mga6-64-ok

Wanting to invent an advisory for this, I am confused about the SRPM version. Bug comments say 2.3.2-1, but the SRPMs update link shows nextcloud-12.0.3-1.mga6.src.rpm. Please clarify!
I added a 32-bit OK from comment 14.

CC: (none) => lewyssmith
Whiteboard: mga6-64-ok => mga6-64-ok MGA6-32-OK

Lewis, this bug is for nextcloud-client, not nextcloud.

(In reply to David Walser from comment #19)
> Lewis, this bug is for nextcloud-client, not nextcloud.
I suspected that, but did not see it listed; I doubt that I would have overlooked it - it is there now! Advisory invented from early comment & the SRPMs link; & uploaded.

Keywords: (none) => advisory

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2017-0113.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Thank you :)