yaws.spec:74: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/authmod_gssapi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:75: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/haxe.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:76: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/json.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:77: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/jsonrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:78: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/mime_type_c.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:79: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/mime_types.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:80: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws.app
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:81: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:82: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_404.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:83: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_api.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:84: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_app.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:85: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_appmod_cgi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:86: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_cgi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:87: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_compile.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:88: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_config.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:89: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ctl.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:90: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_dav.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:91: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_debug.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:92: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_generated.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:93: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_html.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:94: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_jsonrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:95: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_log.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:96: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_log_file_h.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:97: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ls.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:98: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_pam.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:99: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_revproxy.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:100: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_rpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:101: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_rss.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:102: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sendfile.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:103: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sendfile_compat.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:104: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_server.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:105: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_session_server.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:106: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_soap_lib.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:107: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_soap_srv.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:108: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sup.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:109: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sup_restarts.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:110: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ticker.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:111: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_xmlrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:112: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_zlib.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:113: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/erlsom.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:114: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/soap.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:115: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:116: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws_api.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:117: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws_dav.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:118: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/envelope.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:119: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/epam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:120: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/setuid_drv.so
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:121: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/yaws_sendfile_drv.so
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:122: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/soap.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:123: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/wsdl.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.spec:127: W: libdir-macro-in-noarch-package %{_libdir}/pkgconfig/yaws.pc
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:74: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/authmod_gssapi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:75: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/haxe.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:76: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/json.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:77: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/jsonrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:78: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/mime_type_c.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:79: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/mime_types.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:80: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws.app
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:81: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:82: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_404.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:83: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_api.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:84: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_app.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:85: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_appmod_cgi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:86: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_cgi.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:87: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_compile.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:88: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_config.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:89: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ctl.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:90: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_dav.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:91: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_debug.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:92: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_generated.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:93: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_html.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:94: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_jsonrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:95: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_log.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:96: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_log_file_h.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:97: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ls.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:98: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_pam.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:99: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_revproxy.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:100: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_rpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:101: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_rss.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:102: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sendfile.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:103: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sendfile_compat.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:104: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_server.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:105: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_session_server.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:106: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_soap_lib.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:107: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_soap_srv.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:108: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sup.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:109: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_sup_restarts.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:110: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_ticker.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:111: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_xmlrpc.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:112: W: libdir-macro-in-noarch-package %{_libdir}/yaws/ebin/yaws_zlib.beam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:113: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/erlsom.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:114: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/soap.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:115: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:116: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws_api.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:117: W: libdir-macro-in-noarch-package %{_libdir}/yaws/include/yaws_dav.hrl
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:118: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/envelope.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:119: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/epam
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:120: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/setuid_drv.so
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:121: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/lib/yaws_sendfile_drv.so
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:122: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/soap.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:123: W: libdir-macro-in-noarch-package %{_libdir}/yaws/priv/wsdl.xsd
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src:127: W: libdir-macro-in-noarch-package %{_libdir}/pkgconfig/yaws.pc
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

yaws.src: W: invalid-license MIT/BSD/FIXME
The value of the License tag was not recognized.  Known values are: "AAL",
"Adobe", "ADSL", "AFL", "AGPLv1", "AGPLv3", "AMPAS BSD", "ARL", "ASL 1.0",
"ASL 1.0+", "ASL 1.1", "ASL 1.1+", "ASL 2.0", "ASL 2.0+", "APSL 2.0", "APSL
2.0+", "Artistic 2.0", "Artistic clarified", "BitTorrent", "Boost", "BSD",
"BSD with advertising", "CATOSL", "CeCILL", "CeCILL-B", "CeCILL-C", "CDDL",
"CNRI", "CPAL", "CPL", "Condor", "Copyright only", "Crystal Stacker", "DOC",
"ECL 1.0", "ECL 2.0", "eCos", "EFL 2.0", "EFL 2.0+", "Entessa", "EPL", "ERPL",
"EU Datagrid", "Fair", "FTL", "Giftware", "GL2PS", "Glide", "gnuplot", "GPL+",
"GPL+ or Artistic", "GPLv1", "GPLv2 or Artistic", "GPLv2+ or Artistic",
"GPLv2", "GPLv2 with exceptions", "GPLv2+", "GPLv2+ with exceptions", "GPLv3",
"GPLv3 with exceptions", "GPLv3+", "GPLv3+ with exceptions", "IBM", "IJG",
"ImageMagick", "iMatix", "Imlib2", "Intel ACPI", "Interbase", "ISC", "Jabber",
"JasPer", "LBNL BSD", "LGPLv2", "LGPLv2 with exceptions", "LGPLv2+", "LGPLv2+
or Artistic", "LGPLv2+ with exceptions", "LGPLv3", "LGPLv3 with exceptions",
"LGPLv3+", "LGPLv3+ with exceptions", "libtiff", "LLGPL", "LPL", "LPPL",
"mecab-ipadic", "MIT", "MIT with advertising", "Motosoto", "MPLv1.0",
"MPLv1.0+", "MPLv1.1", "MPLv1.1+", "NCSA", "NetCDF", "NGPL", "NOSL", "Naumen",
"Netscape", "Nokia", "OpenLDAP", "OpenPBS", "OReilly", "OSL 1.0", "OSL 1.0+",
"OSL 1.1", "OSL 1.1+", "OSL 2.0", "OSL 2.0+", "OSL 2.1", "OSL 2.1+", "OSL
3.0", "OSL 3.0+", "OpenSSL", "OReilly", "Phorum", "PHP", "psutils", "Public
Domain", "Python", "Qhull", "QPL", "RiceBSD", "RPSL", "Ruby", "SCRIP",
"Sendmail", "Sleepycat", "SISSL", "SLIB", "SPL", "TCL", "Teeworlds", "TMate",
"UCD", "VOSTROM", "Vim", "VNLSL", "VSL", "W3C", "WTFPL", "wxWidgets", "Xerox",
"xinetd", "YPLv1.1", "Zend", "ZPLv1.0", "ZPLv1.0+", "ZPLv2.0", "ZPLv2.0+",
"ZPLv2.1", "ZPLv2.1+", "zlib", "zlib with acknowledgement", "CDL", "FBSDDL",
"GFDL", "IEEE", "OFSFDL", "Open Publication", "Public Use", "CC-BY", "CC-BY-
SA", "CC-BY-ND", "DSL", "EFML", "Free Art", "GeoGratis", "OAL", "Arphic",
"Baekmuk", "Bitstream Vera", "Hershey", "Liberation", "Lucida", "mplus",
"OFL", "STIX", "Utopia", "XANO", "Redistributable, no modification permitted",
"Freely redistributable without restriction".

