The biggest problem with Debian 13 is not with Debian, it's with people like Google and Cloudflare.

Come on guys, Debian 13 has been in testing for months, and you can't be arsed to update your apt repos from bookworm to trixie by release, or even weeks after release? That's embarrassing.

      ~ sudo apt update --audit
    [...]
    Hit:8 https://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease
    Hit:10 https://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease
    Hit:11 https://pkg.cloudflareclient.com bookworm InRelease
    Hit:12 https://pkg.cloudflare.com/cloudflared bookworm InRelease
    [...]
    Fetched 407 kB in 2s (222 kB/s)
    2 packages can be upgraded. Run 'apt list --upgradable' to see them.
    Warning: https://pkg.cloudflare.com/cloudflared/dists/any/InRelease: Policy will reject signature within a year, see --audit for details
    Audit: https://pkg.cloudflare.com/cloudflared/dists/any/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is:
       Signing key on FBA8C0EE63617C5EED695C43254B391D8CACCBF8 is not bound:
                  No binding signature at time 2025-08-21T15:58:52Z
         because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance
         because: SHA1 is not considered secure since 2026-02-01T00:00:00Z

These apt repos are still bookworm-only after the trixie release, and it's been weeks. And Cloudflare is still stuck on SHA1.

  $ curl -s https://packages.cloud.google.com/apt/dists/cloud-sdk-trixie/InRelease | grep -E Suite:\|Date:
  Suite: cloud-sdk-trixie
  Date: Wed, 27 Aug 2025 18:45:14 UTC
  $ curl -s https://packages.cloud.google.com/apt/dists/google-compute-engine-trixie-stable | grep -E Suite:\|Date:
  Suite: google-compute-engine-trixie-stable
  Date: Mon, 25 Aug 2025 21:24:03 UTC