https://owncloud.org/blog/owncloud-desktop-client-2-0-is-out-with-multi-account-support-and-more/

Component: New RPM package request => RPM Packages
Hardware: x86_64 => All
Version: 5 => Cauldron
Whiteboard: (none) => MGA5TOO
Severity: normal => enhancement

If someone builds, i can test :)
- same for the latest server.

CC: (none) => fri

2.0.1 submitted into cauldron. There are some problems tho': 

https://bugs.archlinux.org/task/46126

The client itself seems to be working and can be started from start menu (in Plasma 5 that is..).

CC: (none) => mageia

Last post aug 31 at that link say it works after a restart.
But there are more problems in mga6?
I do not run any mga6/cauldron yet as my test computer got occupied...
but can test when you have for mga5 32 & 64.

i would like to push it as a backport, or an update for mga5.

is it OK ?

Backport, great :)
2.x can connect to several servers in one instance.

As an update from 1.x: !! NO !!
Too different, especailly if you already have more than one configuration for owncloud 1.x (run one at a time to reach two different servers)

On my MSWindows computer it fouled up when updating itself latest 1.8.x to first 2.x it found.
( Needed complete reconfigure and i did not have credentials at hand... )
Also on at least one customer running MSwindows it fouled up.

Tested on i586 MGA5, works nicely. Only one point : it shows in config box that 2.0.2 version is latest, maybe we should upgrade to this one before pushing to backports?

Status: NEW => ASSIGNED

Please test now, i added version 2.0.2.

(In reply to Nicolas Lécureuil from comment #8)
> Please test now, i added version 2.0.2.

No you didn't, according to http://pkgsubmit.mageia.org/ ;-)

mga6 2.0.2 was submitted, but not mga5.
I will test 2.0.2 when available on mga5 64bit.

BTW, any chance of updating ownclud server?
latest mga5 is 8.0.9, while latest stable is 8.2.1.

2.0.2 is on backport now.

For owncloud we push on backports or updates ?

Thanks Nicholas
Iĺl try client 2.0.2 tomorrow.

IMO owncloud (server) should be on updates, as it should be updated as regularly as possible.  That suits SOHO usage.  If run in larger business a good sysadmin may not run automatic updates at all, or check them.  We have kernel and graphic in updates so why not owncloud.


From https://doc.owncloud.org/server/8.1/admin_manual/maintenance/upgrade.html :
It is best to keep your ownCloud server upgraded regularly, and to install all point releases and major releases without skipping any of them, as skipping releases increases the risk of errors. Major releases are 8.0, 8.1, 8.2, and 9.0. Point releases are intermediate releases for each major release. For example, 8.0.9 and 8.1.3 are point releases. Skipping major releases is not supported.

Note that last sentence "Skipping major releases is not supported."
If we follow it, we must first release 8.1.x as update *), 
wait a couple weeks so all users update, and then release then latest 2.x.

This also means we can not delay major owncloud releases until next major mageia release ! as owncloud may and have been shifting major releases faster)


IIRC there use to often be problems with x.x.0 versions so go for latest 8.1.x

(In reply to Morgan Leijström from comment #12)
 > IMO owncloud (server) should be on updates, as it should be updated as
> regularly as possible.
> 

Agreed, but this needs a new bug report....

Please open a new bugreport for owncloud, it is on updates_testing already.

I made Bug 17279 : Update owncloud server to 8.2.1 need first 8.1.x 

Client 2.0.2 installing and running perfectly fine on mga5-64

Clean(ed) install; I uninstalled the three 1.8.3 packages and removed its configuration files before installing and configuring 2.0.2.

Thank you

I have tested the client 2.0.2 on both i586 and x86_64 and added the whiteboard keywords.

Nicolas, please add an advisory and assign to qa-bugs so that it can be pushed to Backports!

Whiteboard: MGA5TOO => MGA5TOO MGA5-64-OK MGA5-32-OK

2.1.0 released, with quite a lot bugfixes.
I am ready to try if packaged.

https://owncloud.org/changelog/desktop/

2.0.2 has been in testing for more than one month. I use it daily with no prolem in i586 and x86_64, so I suggest we validate it.

may i update to 2.1.0 first ? so we only validate once ?

looking to the changelog i uploaded a 2.1.0 version

Using Mageia 5 64 bit, found 2.1.0-1mga5 in backports_testing, thanks.
And yes it say it is 2.1.0, more specifically  "Built from Git revision c0c9fb on Jan 24 2016, 15:04:19 using Qt 5.4.2, OpenSSL 1.0.2e 3 Dec 2015"

Quick test OK, syncing to two different owncloud servers: a 8.0.9 on my mageia server on LAN, and a 8.2.2 at my internet provider shared hosting.
Update from working 2.0.2, sync state verified OK.
Tested new files and file deletion propagated OK.
Leaving MGA5-64-OK as is (was for earlier version)
Removing "MGA5-32-OK" for someone else to check on this version.

Any plan for Bug 17279 : Update owncloud server to 8.2.1 need first 8.1.x ?

Whiteboard: MGA5TOO MGA5-64-OK MGA5-32-OK => MGA5TOO MGA5-64-OK

(In reply to Morgan Leijström from comment #21)
> Removing "MGA5-32-OK" for someone else to check on this version.

Tested here also as an update of 2.0.2 client on i586. All is ok.

> 
> Any plan for Bug 17279 : Update owncloud server to 8.2.1 need first 8.1.x ?

Let's continue to discuss that inside this bug.

Will need a list of rpms & srpms please.

rpms: owncloud-client

srpms: owncloud-client

ping

Sysadmins are aware. Ping won't help to free up any time for them. 
Backports are our lowest priority.

Current owncloud client (and server #17279) are put in backports instead of normal updates to avoid because they need user interaction to work after the update and we do not want automatic update to break anything.

They do both have bugfixes that are as important as other updates.

Sysadmins are aware they are awaiting push Morgan.

Done

mga-adv-move-pkg --sync --backport 5/core/owncloud-client

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