Hello,

If I try the maintenance from bash, with apt-get ipgrade as root, it performs 
the debian part without problem but doesn't for the TDE part.

The reason seems to be a signature problem.

Herewith the log for that part :

"
Err�:8 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster 
InRelease
  Les signatures suivantes n'ont pas pu �tre v�rifi�es car la cl� publique 
n'est pas disponible�: NO_PUBKEY C93AF1698685AD8B
Lecture des listes de paquets... Fait
W: Erreur de GPG�:�http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb 
buster InRelease�:�Les signatures suivantes n'ont pas pu �tre v�rifi�es car 
la cl� publique n'est pas disponible�: NO_PUBKEY C93AF1698685AD8B
E: Le d�p�t http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster 
InRelease n'est pas sign�.
N: Les mises � jour depuis un tel d�p�t ne peuvent s'effectuer de mani�re 
s�curis�e, et sont donc d�sactiv�es par d�faut.
N: Voir les pages de manuel d'apt-secure(8) pour la cr�ation des d�p�ts et les 
d�tails de configuration d'un utilisateur.
"


On Thursday 19 December 2019 00:46:24 Sl�vek Banko wrote:
> On Wednesday 18 of December 2019 23:43:44 Thierry de Coulon wrote:
> > On Wednesday 18 December 2019 22.04:11 mb850063@... wrote:
> > > Hello,
> > >
> > > I updated from the official TDE version for Debian 9 (stretch).
> > >
> > > It seems an official TDE version for Debian 10 (Buster) doesn't still
> > > exist.
> > >
> > > Only the unofficial version from Slavek.
> > >
> > > However it is some time from now that I upgraded, without any problem
> > > and thru the same link.
> > >
> > > Just that, now, it doesn't work anymore and the maintenance of the
> > > system cannot be performed anymore.
> >
> > Then, as I said, the problem seems to be that Slaveks preliminary stable
> > builds don't seem to be (or no more to be) an upgrade solution for
> > the "standard" stable builds.
> >
> > Newer versions of Slavek's builds work correctly as updates to Slavek's
> > older builds (at leat here).
> >
> > Thierry
>
> Hi,
>
> I'm not sure I understand your statement correctly, but the official
> R14.0.x packages and PSB packages are built from identical source
> packages. Therefore, the result is very similar - it has the same
> dependencies, recommens, conflicts - and it was possible to switch from
> official to PSB as well as from PSB to official (once final version is
> released as official).
>
> Note: Starting with the release of R14.0.7, the official binary packages
> will be identical to the PSB packages.
>
> Cheers