<?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>4731</bug_id>
          
          <creation_ts>2013-06-13 17:15:37 +0000</creation_ts>
          <short_desc>Image verification for downloadable BSP images</short_desc>
          <delta_ts>2015-01-30 15:25:12 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>QA/Testing</classification>
          <product>Test Plans/Suite</product>
          <component>test-plans/suite</component>
          <version>1.5</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>5866</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.8 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tom Zanussi">tom.zanussi</reporter>
          <assigned_to name="Lucian Musat">georgex.l.musat</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>corneliux.stoicescu</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>33898</commentid>
    <comment_count>0</comment_count>
    <who name="Tom Zanussi">tom.zanussi</who>
    <bug_when>2013-06-13 17:15:37 +0000</bug_when>
    <thetext>Something that should be done before we put any of the tarballs up on the website, if they contain bootable images, is image verification.

Basically, the reason this is important is that there are customers who download BSP tarballs for BSPs from the downloads section of the website who are able to boot the image, but their own built image isn&apos;t able to boot.  So they try using the metadata in the BSP tarball to re-create the image on their own system and can&apos;t.  It may be because they don&apos;t have the complete settings needed to to that or it may be that the image built and included in the tarball isn&apos;t the one that was generated from the tarball metadata.  Basically, we have no way of knowing unless we can do the same thing ourselves.

I believe it&apos;s also a requirement of the GPL i.e. we need to make available not only the sources but the config used to build the image.  So Beth has put the output of the build as far as the configuration goes along with the images in the build directory containing the output artifacts.

So that&apos;s what this is about - we should be able to recreate the image for any image we bundle in the tarball using the metadata in the tarball and the build settings contained in the build log that the autobuilder is saving in the artifacts directory, just as a customer would i.e. completely from scratch.

This is especially important for any images we get externally, since not only may they have these problems with their tarballs, but they may also be shipping unbootable images that were never tested.  So there are multiple quality problems there that we need to at least have a way of checking before we put those tarballs up on the site, and if we do it for those then we should also do it for the rest, or at least a representative subset.

So basically, as I mentioned I don&apos;t think this should be a big deal, and I&apos;m happy to help in any way I can - I think it&apos;s just a matter of grabbing the relevant settings from the build output, untarring the BSP tarball and doing a build with that metadata along with the poky metadata, from a completely clean state and not using a downloads dir, and then comparing the resulting image with the image in the tarball modulo differences that could come from different dates, etc.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>48435</commentid>
    <comment_count>1</comment_count>
    <who name="Tom Zanussi">tom.zanussi</who>
    <bug_when>2015-01-30 15:25:12 +0000</bug_when>
    <thetext>I think that if bug 5866 is resolved, the results/methods of showing images are identical or not for that bug should be sufficient to show that the output of two BSP builds/images are identical as well, so marking this as a duplicate of that:

Bug 5866 - Reproducible builds: identical binaries

*** This bug has been marked as a duplicate of bug 5866 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>