I've been building tde for various architectures (arm, ppc, amd64 ...) and I've come across a couple of issues that maybe somebody could help me with. This is using latest GIT source. I know I could just pull debs from the net.
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?
2. On debian wheezy (yes, I know it's oldstable) tdelibs FTBS.
This is due to heimdal/krb5.h as C++ does not permit struct names and typedef names to be the same or so I believe .... Patching krb5.h on wheezy solves the problem.
Anyway, is that just a case of wheezy is dead long live jessie and folk are not expected to build on wheezy/
Any info, especially regarding 1, greatly appreciated.
Cheers, Mike.
On Sunday 20 of December 2015 17:28:48 Michael Howard wrote:
- 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-r...
These dependencies are available in the official repositories - see http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt... http://mirror.ppa.trinitydesktop.org/trinity/trinity-nightly-build-dependenc...
As apt source can be used also preliminary stable builds repository: deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14
On 20/12/2015 17:11, Slávek Banko wrote:
On Sunday 20 of December 2015 17:28:48 Michael Howard wrote:
- 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 avirtual 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-r...
These dependencies are available in the official repositories - see http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt... http://mirror.ppa.trinitydesktop.org/trinity/trinity-nightly-build-dependenc...
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?
On 20/12/2015 17:29, Michael Howard wrote:
On 20/12/2015 17:11, Slávek Banko wrote:
On Sunday 20 of December 2015 17:28:48 Michael Howard wrote:
- 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 avirtual 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-r...
These dependencies are available in the official repositories - see http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt...
http://mirror.ppa.trinitydesktop.org/trinity/trinity-nightly-build-dependenc...
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?
Apologies for following myself up but, having checked the 'Packages' file again, 'kitchensync-trinity' does indeed depend on 'libopensync0 (>= 0.22)' which begs the question, how does one install 'tde-trinity' on a clean jessie (which I assume people have done?) when 'libopensync0' is not available in jessie? Without fiddling that is.
Or, am I being a bit thick? :)
Mike.
--
On Sunday 20 of December 2015 19:42:55 Michael Howard wrote:
Apologies for following myself up but, having checked the 'Packages' file again, 'kitchensync-trinity' does indeed depend on 'libopensync0 (>= 0.22)' which begs the question, how does one install 'tde-trinity' on a clean jessie (which I assume people have done?) when 'libopensync0' is not available in jessie? Without fiddling that is.
Or, am I being a bit thick?
It is very easy - documentation for installation Trinity always says to use both the "main" repository, and "build-deps". So users do not have to deal with libraries that are not already included in the distribution, but are necessary for Trinity installation. See Trinity wiki:
https://wiki.trinitydesktop.org/DebianInstall
The problem therefore arises basically just for developers, because these packages are not managed in the GIT.
On 20/12/2015 18:59, Slávek Banko wrote:
On Sunday 20 of December 2015 19:42:55 Michael Howard wrote:
Apologies for following myself up but, having checked the 'Packages' file again, 'kitchensync-trinity' does indeed depend on 'libopensync0 (>= 0.22)' which begs the question, how does one install 'tde-trinity' on a clean jessie (which I assume people have done?) when 'libopensync0' is not available in jessie? Without fiddling that is.
Or, am I being a bit thick?
It is very easy - documentation for installation Trinity always says to use both the "main" repository, and "build-deps". So users do not have to deal with libraries that are not already included in the distribution, but are necessary for Trinity installation. See Trinity wiki:
https://wiki.trinitydesktop.org/DebianInstall
The problem therefore arises basically just for developers, because these packages are not managed in the GIT.
Ah, ok, I'm very sorry for being a thicko tonight.
I've always had a problem with RTFM :)
Mike.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/12/20 08:02 PM, Michael Howard wrote:
On 20/12/2015 18:59, Slávek Banko wrote:
On Sunday 20 of December 2015 19:42:55 Michael Howard wrote:
Apologies for following myself up but, having checked the 'Packages' file again, 'kitchensync-trinity' does indeed depend on 'libopensync0 (>= 0.22)' which begs the question, how does one install 'tde-trinity' on a clean jessie (which I assume people have done?) when 'libopensync0' is not available in jessie? Without fiddling that is.
Or, am I being a bit thick?
It is very easy - documentation for installation Trinity always says to use both the "main" repository, and "build-deps". So users do not have to deal with libraries that are not already included in the distribution, but are necessary for Trinity installation. See Trinity wiki:
https://wiki.trinitydesktop.org/DebianInstall
The problem therefore arises basically just for developers, because these packages are not managed in the GIT.
Ah, ok, I'm very sorry for being a thicko tonight.
I've always had a problem with RTFM :)
Mike.
Hi Michael, as long as you make all the packages that you have built available to "apt", there should be no problem to install TDE. I also build and install my own TDE packages from a local repository, so I go through the same process every time.
Cheers Michele
On Sunday 20 of December 2015 18:29:36 Michael Howard wrote:
On 20/12/2015 17:11, Slávek Banko wrote:
On Sunday 20 of December 2015 17:28:48 Michael Howard wrote:
- 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 avirtual 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/dep s-r14
These dependencies are available in the official repositories - see http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ub untu http://mirror.ppa.trinitydesktop.org/trinity/trinity-nightly-build-depend encies/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?
Build-deps in fact are necessary not only at "build time", but they are essential also for user installation - at "run time". For example, akode and libr are for R14.0.x series in build-deps, but are necessary for run time. For R14.1.x are akode and libr already integrated into GIT...
Some packages are in build-deps, because it is an older version of libraries == no longer a part of the distributions and it would be better to update the code so that the libraries will be no longer needed. However, it may require more effort than we have in human resources. For example, library lcms1 - some parts of code has been updated for lcms2, but large applications as digikam and koffice still waiting. And therefore lcms1 is necessary. For such a library seems to be better to update the Trinity code than integrating these libraries into Trinity GIT.
-
Michael Howard -
Michele Calgaro -
Slávek Banko