openresty / openresty/openresty-packaging
Jammy packages broken
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 187
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Over the night, we started seeing installs of openresty on Ubuntu 22 jammy start failing:
16.57 E: Failed to fetch http://openresty.org/package/ubuntu/dists/jammy/main/binary-amd64/Packages.gz File has unexpected size (38031 != 35720). Mirror sync in progress? [IP: 3.131.85.84 80]
16.57 Hashes of expected file:
16.57 - Filesize:35720 [weak]
16.57 - SHA512:e7e0c829dad52486e24584a2ce82601a924848330ce929c22b7af349ac86c9733d2e888ff96ccef1a20607d265a92328686a225ce0f2d6fc4d8e8ba38f0cab47
16.57 - SHA256:080a1f85b3a3e1c00fc72dd3d80e84e0aec75a91e086740ae1a966fd139c56a8
16.57 - SHA1:2d3760f30c68db6a537c7934c01049d786c258fa [weak]
16.57 - MD5Sum:06d642d370e97e63d99e047ae51c7b11 [weak]
16.57 Release file created at: Thu, 17 Oct 2024 06:29:21 +0000
16.57 E: Some index files failed to download. They have been ignored, or old ones used instead.
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 reproducing the Ubuntu 22 Jammy install failure and inspect the openresty.org package repository metadata around Packages.gz and its Release file. Done means Jammy package indexes have matching sizes and hashes and a fresh openresty install succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100