> What command were you using?  Please say what command you were trying
> to run when you were trying to install owncloud.

Sorry, I thought it could be safely assumed I was using

apt-get install owncloud-client

> Of course none of those install owncloud.

Yes, thank you. Those were various proposed solutions from googling
about held broken packages. I never claimed they were supposed to
install owncloud, but possibly solve some underlying issue.

> Did you forget the -t option?  It appears to me that you are trying to
> install owncloud from backports.

> Are you installing from backports?  Or from some place else.  If from
> backports then you don't show it but you need to include the -t
> backports option.

I'm not trying to install from backports, although

apt-get install -t wheezy-backports owncloud-client

gives the same results.

> Here it looks like you are trying to install from owncloud.org not
> Debian.  If you are trying to install from owncloud.org then it looks
> like a bug in owncloud's package that they are depending upon
> something that doesn't exist anymore.  They have an exact dependency,
> the "(=" part, which is fragile.  If you are trying to install their
> packages then you need to get them involved for supporting them.

I actually added that as an attempt to solve the initial problem, which
still presents itself now that I have removed the file
/etc/apt/sources.list.d/owncloud.list entirely. I don't think the
problem has to do with the exact dependency, as that package does exist
with that version in the repo, but that libocsync0 does not exist. 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87383qqybc....@enterprise.kinaa.net

Reply via email to