Mageia forum

Hello,

I was running an owncloud service on my private webspace since 2 years. During summer, I switched over to the Nextcloud fork in the hope of a better community support.
With Nextcloud server versions 9 and 10, the old Owncloud client (version 1.8.3 shipped with mga5) could still connect.
But when I have been doing the upgrade to Nextcloud 11.0.0 two days ago, I saw that my Mageia Laptop does not replicate the cloud data any longer.

The error message is:
"Error downloading https://Nextcloud-URL/remote.php/webdav/ - server replied: Forbidden (Unsupported client version)"

I filed a bug in the Bugzilla [1], but I am not even sure if this is a valid bug report.
I see that Cauldron contains the Nextcloud client instead of Owncloud client, but it seems to early to upgrade the entire distro to Cauldron.

Is there any hint how I could use the particular Cauldron packages and stay with the rest in Mageia 5 status?
---- I recall that enabling the Cauldron sources would typically require to update the rpm packages first, which may come along with a lot of further things in a chain reaction.

What are my options?

Thanks a lot.

Best regards,
Marcus

[1] https://bugs.mageia.org/show_bug.cgi?id=20035

mzurhorst wrote:Is there any hint how I could use the particular Cauldron packages and stay with the rest in Mageia 5 status?

Basically you can't, except for a few packages which don't contain any compiled stuff, or don't rely on any specific library versions newer then in mga5.

mzurhorst wrote:What are my options?

Basically the only thing you can do is to grab the src.rpm from cauldron for the package you want, and rebuilt it on your mga5 box. But that also includes backporting of any libraries of which newer versions compared to mga5 are required.

Have you tried Owncloud client (version 2.2.4) from Mageia5 backports?

Hi Ken,

thanks a lot for the hint with the backports.
I did not have them in mind, and the 2.2.4 owncloud client works great.

Thanks a lot!

Kind regards,
Marcus

Please mzurhorst , don't forget to mark the topic [SOLVED].
You can do so, by editing the subject/title in the first message in this topic.
Write [SOLVED] to the left of subject/title, thanks ahead.

Happy New Year!!!!

Hi!

I have the same problem but tried to upgrade to 2.x without success.
Did added backports repositories but the version I have it's 2.1, not 2.4 (Mageia 5)

Versión: 2.1.0-1.mga5
Grupo: Archivado/Respaldo
Arquitectura: x86_64
Tamaño: 4693 KB
Medio: Core Backports Testing

- lib64ocsync2-2.1.0-1.mga5.x86_64
- lib64owncloudsync2-2.1.0-1.mga5.x86_64
- owncloud-client-2.1.0-1.mga5.x86_64

and when I try to apply changes in order to install I got an '...falló la recuperación: aria2 falló: salió con 3' error (more or less: 'recovery failed. aria2 failed: exited with 3').

Any hint?
Colegota

Please show the output of

Code: Select all: urpmq --list-media active --list-url

Code: Select all: [colegota@alforjas ~]$ urpmq --list-media active --list-url Core Release2 http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/core/release Core Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/core/updates Core Updates Testing http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/core/updates_testing Core Backports http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/core/backports Core Backports Debug http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/debug/core/backports Core Backports Testing http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/core/backports_testing Nonfree Release2 http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/nonfree/release Nonfree Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/nonfree/updates Nonfree Backports http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/nonfree/backports Tainted Release http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/tainted/release Tainted Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/tainted/updates Tainted Backports http://ftp.free.fr/mirrors/mageia.org/distrib/5/x86_64/media/tainted/backports Core 32bit Release http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/core/release Core 32bit Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/core/updates Nonfree 32bit Release http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/nonfree/release Nonfree 32bit Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/nonfree/updates Tainted 32bit Release http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/tainted/release Tainted 32bit Updates http://ftp.free.fr/mirrors/mageia.org/distrib/5/i586/media/tainted/updates

Best disable those again: Core Backports Debug and Core Backports Testing
And what is the output as root of

Code: Select all: urpmi.update -a urpmi owncloud-client

It worked, thanks a lot!

While I'm not sure what was the problem. I did added core backports repository after read this thread, and gives the error, then added backports Debug and Testing just to check.
Seems as if I need to update manually after add a repository but I believed that was automatic.

The outputs:

(*) "está al día" = "It's up to date", "Actualizado" = "Updated"

