Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 7503

Raspberry Pi OS • Re: ran sudo apt update and got this any help would be great

$
0
0
Same errors here, or very similar. One thing I do not understand is why it's reporting that the source is for "buster" when /etc/apt/sources.list has only two uncommented lines with "trixie" in them. i.e.:
deb http://deb.debian.org/debian trixie main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security trixie-security main contrib non-free

Mine appears to be throwing errors for (related to node_18.x? and) sqv.

AH HA! (maybe)... I ran raspi-config and noticed that "About" returns "Version: 20231012~bullseye"! hrm.... This is above my paygrade. I would have thought that apt would update raspi-config.

I imagine that a clean installation will fix all of this, but I have heavily modified stuff to enable a very cool btrfs setup along with zigbee and HomeKit integration that I immediately forgot how to set up.

Also, when doing update on raspi-config I get a lot of similar errors:

Code:

sudo raspi-configHit:1 http://deb.debian.org/debian trixie InReleaseHit:2 http://security.debian.org/debian-security trixie-security InReleaseHit:3 https://repo.homebridge.io stable InReleaseGet:4 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B]Err:4 https://deb.nodesource.com/node_18.x bullseye InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 is not bound:            No binding signature at time 2023-08-09T19:27:38Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00ZGet:5 http://archive.raspberrypi.org/debian bullseye InRelease [39.0 kB]Err:5 http://archive.raspberrypi.org/debian bullseye InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on CF8A1AF502A2AA2D763BAE7E82B129927FA3303E is not bound:            No binding signature at time 2026-01-16T15:31:41Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00ZFetched 43.5 kB in 1s (61.0 kB/s)[snip]raspi-config is already the newest version (20231012~bullseye).0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
This tells me that some configuration file *somewhere* has "Get:4 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B]" in it, and needs to be changed to trixie.... The wild random hunt continues!....

Statistics: Posted by captain69 — Wed Feb 04, 2026 7:30 pm — Replies 3 — Views 53



Viewing all articles
Browse latest Browse all 7503

Trending Articles