| Summary: | app-emulation/firecracker-bin keyword request for ~arm64 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sebastian Hamann <gentoo-bugs> |
| Component: | Keywording | Assignee: | Sebastian Hamann <gentoo-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | proxy-maint, sam |
| Priority: | Normal | Keywords: | CC-ARCHES, KEYWORDREQ |
| Version: | unspecified | Flags: | nattka:
sanity-check+
|
| Hardware: | ARM64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: |
app-emulation/firecracker-bin-0.24.1 ~arm64
app-emulation/firecracker-bin-0.24.2 ~arm64
|
Runtime testing required: | --- |
|
Description
Sebastian Hamann
2020-09-07 18:52:26 UTC
Unable to check for sanity:
> package masked: app-emulation/firecracker-bin-0.22.0, by keywords: -arm64
Looks like arm64? ( ... ) should be in the ebuild first. Oh, I see. It has "-* ~amd64". Maybe it should have been: "-(all other arches but amd64, arm64) ~amd64"? I accept this is a bit of a quirk. I'll get on this. (In reply to Sam James from comment #3) > Oh, I see. It has "-* ~amd64". > > Maybe it should have been: "-(all other arches but amd64, arm64) ~amd64"? I > accept this is a bit of a quirk. I'll get on this. Should I change the ebuild like this? Since upstream only provides binaries for amd64 and arm64, I'd rather explicitly keyword these two than "unkeyword" every other arch that Gentoo currently supports. Unable to check for sanity:
> package masked: app-emulation/firecracker-bin-0.22.1, by keywords: -arm64
All sanity-check issues have been resolved Unable to check for sanity:
> no match for package: app-emulation/firecracker-bin-0.23.0
arm64 team, are there problems with this? This has been open for quite some time now. All sanity-check issues have been resolved arm64 done all arches done |