404 error when updating Parrot OS Home

I didn’t run sudo apt update && sudo apt full-upgrade for about 2 weeks on Parrot OS Home (on a low powered machine I don’t use frequently) and I encountered a 404 Not Found error.

I was able to update many other packages just fine. However, no matter what I do (even changing mirrors between the default Parrot mirror and MIT in /etc/apt/sources.list.d/parrot.list), I still receive a 404 error for these 11 packages. I’m not sure if this is due to some sort of mirror syncing in process - I had tried updating Parrot more than 12 hours ago.

Also, I am fully using the testing repos, not the rolling repos.

Below is the error I received:

11 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   codium (1.57.0-1623554025 => 1.58.0-1625926890)
   exim4-base (4.94.2-5 => 4.94.2-6)
   exim4-config (4.94.2-5 => 4.94.2-6)
   exim4-daemon-light (4.94.2-5 => 4.94.2-6)
   gnome-desktop3-data (3.38.5-2 => 3.38.5-3)
   libgnome-desktop-3-19 (3.38.5-2 => 3.38.5-3)
   libpq5 (13.2-1 => 13.3-1)
   mat2 (0.12.1-1 => 0.12.1-2)
   python-apt-common (2.2.0 => 2.2.1)
   python3-apt (2.2.0 => 2.2.1)
   python3-lxml (4.6.3-1 => 4.6.3+dfsg-0.1)
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 85.0 MB of archives.
After this operation, 3,993 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Err:1 https://deb.parrot.sh/parrot testing/main amd64 codium amd64 1.58.0-1625926890
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:2 https://deb.parrot.sh/parrot testing/main amd64 exim4-config all 4.94.2-6
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:3 https://deb.parrot.sh/parrot testing/main amd64 exim4-daemon-light amd64 4.94.2-6
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:4 https://deb.parrot.sh/parrot testing/main amd64 exim4-base amd64 4.94.2-6
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:5 https://deb.parrot.sh/parrot testing/main amd64 gnome-desktop3-data all 3.38.5-3
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:6 https://deb.parrot.sh/parrot testing/main amd64 libgnome-desktop-3-19 amd64 3.38.5-3
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:7 https://deb.parrot.sh/parrot testing/main amd64 libpq5 amd64 13.3-1
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:8 https://deb.parrot.sh/parrot testing/main amd64 mat2 all 0.12.1-2
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:9 https://deb.parrot.sh/parrot testing/main amd64 python-apt-common all 2.2.1
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:10 https://deb.parrot.sh/parrot testing/main amd64 python3-apt amd64 2.2.1
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Err:11 https://deb.parrot.sh/parrot testing/main amd64 python3-lxml amd64 4.6.3+dfsg-0.1
  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
Scanning application launchers
Removing duplicate launchers or broken launchers
Launchers are updated
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/c/codium/codium_1.58.0-1625926890_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/e/exim4/exim4-config_4.94.2-6_all.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/e/exim4/exim4-daemon-light_4.94.2-6_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/e/exim4/exim4-base_4.94.2-6_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/g/gnome-desktop3/gnome-desktop3-data_3.38.5-3_all.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/g/gnome-desktop3/libgnome-desktop-3-19_3.38.5-3_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/p/postgresql-13/libpq5_13.3-1_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/m/mat2/mat2_0.12.1-2_all.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/p/python-apt/python-apt-common_2.2.1_all.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/p/python-apt/python3-apt_2.2.1_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]
E: Failed to fetch https://deb.parrot.sh/parrot/pool/main/l/lxml/python3-lxml_4.6.3%2bdfsg-0.1_amd64.deb  404  Not Found [IP: 2607:5300:203:7094:dddd:feed:dead:beef 443]

Look like it is mirror problem rather than Parrot’s team problem. U should comment official repo and try use MIT repo only to see

  1. In the moment, when I was sitting with this issue in front of me, the problem persisted - no matter what mirror I switched to. Well, I only attempted to use 3 mirrors: MIT, Clarkson, and the default Parrot mirror (based on observing output from APT, technically this will contact any available Parrot mirror server per package - but once there is a match between a package and a mirror, the path stays fixed… until all the mirrors are updated, I suppose). I didn’t try any other mirrors because doing so would throw the same error IIRC.
  2. However, I simply waited about a few days later (3 days to 1 week later), and then updating proceeded perfectly fine.

Based on this, I currently believe I experience some sort of mirror lapse/downtime.

The answer is to simply wait later (although I don’t know precisely how long) until you do not get the error message anymore in APT. Yet this explanation I’ve tried to deduce seems a bit unsatisfying to me - mostly because I don’t know or understand why this is happening, even if the answer could be very direct and is possibly not terribly deep.