On Monday 05 of October 2020 00:07:31 Felix Miata wrote:
[1]
# inxi -SI
System: Host: m7ncd Kernel: 4.19.0-11-686 i686 bits: 32 Desktop:
IceWM 1.8.3 Distro: Debian GNU/Linux bullseye/sid Info: Processes:
119 Uptime: 13h 16m Memory: 1002.4 MiB used: 218.0 MiB (21.7%) Shell:
Bash inxi: 3.1.07 # grep rinit /etc/apt/sources.list
deb
http://mirror.xcer.cz/trinity-sb testing deps-r14 main-r14
deb-src
http://mirror.xcer.cz/trinity-sb testing deps-r14 main-r14
# apt update
Hit:1
http://ftp.debian.org/debian testing InRelease
Err:2
http://mirror.xcer.cz/trinity-sb testing InRelease
403 Forbidden [IP: 91.241.23.210 80]
Reading package lists... Done
E: Failed to fetch
http://mirror.xcer.cz/trinity-sb/dists/testing/InRelease 403 Forbidden
[IP: 91.241.23.210 80] E: The repository
'http://mirror.xcer.cz/trinity-sb testing InRelease' is not signed. N:
Updating from such a repository can't be done securely, and is therefore
disabled by default. N: See apt-secure(8) manpage for repository
creation and user configuration details.
What am I missing?
It's not a problem on your side, but on mirror.xcer.cz, where after a
recent outage the services are not in order ... I have to solve it with
the administrator of this server.
In any case, it is recommended to use the new address of the PSB
repository, which is located on the official mirrors - see
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
[2]
# inxi -SI
System: Host: fi965 Kernel: 5.3.18-lp152.26-default x86_64 bits: 64
Desktop: Trinity R14.0.8 Distro: openSUSE Leap 15.2 Info:
Processes: 208 Uptime: N/A Memory: 7.77 GiB used: 446.8 MiB (5.6%)
Shell: Bash inxi: 3.1.07 # cat /etc/zypp/repos.d/TDE*o
[TDE]
autorefresh=0
baseurl=http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/opensus
e15.2/trinity-r14/RPMS/x86_64 enabled=1
gpgcheck=0
name=TDE
type=rpm-md
[TDEnoarch]
autorefresh=0
baseurl=http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/opensus
e15.2/trinity-r14/RPMS/noarch enabled=1
gpgcheck=0
name=TDEnoarch
type=rpm-md
# zypper ref
Retrieving repository 'Libdvdcss' metadata
........................................................................
.........................................................................
..........................................[done] Building repository
'Libdvdcss' cache
........................................................................
.........................................................................
...............................................[done] Repository
'Mozilla' is up to date.
Repository 'NonOSS' is up to date.
Repository 'OSS' is up to date.
Retrieving repository 'TDE' metadata
........................................................................
.........................................................................
...............................................[error] Repository 'TDE'
is invalid.
[
TDE|http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/opensuse15
.2/trinity-r14/RPMS/x86_64] Valid metadata not found at specified URL
History:
-
[
TDE|http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/opensuse15
.2/trinity-r14/RPMS/x86_64] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a
valid repository. Skipping repository 'TDE' because of the above error.
Retrieving repository 'TDEnoarch' metadata
........................................................................
.........................................................................
.........................................[error] Repository 'TDEnoarch'
is invalid.
[
TDEnoarch|http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/open
suse15.2/trinity-r14/RPMS/noarch] Valid metadata not found at specified
URL History:
-
[
TDEnoarch|http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/open
suse15.2/trinity-r14/RPMS/noarch] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a
valid repository. Skipping repository 'TDEnoarch' because of the above
error.
Repository 'Update' is up to date.
Repository 'UpdateNonOSS' is up to date.
Some of the repositories have not been refreshed because of an error.
#
openSUSE 15.1 support terminates in less than 60 days.
openSUSE 15.2 was released 3 months ago.
Are the instructions for 15.2 different from those for 15.1?
When can openSUSE users be expected to be able to upgrade from 15.1 to
15.2? Is a bug report needed?
For a question about the RPM repository, François, who manages RPM
packages, needs to answer. In any case, there is a fact that R14.0.9 is
planned for the end of October, so it is possible that François will delay
the release of packages for OpenSUSE 15.2 until R14.0.9.
Cheers
--
Slávek