The introduction of build-mkbaselibs-sle [1] introduced a problem detected by repo_checker that will show up in all letter stagings. x86_64 found conflict of build-mkbaselibs-20170804-3.1.noarch with build-mkbaselibs- sle-20170804-1.1.noarch: - /usr/lib/build/baselibs_global-deb.conf - /usr/lib/build/baselibs_global.conf - /usr/lib/build/mkbaselibs i586 found conflict of build-mkbaselibs-20170804-3.1.noarch with build-mkbaselibs- sle-20170804-1.1.noarch: - /usr/lib/build/baselibs_global-deb.conf - /usr/lib/build/baselibs_global.conf - /usr/lib/build/mkbaselibs The request was approved by the old repo_checker, but given the new package is not in the rings it likely would not have been detected by the new one, prior to acceptance, since it would have never built the new subpackage. Regardless, the proper workflow is to add to the appropriate binaries to the whitelist based on the effected archs (repo_checker-package-whitelist*) and preferably fix the problem. :) It should be a simple conflict added in spec like the other similar packages. I see build-mkbaselibs-sle was added to the whitelist, but not build- mkbaselibs which is the reason the errors keep showing up. Just build- mkbaselibs-sle by itself would prevent installcheck messages from blocking, but file conflict messages that thus involve two package need to have both packages whitelisted. I added build-mkbaselibs to the list [2] which should ignore the messages, but lets get a 1-2 line fix to the package. [1] https://build.opensuse.org/request/show/514523 [2] https://build.opensuse.org/package/rdiff/openSUSE:Factory:Staging/ dashboard?linkrev=base&rev=41709 -- Jimmy -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner@opensuse.org