https://bugzilla.suse.com/show_bug.cgi?id=1228420 https://bugzilla.suse.com/show_bug.cgi?id=1228420#c4 --- Comment #4 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Michael Andres from comment #2)

In https://build.opensuse.org/project/monitor/zypp:TW is see the yast packages succeeding, at least for TW and Factory.

considering you have 0 of the failing packages from https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:L?blocked=0&building=0&dispatching=0&finished=0&scheduled=0&signing=0&succeeded=0 in your project, I am somewhat not surprised that you don't see the errors The failing packages are:

osc prjresults -V -s F openSUSE:Factory:Staging:L standard i586 (unpublished) | standard x86_64 (unpublished) F F autoyast2 F F yast2 F F yast2-add-on F F yast2-bootloader F F yast2-caasp F F yast2-configuration-management F F yast2-country F F yast2-fcoe-client F F yast2-firewall F F yast2-ftp-server F F yast2-installation F F yast2-iscsi-client F F yast2-kdump F F yast2-network F F yast2-nfs-client F F yast2-nfs-server F F yast2-ntp-client F F yast2-online-update F F yast2-packager F F yast2-rdp x F yast2-registration F F yast2-security F F yast2-services-manager F F yast2-storage-ng F F yast2-tftp-server F F yast2-update F F yast2-users

It's ruby code, yes, but they all fail on importing the Pkg module which is the one interacting with libzypp; and libzypp is the only change in Staging:L impacting the yast stack. -- You are receiving this mail because: You are on the CC list for the bug.