Update package metadata before installing packages #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On Discord, @FoamyGuy mentioned that some builds were failing at the "install deps" step with a message like: ``` E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev-dev_237-3ubuntu10.33_amd64.deb 404 Not Found [IP: 52.177.174.250 80] ``` This kind of error can occur when the package metadata is out of date and this specific package version was superseded by another in a security update. Ideally, the image supplied by github would always be up to date, but if it's not, then doing the "update" will ensure that the metadata is right at the cost of probably just 1-2s of runtime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Discord, @FoamyGuy mentioned that some builds were failing at the "install deps" step with a message like:
This kind of error can occur when the package metadata is out of date and this specific package version was superseded by another in a security update.
Ideally, the image supplied by github would always be up to date, but if it's not, then doing the "update" will ensure that the metadata is right at the cost of probably just 1-2s of runtime.
(I intended to submit this patch a few weeks ago but accidentally opened a PR against my fork instead, whoops!)