-
Select Topic AreaBug BodyStarting approximately yesterday, we've been getting 404 errors when installing packages on Ubuntu. I tried this script manually and it works fine on my computer. Here are the relevant logs |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Hey @mia-trilo, It looks like your issue might be caused by outdated or missing package information in the APT cache. This can often happen in GitHub Actions when the image has recently changed (e.g., to a new Ubuntu release like noble) and the package mirrors haven’t fully caught up yet. Possible Solutions |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi Mia, it looks like the 404 errors you're encountering during apt install on Ubuntu (likely Noble) in GitHub Actions are caused by outdated or unsynced package mirrors — a common issue shortly after a new Ubuntu release. Since you’re using an ARM64 machine and can’t switch to ubuntu-latest (which requires a custom large-runner), here are a few ways to fix it: If you still encounter missing package errors (e.g., 404 for libarchive-tools), try: Or manually install the missing .deb package if needed: This issue happens when Ubuntu mirrors lag behind the release. You can also consider pinning to ubuntu-22.04 in your workflow if x86_64 is acceptable, or look into GitHub's large runners for ARM64 support: |
Beta Was this translation helpful? Give feedback.
Hey @mia-trilo,
It looks like your issue might be caused by outdated or missing package information in the APT cache. This can often happen in GitHub Actions when the image has recently changed (e.g., to a new Ubuntu release like noble) and the package mirrors haven’t fully caught up yet.
Possible Solutions