On 20/12/2015 17:11, Sl�vek Banko wrote: > On Sunday 20 of December 2015 17:28:48 Michael Howard wrote: >> 1. On debian jessie, after building, 'aptitude install tde-trinity' >> complains with; >> >> The following packages have unmet dependencies: >> kitchensync-trinity : Depends: libopensync0 (>= 0.22) which is a >> virtual package. >> The following actions will resolve these dependencies: >> >> Keep the following packages at their current version: >> 1) kitchensync-trinity [Not Installed] >> 2) tde-trinity [Not Installed] >> 3) tdepim-trinity [Not Installed] >> >> but, libopensync0 isn't available in jessie. Obviously, the packages >> build because Slavek's repo was in the sources.list. So, what gives? It >> shouldn't need Slavek's repo in the sources.list to install TDE should it? > libopensync0 is available in extra build dependencies repository - see > https://quickbuild.pearsoncomputing.net/~slavek-banko/+archive/ubuntu/deps-r14 > > These dependencies are available in the official repositories - see > http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubuntu > http://mirror.ppa.trinitydesktop.org/trinity/trinity-nightly-build-dependencies/ubuntu > > As apt source can be used also preliminary stable builds repository: > deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14 > Thanks for the reply. Yes, I know the build dependencies are available, that's how I built the packages :) What I was wondering is why, having built all the packages (in a chroot) that I could not _install_ 'tde-trinity ' unless I had a build dependency repo in my sources.list. That should not be necessary, surely? --