On Wed, 29 Apr 2020, Marvin Jones via trinity-users wrote:

>On Wed, 29 Apr 2020, Sl�vek Banko wrote:
>>On Wednesday 29 of April 2020 22:59:46 Marvin Jones via wrote:
>>> Well, this is new.
>>> On a apt-get upgrade:
>>>
>>> W: The repository
>>> 'http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.
>>>0.x xenial Release' does not have a Release file.
>>> N: Data from such a repository can't be authenticated and is therefore
>>>     potentially dangerous to use.
>>> N: See apt-secure(8) manpage for repository creation and user
>>>     configuration details.
>>> W: The repository
>>>  'http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x
>>>    xenial Release' does not have a Release file.
>>> N: Data from such a repository can't be authenticated and is therefore
>>>     potentially dangerous to use.
>>> N: See apt-secure(8) manpage for repository creation and user
>>>     configuration details.
>>>
>>> Ubuntu 16.04 using Trinity 14.07 with Preliminary Stable build.
>>
>>All files are where they should be, including GPG signatures. When you try
>>apt-get update or apt update (or both), what does it say?
>
>Strange...  Now I get the error for _only_ trinity-builddeps-r14.0.x
>
>W: The repository
> 'http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x
>   xenial Release' does not have a Release file.
>N: Data from such a repository can't be authenticated and is therefore
>    potentially dangerous to use.
>N: See apt-secure(8) manpage for repository creation and user
>    configuration details.
>
>As for apt-get update, it looks Just Fine to me:

And, now the "does not have a Release file" error has gone for
the trinity-builddeps-r14.0.x file , and the apt-get dist-upgrade
went to completion with incident.

We will never know....

Jonesy
-- 
  Marvin L Jones     | Marvin     | W3DHJ  | linux
   Pueblo, Colorado  |  @         | Jonesy |  FreeBSD __
    38.238N 104.547W |   jonz.net | DM78rf |          SK