On 2017-04-10 09:09, Jiri Slaby wrote:
"build_compare_status" : "reproducible", "status" : "unreproducible", They are marked as unreproducible, but there is no diff file for them?
In this case, the build_compare_status value tells that our build_compare filters dropped the differences, so this is one of the trickier cases. For OBS it counts as 'the same' , is not re-published and depending builds are not re-triggered, but it is not a true bit-identical reproducible build. I made a patch to my scripts, so that in the future there will be a diff like this one: http://rb.zq1.de/compare.factory-20170410/sparse-compare.out that contains telling lines such as sparse-devel -/usr/lib64/libsparse.a 3bc3e1d236ec48bb645fece5bef2fbb9 0 +/usr/lib64/libsparse.a 3ee192c50ba353019f46f925d836f9c1 0 which might come from file-system ordering differences or embedded timestamps. In this case, it is the latter as can be seen with unrpm sparse-devel*.rpm ar vt usr/lib64/libsparse.a < rw-r--r-- 399/399 1800 Apr 3 11:23 2018 target.o
rw-r--r-- 399/399 1800 Apr 9 13:19 2017 target.o
In Factory and 42.3 we have strip-nondeterminism which can help getting rid of these timestamps. Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org