Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: drb on 2019/08/31, 15:30:57
-
E: The repository 'http://packages.siduction.org/base unstable Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
E: The repository 'http://packages.siduction.org/extra unstable Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
E: The repository 'http://packages.siduction.org/fixes unstable Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
-
ACK, work in progress (https://forum.siduction.org/index.php?topic=7752.msg63225#msg63225).
-
Thanks!
-
Should work now
-
Dumb question but the first line of the failure "packages.siduction.org/base" is there such a repository or am I missing something?
-
# LANG=C apt update
...
Err:8 https://packages.siduction.org/extra experimental Release
Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 164.68.115.91 443]
...
-
@axt - letsencrypt wollte unbeding das siduction-cert schrotten - nu gibts eins extra für packages
@tommy2 - schmeiss base bloss raus, verwenden wir sein ca 5 oder 6 Jahren nich mehr
-
@melmarker thanks. ;)
-
Sometimes some things last a bit longer - in this special case i had to revert and re-issue the most letsencrypt certificates because certbot mixed them - the next problem was only a few typos.
EDIT: I'm melmarker with my new created account :D So don't worry if i delete it after the first and only use.
-
Only for the records - i've enabled the http:// transport for the siduction repositories again - https:// remains untouched. Main reason for doing so was a kind of not really predictable behaviour with https in our new VM - so for users is no change, https:// only transfer things over a secure connection - not really a must.