General discussion • Issues with Trixie "InRelease" Repos

I'm in the process of building out a couple of new 8Gb Pi4B machines to take up new infrastructure roles and as part of that I'm undertaking my first attempt at locally-hosted email services (Postfix, Dovecot).

Running a "sudo apt update" this evening [May 1st, 2026], I'm getting multiple errors relating to a signature error with the "InRelease" repo at

http://archive.raspberrypi.com/debian/d ... /InRelease

Asking Google whether or not there are any known issues with the Repos for Trixie, I received back that as of late April, there are documented issues regarding the Debian Trixie repos, with the root cause apparently being a stricter level of enforcement of SHA1 deprecation policies on new Trixie installations.

I'm curious to know if anyone else is running Trixie and, if so, if anyone else has seen this issue. It seems a bit odd that breakages of this nature would be making it in to the upstream repos - should this not be something that Raspberry Pi themselves are in a position to prevent happening?

Interested to know if people think this warrants a bug report at github...

Thanks in advance...

Statistics: Posted by sproggit — Fri May 01, 2026 8:14 pm

---