Anyone else seeing this?

sudo apt update
Hit:1 https://download.docker.com/linux/debian bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Err:3 http://deb.debian.org/debian bookworm InRelease
  Temporary failure resolving 'deb.debian.org'
Err:4 http://deb.debian.org/debian-security bookworm-security InRelease
  Temporary failure resolving 'deb.debian.org'
Err:5 http://deb.debian.org/debian bookworm-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

Anyone know how to solve it?

  • Geodad@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    24 hours ago

    I had similar problems because my time was out of sync. I turn off all tracking, so it disabled automatic time syncing.

    • retrolasered@feddit.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Oh yeah, ive had this on a public network where the port for time sync was firewalled and had to pull the time from google to fix