| Summary: | meta-java (hardknott) recipes with archive.apache.org in SRC_URI fails to fetch | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Enrique Herrera <Enrique.Herrera> |
| Component: | meta-yocto | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | major | ||
| Priority: | Undecided | CC: | poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 3.3.4 | ||
| Target Milestone: | 0.0.0 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Enrique Herrera
2025-03-11 13:20:08 UTC
That's unfortunate but this isn't a bug for YoctoProject's bugzilla. The content on the internet is unreliable so you should cache your content as is done for some YP vendors (WindRiver for example). Oh and hardknott is no longer supported: https://wiki.yoctoproject.org/wiki/Releases It seems that the EOL was April 2022. The project may need to document which projects are tracked in the YP Bugzilla and/or provide a tool to check but this sort of report isn't so frequent that we can allocate scarce resources to doing that work. The YP bugzilla tracks only certain projects hosted on: https://git.yoctoproject.org/ The meta-java repo and the bugzilla menu system should have helped you to understand that. This wiki may be helpful. https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking Finally, while we aren't supporting hardknott if you have source URLs that you are not able to find and manually fetch yourself, I may have archived some of them as part of WR Linux and I'd be willing to check for you for a few but not 10s or 100s of packages. Good luck. |