verify initrd.gz/vmlinuz64 local versions are cache invalidated on updates
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 451
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
right now if you have an old linux and install a new one, e.g. updating from https://github.com/maxogden/hypercore/releases/download/v2.0.0/initrd.gz to https://github.com/maxogden/hypercore/releases/download/v2.1.0/initrd.gz, it sees that initrd.gz already exists and skips the new download
this doesn't affect users who use npm install -g linux, as npm deletes the old folder in that case. but we should still make sure we dont accidentally cache the old one for other use cases
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the download and caching path for initrd.gz and vmlinuz64, then reproduce an update from the v2.0.0 URLs to v2.1.0 URLs described in the issue. Done means a newer Linux version does not reuse an older local artifact when the filename is unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100