openwrt / openwrt/actions-shared-workflows
Test Build: Failing on some arch caused by untrusted GPG key
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 12
- Forks
- 29
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 2
Description
arm_cortex-a9_vfpv3-d16 mips_24kc mipsel_24kc
https://github.com/openwrt/packages/actions/runs/12027875534?pr=25449
--2024-11-26 09:45:17-- https://downloads.openwrt.org/snapshots/targets/armsr/armv7/sha256sums.asc
Resolving downloads.openwrt.org (downloads.openwrt.org)... 146.75.30.132, 2a04:4e42:77::644
Connecting to downloads.openwrt.org (downloads.openwrt.org)|146.75.30.132|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 299 [text/plain]
Saving to: ‘sha256sums.asc’
0K 100% 23.9M=0s
2024-11-26 09:45:17 (23.9 MB/s) - ‘sha256sums.asc’ saved [299/299]
gpg: Signature made Tue 26 Nov 2024 09:34:36 AM UTC
gpg: using EDDSA key 92C561DE55AE6552F3C736B82B0151090606D1D9
gpg: BAD signature from "OpenWrt Build System (Nitrokey3) <contact@openwrt.org>" [unknown]
Error: Process completed with exit code 1.
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 with the linked GitHub Actions run and inspect the test-build step that downloads and verifies sha256sums.asc. Reproduce the BAD signature on arm_cortex-a9_vfpv3-d16, mips_24kc, or mipsel_24kc, then confirm the affected architectures complete the build successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100