<?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>2313</bug_id>
          
          <creation_ts>2012-04-17 14:29:16 +0000</creation_ts>
          <short_desc>bitbake fails to build against lockdown exported file</short_desc>
          <delta_ts>2012-04-18 15:44:17 +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>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>(1.2)</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jiajun Xu">jiajun.xu</reporter>
          <assigned_to name="Lianhao Lu">lianhao.lu</assigned_to>
          <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>20529</commentid>
    <comment_count>0</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-04-17 14:29:16 +0000</bug_when>
    <thetext>tree/branch: poky/1.2_M4
commit: fae1c7a5fdcea199338b5f91efaafd7c72aec5dd

In 1.2 M4 RC3, I find that bitbake fails to build against lockdown exported file, which could pass in 1.2 M4 RC2.

The error log as below:
########
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 170 of 689 (ID: 105, /home/jxu49/osel/poky/meta/recipes-core/eglibc/eglibc_2.13.bb, do_install)
NOTE: Running task 357 of 689 (ID: 442, /home/jxu49/osel/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.2.bb, do_package)
NOTE: Running task 381 of 689 (ID: 539, virtual:native:/home/jxu49/osel/poky/meta/recipes-core/gettext/gettext_0.18.1.1.bb, do_compile)
NOTE: package eglibc-2.13-r23+svnr15508: task do_install: Started
NOTE: package linux-libc-headers-3.2-r1: task do_package: Started
ERROR: Can NOT get PRAUTO from lockdown exported file
ERROR: Function failed: package_get_auto_pr
ERROR: Logfile of failure stored in: /home/jxu49/osel/poky/pr/tmp/work/i586-poky-linux/linux-libc-headers-3.2-r1/temp/log.do_package.30482
NOTE: package linux-libc-headers-3.2-r1: task do_package: Failed
NOTE: package gettext-native-0.18.1.1-r11: task do_compile: Started
ERROR: Task 442 (/home/jxu49/osel/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.2.bb, do_package) failed with exit code &apos;1&apos;
Waiting for 2 running tasks to finish:
0: eglibc-2.13-r23+svnr15508 do_install (pid 30479)
1: gettext-native-0.18.1.1-r11 do_compile (pid 30485)
NOTE: package gettext-native-0.18.1.1-r11: task do_compile: Succeeded
Waiting for 1 running tasks to finish:
0: eglibc-2.13-r23+svnr15508 do_install (pid 30479)
NOTE: package eglibc-2.13-r23+svnr15508: task do_install: Succeeded
NOTE: Tasks Summary: Attempted 600 tasks of which 597 didn&apos;t need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/jxu49/osel/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.2.bb, do_package
########

The steps I use to reproduce the issue as below:
1. prepare 2 poky build environments
2. in one of the poky source, set PRSERV_HOST to localhost and PRSERV_PORT to 0 in local.conf
4. run &quot;bitbake man&quot; and then add following lines into man_${PV}.bb
#######
do_package_append() {
        bb.build.exec_func(&apos;do_test_prserv&apos;, d)
}

do_test_prserv() {
 echo &quot;Test if PR service could work&quot;
}
#######
7. re-run &quot;bitbake man&quot;, and check the deploy folder if the packages for man are re-generated with PR number bump up
8. run &quot;bitbake-prserv-tool export export.inc&quot;
9. in the second poky source, set PRSERV_HOST to localhost and PRSERV_PORT to 0 in local.conf
10. run &quot;bitbake -R export.inc man&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20613</commentid>
    <comment_count>1</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2012-04-18 02:52:30 +0000</bug_when>
    <thetext>can NOT reproduce the issue using the steps mentioned in comment #1.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20614</commentid>
    <comment_count>2</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2012-04-18 03:11:11 +0000</bug_when>
    <thetext>After a discussion with Jiaju,  it seems that in the &quot;exporter&quot; building, many required packages do_package task(i.e. eglibc, libgcc, bash, etc) are not executed, which result in incomplete information stored in the PR database. We guess these tasks might be executed before enabling the local PR database.

He&apos;ll use a clean environment to verify this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20653</commentid>
    <comment_count>3</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-04-18 15:44:17 +0000</bug_when>
    <thetext>I tried a clean build and now lockdown exported file could work. Mark the bug as INVALID.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>