Bug 12466 - buildcpio tests still using ftp sources
Summary: buildcpio tests still using ftp sources
Status: RESOLVED INVALID
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Jose Perez C
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-01-05 18:20 UTC by California Sullivan
Modified: 2018-01-05 23:21 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description California Sullivan 2018-01-05 18:20:46 UTC 
Ftp is bad, we should use something else.

Resulted in this error:
https://autobuilder.yocto.io/builders/nightly-rpm-non-rpm/builds/665/steps/Running%20Sanity%20Tests/logs/stdio

Its used in these places:

[clsulliv@clsulliv poky]$ grep -r //ftp meta/lib/oeqa/
meta/lib/oeqa/runtime/cases/buildcpio.py:        uri = 'https://ftp.gnu.org/gnu/cpio'
meta/lib/oeqa/sdk/cases/buildcpio.py:                      "https://ftp.gnu.org/gnu/cpio/cpio-2.12.tar.gz",
Comment 1 California Sullivan 2018-01-05 19:10:48 UTC 
Oops, didn't see that RP already sent a patch addressing this: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146105.html

No need for this bug report.
Comment 2 Armin Kuster 2018-01-05 21:57:32 UTC 
hmm, wont we need this back ported?
Comment 3 Richard Purdie 2018-01-05 23:20:28 UTC 
(In reply to comment #2)
> hmm, wont we need this back ported?

already queued in rocko-next too fwiw.
Comment 4 Richard Purdie 2018-01-05 23:21:36 UTC 
Also to note, the sdk case will already use the copy from DL_DIR if its there rather than downloading.

Its also an https url, not an ftp url, its an ftp domain name, just to be confusing :)