<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>11242</bug_id>
          
          <creation_ts>2017-03-24 17:12:49 +0000</creation_ts>
          <short_desc>binary reproducibility: ipk packages never identical</short_desc>
          <delta_ts>2018-02-01 21:08:14 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>opkg</product>
          <component>opkg</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Juro Bystricky">juro.bystricky</reporter>
          <assigned_to name="Alejandro del Castillo">alejandro.delcastillo</assigned_to>
          <cc>joshuagloe</cc>
    
    <cc>randy.macleod</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>71715</commentid>
    <comment_count>0</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2017-03-24 17:12:49 +0000</bug_when>
    <thetext>When trying to achieve binary reproducible packages, .ipk packages are not comparing favourably with neither RPM nor DEB packages.

For core-image-minimal 
(see  https://bugzilla.yoctoproject.org/show_bug.cgi?id=5866 )
we get something like this:

core-image-minimal (with INHERIT +=&quot;reproducible&quot;)
==================================================

       IPK    RPM   DEB
       ----------------
Same:     0   530  3617
Diff:  3868  3338   251
Total: 3868  3868  3868</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79246</commentid>
    <comment_count>1</comment_count>
    <who name="Alejandro del Castillo">alejandro.delcastillo</who>
    <bug_when>2018-01-29 10:27:05 +0000</bug_when>
    <thetext>Gzip by default adds a timestamp to the archive. Modified opkg-build to supress timestamping the gzip archive. Also, added deterministic directory entries sorting, as well as support for SOURCE_DATE_EPOCH. With those fixes, opkg now looks more inline with deb and rpm:

Comparing 2781 files in git/oe-core/build//tmp-glibc/deploy/ipk/ to test_oe/openembedded-core/build//tmp-glibc/deploy/ipk/
Same:  2713 
Different:  68 
Total: 2781</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79251</commentid>
    <comment_count>2</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-01-29 15:57:57 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; Gzip by default adds a timestamp to the archive. Modified opkg-build to
&gt; supress timestamping the gzip archive. Also, added deterministic directory
&gt; entries sorting, as well as support for SOURCE_DATE_EPOCH. With those fixes,
&gt; opkg now looks more inline with deb and rpm:
&gt; 
&gt; Comparing 2781 files in git/oe-core/build//tmp-glibc/deploy/ipk/ to
&gt; test_oe/openembedded-core/build//tmp-glibc/deploy/ipk/
&gt; Same:  2713 
&gt; Different:  68 
&gt; Total: 2781

Great news, is there a patch in ML or upstream?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79253</commentid>
    <comment_count>3</comment_count>
    <who name="Alejandro del Castillo">alejandro.delcastillo</who>
    <bug_when>2018-01-29 16:24:39 +0000</bug_when>
    <thetext>yep, I posted to the ML today [1]. Usually I leave it there for a few days before pulling into the trunk. Once I do that, I&apos;ll close this bug (usually I don&apos;t get a whole lot of feedback from the ML, but still like to leave the patch there for a few days).


[1] https://groups.google.com/forum/#!topic/opkg-devel/sFGFB-W9xM8</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79254</commentid>
    <comment_count>4</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-01-29 16:50:54 +0000</bug_when>
    <thetext>I hade a look at the patch, I like the way you check if really gzip or pigz. I filed a bug complaining about gzip != pigz a while ago.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79255</commentid>
    <comment_count>5</comment_count>
    <who name="Alejandro del Castillo">alejandro.delcastillo</who>
    <bug_when>2018-01-29 16:57:50 +0000</bug_when>
    <thetext>took me a few hours to realize that OE uses pgzip....and that -n on gzip in pgzip is -nT...really annoying, glad there is bug, the discrepancy makes no sense!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79299</commentid>
    <comment_count>6</comment_count>
    <who name="Alejandro del Castillo">alejandro.delcastillo</who>
    <bug_when>2018-02-01 18:01:33 +0000</bug_when>
    <thetext>fixed on 682f8c5e35b8854a9bb858b8ee1714d27e0c00db</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79302</commentid>
    <comment_count>7</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-02-01 19:32:43 +0000</bug_when>
    <thetext>Thanks, however the fix still needs to percolate to opkg-utils recipe in yocto. AFAIK the recipe presently uses a tarball based on release ver 0.3.5. Are you planning a new release as well (i.e. 0.3.6) ? There seems to be quite a number of additional changes since 0.3.5 in master. In any case, the recipe needs to be modified, be it another version or simply git master. If there are no takers (designated maintainers) I don&apos;t mind doing it myself.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79304</commentid>
    <comment_count>8</comment_count>
    <who name="Alejandro del Castillo">alejandro.delcastillo</who>
    <bug_when>2018-02-01 19:51:45 +0000</bug_when>
    <thetext>I am planning the 0.3.6 release of opkg &amp; opkg-utils by mid February. With the release I usually post new recipes as well. Since we are so close to the release, is it OK to wait? if not, the fix can certainly be backported to 0.3.5.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79305</commentid>
    <comment_count>9</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-02-01 21:08:14 +0000</bug_when>
    <thetext>(In reply to comment #8)
&gt; I am planning the 0.3.6 release of opkg &amp; opkg-utils by mid February. With
&gt; the release I usually post new recipes as well. Since we are so close to the
&gt; release, is it OK to wait? if not, the fix can certainly be backported to
&gt; 0.3.5.

Mid February sounds good. Looking forward to it.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>