I had to do a bit more whacking on the script but I can reproduce it, and I end up with the queue looking like:
http://localhost:3851/ubuntu jammy/main amd64 Components - fetch after 0ns - priority 500 http://localhost:3851/ubuntu jammy/main Icons (48x48) - fetch after 0ns - priority 500 http://localhost:3851/ubuntu jammy/main Icons (64x64) - fetch after 0ns - priority 500 http://localhost:3851/ubuntu jammy/main Icons (64x64@2) - fetch after 0ns - priority 500 http://localhost:3851/ubuntu jammy-updates InRelease - fetch after -7975429267ns - priority 1000 Queue fetch after 0ns So if a server fails on the InRelease file but not another it wants to retry that InRelease file, but it gets queued behind lower priority items, so it never gets to actually detect the queue as stuck and cycle it. Note that this means that apt inherently only gets stuck on a server failure, as the queue is per server. ** Changed in: apt (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