yaws.i386: W: log-files-without-logrotate /var/log/yaws
This package contains files in /var/log/ without adding logrotate
configuration for them.

yaws.i386: W: invalid-license MIT/BSD/FIXME
The value of the License tag was not recognized.  Known values are: "AAL",
"Adobe", "ADSL", "AFL", "AGPLv1", "AGPLv3", "AMPAS BSD", "ARL", "ASL 1.0",
"ASL 1.0+", "ASL 1.1", "ASL 1.1+", "ASL 2.0", "ASL 2.0+", "APSL 2.0", "APSL
2.0+", "Artistic 2.0", "Artistic clarified", "BitTorrent", "Boost", "BSD",
"BSD with advertising", "CATOSL", "CeCILL", "CeCILL-B", "CeCILL-C", "CDDL",
"CNRI", "CPAL", "CPL", "Condor", "Copyright only", "Crystal Stacker", "DOC",
"ECL 1.0", "ECL 2.0", "eCos", "EFL 2.0", "EFL 2.0+", "Entessa", "EPL", "ERPL",
"EU Datagrid", "Fair", "FTL", "Giftware", "GL2PS", "Glide", "gnuplot", "GPL+",
"GPL+ or Artistic", "GPLv1", "GPLv2 or Artistic", "GPLv2+ or Artistic",
"GPLv2", "GPLv2 with exceptions", "GPLv2+", "GPLv2+ with exceptions", "GPLv3",
"GPLv3 with exceptions", "GPLv3+", "GPLv3+ with exceptions", "IBM", "IJG",
"ImageMagick", "iMatix", "Imlib2", "Intel ACPI", "Interbase", "ISC", "Jabber",
"JasPer", "LBNL BSD", "LGPLv2", "LGPLv2 with exceptions", "LGPLv2+", "LGPLv2+
or Artistic", "LGPLv2+ with exceptions", "LGPLv3", "LGPLv3 with exceptions",
"LGPLv3+", "LGPLv3+ with exceptions", "libtiff", "LLGPL", "LPL", "LPPL",
"mecab-ipadic", "MIT", "MIT with advertising", "Motosoto", "MPLv1.0",
"MPLv1.0+", "MPLv1.1", "MPLv1.1+", "NCSA", "NetCDF", "NGPL", "NOSL", "Naumen",
"Netscape", "Nokia", "OpenLDAP", "OpenPBS", "OReilly", "OSL 1.0", "OSL 1.0+",
"OSL 1.1", "OSL 1.1+", "OSL 2.0", "OSL 2.0+", "OSL 2.1", "OSL 2.1+", "OSL
3.0", "OSL 3.0+", "OpenSSL", "OReilly", "Phorum", "PHP", "psutils", "Public
Domain", "Python", "Qhull", "QPL", "RiceBSD", "RPSL", "Ruby", "SCRIP",
"Sendmail", "Sleepycat", "SISSL", "SLIB", "SPL", "TCL", "Teeworlds", "TMate",
"UCD", "VOSTROM", "Vim", "VNLSL", "VSL", "W3C", "WTFPL", "wxWidgets", "Xerox",
"xinetd", "YPLv1.1", "Zend", "ZPLv1.0", "ZPLv1.0+", "ZPLv2.0", "ZPLv2.0+",
"ZPLv2.1", "ZPLv2.1+", "zlib", "zlib with acknowledgement", "CDL", "FBSDDL",
"GFDL", "IEEE", "OFSFDL", "Open Publication", "Public Use", "CC-BY", "CC-BY-
SA", "CC-BY-ND", "DSL", "EFML", "Free Art", "GeoGratis", "OAL", "Arphic",
"Baekmuk", "Bitstream Vera", "Hershey", "Liberation", "Lucida", "mplus",
"OFL", "STIX", "Utopia", "XANO", "Redistributable, no modification permitted",
"Freely redistributable without restriction".

yaws.i386: W: no-soname /usr/lib/yaws/priv/lib/setuid_drv.so
yaws.i386: W: no-soname /usr/lib/yaws/priv/lib/yaws_sendfile_drv.so
yaws.i386: E: init-script-without-chkconfig-postin /etc/init.d/yaws
The package contains an init script but doesn't contain a %post with a call to
chkconfig.

yaws.i386: E: init-script-without-chkconfig-preun /etc/init.d/yaws
The package contains an init script but doesn't contain a %preun with a call
to chkconfig.

yaws.i386: W: service-default-enabled /etc/init.d/yaws
The service is enabled by default after "chkconfig --add"; for security
reasons, most services should not be. Use "-" as the default runlevel in the
init script's "chkconfig:" line and/or remove the "Default-Start:" LSB keyword
to fix this if appropriate for this service.

2 packages and 1 specfiles checked; 2 errors, 108 warnings.