Personally, I don't see the benefit of these errors that are mentioned, and they should be removed.
On Fri, Apr 5, 2019 at 3:49 PM Shawn Wells <[email protected]> wrote: > > On 4/5/19 7:16 AM, Watson Sato wrote: > > > > On Wed, Apr 3, 2019 at 4:49 PM Shawn Wells <[email protected]> wrote: > >> When building off master, I receive the following errors: >> >> >> > ./build_product rhel7 >> > >> > ........ >> > Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_enhanced.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_high.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_intermediary.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_minimal.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/C2S-docker.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/docker-host.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/rhelh-stig.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ansible-tower-upstream.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-http-disa.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ipa-server-upstream.profile. >> > . Skipping None.Could not parse profile >> > >> /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-satellite-upstream.profile. >> >> The ssg-rhel7-ds.xml appears built successfully. "xccdf info" shows the >> profiles and I'm able to scan a host. But not sure what those output >> lines mean -- any pointers? >> >> These profiles are set as documentation_complete: false, and the > build_rule_playbook.py is skipping them during build time. > > > Thank you! > > Does it make sense to start a "build errors FAQ" or some other place to > document common errors and what they mean? Where could be the best place > for that? > > Originally though something under docs/, but not sure if a wiki page is > better/easier. Leaning towards everything as code though. > _______________________________________________ > scap-security-guide mailing list -- > [email protected] > To unsubscribe send an email to > [email protected] > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected] >
_______________________________________________ scap-security-guide mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
