ocaml-zarith-devel.x86_64: W: invalid-license-exception OCaml-LGPL-linking-exception ocaml-zarith.src: W: invalid-license-exception OCaml-LGPL-linking-exception ocaml-zarith.x86_64: W: invalid-license-exception OCaml-LGPL-linking-exception The ' WITH ' license exception of the License tag was not recognized. Known values are: "389-exception", "Autoconf-exception-2.0", "Autoconf- exception-3.0", "Bison-exception-2.2", "CLISP-exception-2.0", "Classpath- exception-2.0", "DigiRule-FOSS-exception", "FLTK-exception", "Fawkes-Runtime- exception", "Font-exception-2.0", "GCC-exception-2.0", "GCC-exception-3.1", "LZMA-exception", "Libtool-exception", "Nokia-Qt-exception-1.1", "OCCT- exception-1.0", "Qwt-exception-1.0", "WxWindows-exception-3.1", "eCos- exception-2.0", "freertos-exception-2.0", "gnu-javamail-exception", "i2p-gpl- java-exception", "mif-exception", "openvpn-openssl-exception", "u-boot- exception-2.0". ocaml-zarith-devel.x86_64: W: static-library-without-debuginfo /usr/lib64/ocaml/zarith/libzarith_c_stubs.a The static library doesn't contain any debuginfo. Binaries linking against this static library can't be properly debugged. ocaml-zarith.x86_64: W: unstripped-binary-or-object /usr/lib64/ocaml/zarith/zarith.cmxs stripping debug info from binaries happens automatically according to global project settings. So there's normally no need to manually strip binaries. Left over unstripped binaries could therefore indicate a bug in the automatic stripping process. 3 packages and 0 specfiles checked; 0 errors, 5 warnings.