trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2019

Re: [trinity-devel] Re: Re: Installing from scratch on Debian Stretch from freshly build repository

From: Slávek Banko <slavek.banko@...>
Date: Sun, 10 Feb 2019 01:02:07 +0100
On Saturday 09 of February 2019 22:02:36 deloptes wrote:
> Sl�vek Banko wrote:
> > Hi Emanoil,
> >
> > if you do not have configured any public Trinity repository - stable
> > / nightly builds / preliminary stable builds / preliminary testing
> > builds, and you do not build metapackages in your private repository,
> > then it's quite obvious that you do not have any Trinity metapackages
> > available.
>
> Slavek,
> this is not correct. tde-trinity is in stretch metapackages and I build
> it. It has dependencies on desktop-base-trinity that is not in stretch
> (debian).
>
> I do not know how to explain it better. desktop-base-trinity is only in
> ubuntu.
>
> I could simply remove the dependency from tde-trinity but I am not sure
> what was the intention.
>
> I actually (use case) want to be able to install all tde with
> tde-trinity as described on the web page.
>
> From your and Micheles answer I understand there should be no
> dependency on desktop-base-trinity.
>
> Can you confirm this?
>
> thanks and regards
>

desktop-base-trinity is a metapackage that is built only on Debian by 
default. On Ubuntu this packages is not used because on Ubuntu is a 
metapackage kubuntu-desktop-trinity. In nightly-builds, this is not 
differentiated, and desktop-base-trinity and kubuntu-desktop-trinity are 
built on both Debian and Ubuntu.

As I said before - if you do not build all metapackages, then you do not 
have this metapackage in your repository. As you can see, in Preliminary 
Stable Builds and Preliminary Testing Builds this metapackage is 
avalilable:

http://mirror.ppa.trinitydesktop.org/trinity-sb/pool/main-r14/d/desktop-base-trinity/
http://mirror.ppa.trinitydesktop.org/trinity-testing/pool/main/d/desktop-base-trinity/

Therefore, there is no reason to change the dependency for tde-trinity 
metapackage - dependence is right here. There is no problem in the public 
repositories, but in your local repository.

Cheers
-- 
Sl�vek

Attachments: