Hello there,
I'm trying to install the Owncloud client, but so far without luck. I have some experience with Ubuntu, but I'm new to the challenges of Sparky / Debian.
I have found several deb packages and installation guides, but all for debian 8 or 9, not for debian 10. I have found this page: https://packages.debian.org/buster/owncloud-client but I don't know what to do with it. I have downloaded the .deb package but I can't install it. Is it a page to manually add a repository? How do I do that?
Im running the latest Sparky (rolling release).
Thanks in advance for your help!
On 2019-08-28 Owncloud-client has been removed from Debian testing repo , which sparky rolling is based on.
When I'll find some time I will check what was the reason for the removal.
Edit.
Just checked Owncloud-client from Debian unstable repo on my sparky rolling VM. Installation went fine and it seems to be working ok. Owncloud-client package from Debian Sid will be added to sparky testing repo so you , and perhaps others , will be able to install it with apt.
If you can't wait just add Debian unstable repo to your sources.list , and then
sudo apt update
sudo apt install owncloud-client
Start here
https://packages.debian.org/sid/owncloud-client
Go here
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=owncloud-client;dist=unstable
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933290
appears that the tex-live ... is also missing from testing
https://packages.debian.org/sid/texlive-generic-extra
###
edit added looking at
https://download.owncloud.org/download/repositories/production/owncloud/
They talk about Debian 9. The Redhat instuctions appear a bit dated also.
However their git page indicates a very active community.
https://github.com/owncloud/docs
Thanks for the help. Owncloud is up and running now, but a new problem arises. The application asks for the password everytime I log in. It's the same problem as described here: https://askubuntu.com/questions/1037978/owncloud-client-no-service-keychain-available-ubuntu-18-04
The solution is to install libgnome-keyring0, however, the package is no longer available in Debian 10, as described here: https://github.com/notable/notable/issues/725
How to deal with that?
Thanks in advance..
My guess i
ts to go with Sid-Unstable. Another guess is that all of the items missing in Rolling-Testing were coupled with the same transition. Or maybe not
https://packages.debian.org/sid/libgnome-keyring0
No change log for the libgnome... but changelog for gnome-keyring
Quotegnome-keyring (3.34.0-1) unstable; urgency=medium
* New upstream release
* Drop patches applied in new release:
- Remove-tap-gtester-rely-on-GLib-2.38-built-in-TAP-output-.patch
- test-gkd-ssh-agent-service-Avoid-race-condition-with-serv.patch
* Release to unstable
-- Jeremy Bicha <jbicha@debian.org> Mon, 30 Sep 2019 21:08:35 -0400
gnome-keyring (3.31.91-2) experimental; urgency=medium
* Team upload
* d/p/test-gkd-ssh-agent-service-Avoid-race-condition-with-serv.patch:
Add proposed patch to avoid a race condition that can result in the
tests hanging, which seems to be particularly likely on a
single-CPU machine (Closes: #909416)
* d/p/Remove-tap-gtester-rely-on-GLib-2.38-built-in-TAP-output-.patch:
Fix FTBFS with GLib 2.62+ (Closes: #940157)
-- Simon McVittie <smcv@debian.org> Fri, 13 Sep 2019 10:41:22 +0100
I don't know what solution solved the problem, but it works like a charm. Thanks for the help. Much appreciated.
Looking at the Debian package web page for owncloud... it looks like it migrated as planned to Buster. - Sparky6.
Quote from: paxmark1 on October 23, 2019, 06:34:59 PM
Looking at the Debian package web page for owncloud... it looks like it migrated as planned to Buster. - Sparky6.
Sparky 6 is based on Debian bullseye.
Quote from: wybren on October 23, 2019, 11:34:20 AM
I don't know what solution solved the problem, but it works like a charm. Thanks for the help. Much appreciated.
Pavroo added newest Owncloud-client Debian has to offer to Sparky repo. My best guess is that while performing system upgrade you updated your old , manually installed package. That probably fixed your issue