<?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>231</bug_id>
          
          <creation_ts>2010-08-25 20:33:48 +0000</creation_ts>
          <short_desc>Meet error message prompt when extracting qemu root fs</short_desc>
          <delta_ts>2010-12-21 06:09:40 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>0.9</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>0.9 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="liping Ke">liping.ke</reporter>
          <assigned_to name="Mark Hatle">mark.hatle</assigned_to>
          <cc>jessica.zhang</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>lianhao.lu</cc>
    
    <cc>liping.ke</cc>
    
    <cc>mark.hatle</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>sgw</cc>
    
    <cc>susie.li</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>9399</commentid>
    <comment_count>0</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-08-25 20:33:48 +0000</bug_when>
    <thetext>when we running poky-extract-sdk&lt;poky-sdk-tarball&gt;
&lt;extract-dir&gt;, we met below error:
lke@lke-nhm:/media/contrib/contrib.git/build_new$ poky-extract-sdk
tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2
/home/lke/unfs/kernels/ Extracting rootfs tarball using pseudo...
/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/pseudo -P 
/opt/poky/sysroots/i586-pokysdk-linux/usr tar -C 
&quot;/home/lke/unfs/kernels/&quot; -xjf 
&quot;tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2&quot; tar:
./dev/initctl: Cannot mkfifo: Invalid argument tar: Exiting with 
failure status due to previous errors SDK image successfully extracted 
to /home/lke/unfs/kernels/ 

And also Paste Scott&apos;s comment below
Yes, I saw this too - it is due to an error when tar is extracting a FIFO (something like /dev/initctl if I&apos;m remembering correctly). File a minor bug on this, it may be that pseudo can&apos;t handle FIFOs.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9671</commentid>
    <comment_count>1</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-08 09:11:27 +0000</bug_when>
    <thetext>pseudo is supposed to handle fifos.  So this should not be a problem.

Can you look at /home/lke/unfs/kernels/ and tell me what filesystem that mount point is using?  There are some filesystem types that do not support fifos.  If you happen to be using one this could trigger that error.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9674</commentid>
    <comment_count>2</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-08 10:15:00 +0000</bug_when>
    <thetext>Confirmed with the pseudo author this is a defect in pseudo.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9675</commentid>
    <comment_count>3</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-08 10:21:10 +0000</bug_when>
    <thetext>Upstream is working on a fix....</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9702</commentid>
    <comment_count>4</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-09 08:14:19 +0000</bug_when>
    <thetext>I am unable to run the command: poky-extract-sdk
tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2

What is the configure, commands and steps to generate the poky-image-sdk-qemux86.tar.bz2 file?

I have tried simply running bitbake poky-image-sdk, and I get a .hdimage file, not a tar.bz2.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9707</commentid>
    <comment_count>5</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-09 12:48:22 +0000</bug_when>
    <thetext>Fixed in upstream commit:

e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7

Pull request for the fix will be submitted soon.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9728</commentid>
    <comment_count>6</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2010-09-10 07:44:13 +0000</bug_when>
    <thetext>Fix has been checked in...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9738</commentid>
    <comment_count>7</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-09-11 18:57:41 +0000</bug_when>
    <thetext>Hi, Mark
Did not see the e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7 on the poky/master tree. Is this the commit number of contrib master?

I still meet this error with poky/master last Friday tree. I will verify the latest cs on Monday. When verified, I will change status to verified.

Thanks,
criping</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9903</commentid>
    <comment_count>8</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-09-19 22:58:39 +0000</bug_when>
    <thetext>Verified this bug has been fixed with latest tip of master.
(cs: d1ff9aa4f, Sep 16, RP).</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>