Bug 10577

Summary: Centos 7.2.1511 wrongly not recognised as tested host distribution
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Bas Mevissen <abuse>
Component: meta-yoctoAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED DUPLICATE QA Contact:
Severity: minor    
Priority: Undecided CC: joshuagloe, poky.bs.watcher, poky.watcher
Version: 2.2   
Target Milestone: ---   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Bas Mevissen 2016-11-01 21:29:44 UTC
When running bitbake on a Poky master HEAD of today, the host distro Centos 7.2.1511 is not recognised as a tested host distribution.

This contradicts the information at http://www.yoctoproject.org/docs/{latest,2.2}/ref-manual/ref-manual.html#detailed-supported-distros and the following list in meta-poky/conf/distro/poky.conf:

SANITY_TESTED_DISTROS ?= " \
            poky-1.8 \n \
            poky-2.0 \n \
            poky-2.1 \n \
            poky-2.2 \n \
            Ubuntu-14.04 \n \
            Ubuntu-14.10 \n \
            Ubuntu-15.04 \n \
            Ubuntu-15.10 \n \
            Ubuntu-16.04 \n \
            Fedora-22 \n \
            Fedora-23 \n \
            Fedora-24 \n \
            CentOSLinux-7.* \n \
            Debian-8.* \n \
            openSUSE-13.2 \n \
            SUSELINUX-42.1 \n \
            "

Please fix, as it might be confusing to novice users.

As a side note, it could be added as a comment that the test can be disabled by setting the variable to empty (text based upon CONNECTIVITY_CHECK_URI comment):

# The SANITY_TESTED_DISTROS list is used to compare the host distro against
# to determine whether this distro was tested successfully. To disable the test, 
# set the variable to be empty.

(note that "successfully" was misspelled in the CONNECTIVITY_CHECK_URI comment)
Comment 1 Joshua Lock 2016-11-03 15:23:50 UTC
Fixing the way CentOS is detected in #10591

*** This bug has been marked as a duplicate of bug 10591 ***