Created attachment 3783 [details] diffoscope output showing the difference I built the binutils-doc package twice, two different build folders but otherwise everything else is the same: distro, machine etc. Yet comparing the two builds shows a weird difference (see attached diffoscope output): One package claims to be built by makeinfo version 4.8, the other one by makeinfo 6.1
Created attachment 3794 [details] difooscope output to corrobate the bug claim...
Another weird miscompare (see attached log), different symptomps: this time one build claims: ·Automatically·generated·by·Pod::Man·2.27·(Pod::Simple·3.28) the other one ·Automatically·generated·by·Pod::Man·2.28·(Pod::Simple·3.29)
(In reply to comment #2) > Another weird miscompare (see attached log), different symptomps: > this time one build claims: > ·Automatically·generated·by·Pod::Man·2.27·(Pod::Simple·3.28) > > the other one > > ·Automatically·generated·by·Pod::Man·2.28·(Pod::Simple·3.29) This diff able to reproduce. However, for makeinfo version different have to build few time only can reproduce. Still finding the way to consistently reproduce and root causing..
issue cannot reproduce once binutils updated to version 2.29.
Issue solve once binutils upgrade to version 2.29.
Verification logs: 1) Checkout to origin/master branch to get fixes 2) run command as "Source oe-init-build-env binutils1" 3) change PACKAGE as "deb" in local.conf file 4) build the binutils package 5) run command as "Source oe-init-build-env binutils2" 6) build the package 7) compare two debian package. 8) Both package should be same size.
Verification log , $ diffoscope binutils-doc_bu1_2.29-r0_i386.deb binutils-doc_bu2_2.29-r0_i386.deb --- binutils-doc_bu1_2.29-r0_i386.deb +++ binutils-doc_bu2_2.29-r0_i386.deb +-- file list ¦ @@ -1,3 +1,3 @@ ¦ --rw-r--r-- 0 0 0 4 2017-10-05 11:58:52.000000 debian-binary ¦ --rw-r--r-- 0 0 0 585 2017-10-05 11:58:52.000000 control.tar.gz ¦ --rw-r--r-- 0 0 0 499784 2017-10-05 11:58:52.000000 data.tar.xz ¦ +-rw-r--r-- 0 0 0 4 2017-10-05 13:26:01.000000 debian-binary ¦ +-rw-r--r-- 0 0 0 584 2017-10-05 13:26:01.000000 control.tar.gz ¦ +-rw-r--r-- 0 0 0 499776 2017-10-05 13:26:01.000000 data.tar.xz +-- control.tar.gz ¦ +-- control.tar ¦ ¦ +-- file list ¦ ¦ ¦ @@ -1,2 +1,2 @@ ¦ ¦ ¦ -drwxr-xr-x 0 root (0) root (0) 0 2017-10-05 11:58:52.000000 ./ ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 752 2017-10-05 11:58:52.000000 ./control ¦ ¦ ¦ +drwxr-xr-x 0 root (0) root (0) 0 2017-10-05 13:26:01.000000 ./ ¦ ¦ ¦ +-rw-r--r-- 0 root (0) root (0) 752 2017-10-05 13:26:01.000000 ./control ¦ ¦ ? ¦ ? +-- data.tar.xz ¦ +-- data.tar ¦ ¦ +-- file list ¦ ¦ ¦ @@ -1,30 +1,30 @@ ¦ ¦ ¦ -drwxrwxrwx 0 root (0) root (0) 0 2017-10-05 11:58:52.000000 ./ ¦ ¦ ¦ -drwxr-xr-x 0 root (0) root (0) 0 2017-10-05 11:58:52.000000 ./usr/ ¦ ¦ ¦ -drwxr-xr-x 0 root (0) root (0) 0 2017-10-05 11:58:52.000000 ./usr/share/ ¦ ¦ ¦ -drwxr-xr-x 0 root (0) root (0) 0 2017-10-05 11:58:52.000000 ./usr/share/info/ ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 1127696 2017-10-05 11:58:52.000000 ./usr/share/info/as.info ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 637673 2017-10-05 11:58:52.000000 ./usr/share/info/bfd.info ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 218213 2017-10-05 11:58:52.000000 ./usr/share/info/binutils.info ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 112803 2017-10-05 11:58:52.000000 ./usr/share/info/gprof.info ¦ ¦ ¦ --rw-r--r-- 0 root (0) root (0) 411157 2017-10-05 11:58:52.000000 ./usr/share/info/ld.info
The problem is not 100% reproducible, the problems occurred only once in-a-while. So having two builds that are the same does not mean we will not run into this again. I usually run two builds in parallel, so this may be also a result of some race due to stressed resources. If I run into this again, I will reopen the bug.
I run two builds in parallel, and can able to reproduce the issue in binutils_2.28. Issued is solved in binutils_2.29.
Verified, issue is fixed.