Code: Select all: [colegota@alforjas ~]$ urpmi.update -a el soporte «Core Release2» está al día el soporte «Core Updates» está al día $MIRRORLIST: media/core/updates_testing/media_info/20170105-183030-synthesis.hdlist.cz soporte «Core Updates Testing» actualizado $MIRRORLIST: media/core/backports/media_info/20170105-135857-synthesis.hdlist.cz soporte «Core Backports» actualizado el soporte «Nonfree Release2» está al día el soporte «Nonfree Updates» está al día $MIRRORLIST: media/nonfree/backports/media_info/20161117-235240-synthesis.hdlist.cz soporte «Nonfree Backports» actualizado el soporte «Tainted Release» está al día el soporte «Tainted Updates» está al día el soporte «Tainted Backports» está al día el soporte «Core 32bit Release» está al día el soporte «Core 32bit Updates» está al día el soporte «Nonfree 32bit Release» está al día el soporte «Nonfree 32bit Updates» está al día el soporte «Tainted 32bit Release» está al día el soporte «Tainted 32bit Updates» está al día

Code: Select all: [root@alforjas colegota]# urpmi owncloud-client Para satisfacer las dependencias, se instalarán los paquetes siguientes: Paquete Versión Revisión Arq. (soporte «Core Release2») lib64nemo-extension 2.4.4 1.mga5 x86_64 lib64nemo-gir3.0 2.4.4 1.mga5 x86_64 (soporte «Core Backports») lib64ocsync2 2.2.4 1.mga5 x86_64 lib64owncloudsync2 2.2.4 1.mga5 x86_64 owncloud-client 2.2.4 1.mga5 x86_64 se utilizarán 6.2MB de espacio de disco adicional. se descargarán 1.7MB de paquetes. ¿Efectuar la instalación de los 5 paquetes? (S/n) $MIRRORLIST: media/core/release/lib64nemo-gir3.0-2.4.4-1.mga5.x86_64.rpm $MIRRORLIST: media/core/release/lib64nemo-extension-2.4.4-1.mga5.x86_64.rpm $MIRRORLIST: media/core/backports/lib64owncloudsync2-2.2.4-1.mga5.x86_64.rpm $MIRRORLIST: media/core/backports/owncloud-client-2.2.4-1.mga5.x86_64.rpm $MIRRORLIST: media/core/backports/lib64ocsync2-2.2.4-1.mga5.x86_64.rpm instalando lib64owncloudsync2-2.2.4-1.mga5.x86_64.rpm lib64nemo-extension-2.4.4-1.mga5.x86_64.rpm owncloud-client-2.2.4-1.mga5.x86_64.rpm lib64nemo-gir3.0-2.4.4-1.mga5.x86_64.rpm lib64ocsync2-2.2.4-1.mga5.x86_64.rpm desde /var/cache/urpmi/rpms Preparando... ############################################################################ 1/5: lib64ocsync2 ############################################################################ 2/5: lib64owncloudsync2 ############################################################################ 3/5: lib64nemo-extension ############################################################################ 4/5: lib64nemo-gir3.0 ############################################################################ 5/5: owncloud-client ############################################################################ quitando paquete lib64ocsync1-1.8.3-1.mga5.x86_64 1/1: quitando lib64ocsync1-1.8.3-1.mga5.x86_64 ############################################################################

And the client it's running and compatible with Nextcloud 11.

Regards!
Colegota

c0legota wrote:Seems as if I need to update manually after add a repository

Yes.

We put the updates of ownCloud client in backports so it is not updated like normal updates - because it is not fully compatible and update may make it stop working.

https://wiki.mageia.org/en/OwnCloud#Upgrading

Mageia forum

[SOLVED] [mga5] Owncloud client v1.8.3 is too old for Nextcl

[SOLVED] [mga5] Owncloud client v1.8.3 is too old for Nextcl

Re: [mga5] Owncloud client v1.8.3 is too old for Nextcloud 1

Re: [mga5] Owncloud client v1.8.3 is too old for Nextcloud 1

Re: [mga5] Owncloud client v1.8.3 is too old for Nextcloud 1

Re: [mga5] Owncloud client v1.8.3 is too old for Nextcloud 1

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne

Re: [SOLVED] [mga5] Owncloud client v1.8.3 is too old for Ne