How to cleanup access to Raspberry's repository?

[Toulon7559]

This message links to an observation in another thread that certain required packages cannot be installed.

At the subject Raspberry the standard installation procedures do not find the desired packages.
Turning back to the initial installation action of the procedures, digging deeper and looking at the reporting following CLI

Code: Select all

sudo apt update && sudo apt upgrade

then it seems that for the subject Raspberry-instance the access to Raspberry's repository is 'confused' for unknown reasons.
See the spoiler below

Spoiler: show

Geraakt:1 http://archive.raspberrypi.org/debian bullseye InRelease
Genegeerd:2 https://packages.sury.org/php bullseye InRelease
Fout:3 https://packages.sury.org/php bullseye Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 84.17.46.53 443]
Geraakt:4 http://weewx.com/apt/python2 squeeze InRelease
Genegeerd:5 http://weewx.com/apt/python3 bullseye InRelease
Fout:6 http://weewx.com/apt/python3 bullseye Release
404 Not Found [IP: 34.218.218.142 80]
Pakketlijsten worden ingelezen... Klaar
E: De pakketbron 'https://packages.sury.org/php bullseye Release' heeft geen Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.
E: De pakketbron 'http://weewx.com/apt/python3 bullseye Release' heeft geen Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.
W: Doel Packages (main/binary-armhf/Packages) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1
W: Doel Packages (main/binary-all/Packages) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1
W: Doel Translations (main/i18n/Translation-nl_NL) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1
W: Doel Translations (main/i18n/Translation-nl) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1
W: Doel Translations (main/i18n/Translation-nl_NL.UTF-8) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1
W: Doel Translations (main/i18n/Translation-en) is meerdere keren geconfigureerd in /etc/apt/sources.list.d/php.list:1 en /etc/apt/sources.list.d/sury-php.list:1

The aspect-for-investigation then shifts to an 'off-topic'-question (but still critical for maintenance and installation of software):
how to correct the link to the repository or repositories?
It looks like some corrective action required towards files attached to

Code: Select all

/etc/apt/sources.list.d/

Any hints?

[waltervl]

This is indeed completely off topic, this should be in a raspberry OS forum
But it seems you have added manually (based om some internet instruction) the weewx.com and sury.org entries.
See for example: https://weewx.com/docs/debian.htm

[Toulon7559]

Walter,

The first addition for weewx is obvious (because as instructed during weewx-installation, and not earlier 'harming'),
but the second one (for me) is a question mark, even more related to the reporting in the spoiler of my previous message.
Rummaging in various Raspberry& Linux forums and Github see a reference to this component as element of sources.list,
but do not (yet) see an explanation why it's presence, absence or layout might hinder the access to Raspberry's repository.

Meanwhile weewx (version 4.4.0) no longer active on the subject Raspberry, and therefore weewx-software and the related line in sources.list could be deleted, but doubt that it will make much difference.
IMHO, cause of problem must be 'somewhere else'.
Suspicion (when looking at the error report) that handling of certificate-key needs a repair.
Digging continues .......

[HvdW]

Here's my untouched repository

Code: Select all

deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi

Edit with: sudo nano /etc/apt/sources.list