Bug 15793 - meta-java (hardknott) recipes with archive.apache.org in SRC_URI fails to fetch
Summary: meta-java (hardknott) recipes with archive.apache.org in SRC_URI fails to fetch
Status: RESOLVED NOTABUG
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 3.3.4
Hardware: All Multiple
: Undecided major
Target Milestone: 0.0.0
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2025-03-11 13:20 UTC by Enrique Herrera
Modified: 2025-03-13 15:19 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrique Herrera 2025-03-11 13:20:08 UTC
I ran into fetch fails while building my 'hardknott' project, for the first time this year.  It seems any java recipe that uses 'archive.apache.org' to download source code, fails to fetch.  

I was able to find and append xml-commons-resolver link at: https://dlcdn.apache.org//xerces/xml-commons/binaries/xml-commons-resolver-1.2.tar.gz

After I was able to successfully build xml-commons-resolver, then avalon-framework-api failed to fetch.  I suspect all recipes that have links to  archive.apache.org would fail.  

I really do not have time to fix all the recipes that have this issues. 


----

ERROR: xml-commons-resolver1.1-native-1.2-r1 do_fetch: Fetcher failure for URL: 'http://archive.apache.org/dist/xml/commons/xml-commons-resolver-1.2.tar.gz'. Unable to fetch URL from any source.

ERROR: avalon-framework-api-native-4.3-r1 do_fetch: Fetcher failure for URL: 'http://archive.apache.org/dist/excalibur/avalon-framework/source/avalon-framework-api-4.3-src.tar.gz;name=archive'. Unable to fetch URL from any source.
Comment 1 Randy MacLeod 2025-03-13 14:41:30 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).
Comment 2 Randy MacLeod 2025-03-13 15:19:29 UTC
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.