On Mon, Apr 20, lyndat3@your-mail.com wrote:

Where are the actual differences logged?

Look at the end of the build log, on the "success", "failed" or whatever state is reported for a given package: https://build.opensuse.org/package/show/Virtualization/xen Each package will be rebuild when a package required for build changes in some way. To reduce the amount packages that get republished we have a tool named "build-compare". It compares the newly built package with the former build. If there are no essential differences the new build is thrown away. If it finds differences then the new package has to be published. This works for 90% of the packages. The remaining packages have either still code bugs like build timestamps, binary hashes or random order if binary objects. In case of xen there are several reasons: one thing is a binary hash inside hvm loader (ipxe), and maybe some remaining timestamps. The other more important bug is the way EFI signing is implemented: the first cycle builds xen as usual, then the resulting binary package is signed in a second build cycle. Unfortunately build-compare runs in the first cycle, it compares the former signed binaries with the newly not yet signed binaries. There are bugs opened already to address this in some way. https://bugzilla.suse.com/show_bug.cgi?id=906160 Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org