[oe-commits] [Bug 5437] New: packaged-staging freezes

[bugzilla-daemon at git.openembedded.org]

http://bugs.openembedded.org/show_bug.cgi?id=5437

           Summary: packaged-staging freezes
           Product: Openembedded
           Version: org.openembedded.dev
          Platform: ARM
        OS/Version: Linux
            Status: UNCONFIRMED
          Keywords: angstrom
          Severity: normal
          Priority: P3
         Component: unspecified
        AssignedTo: openembedded-commits at lists.openembedded.org
        ReportedBy: henri.bragge at dcombus.com


First I successfully built a custom Angstrom image for an armv5 platform with
PSTAGE_DIR defined outside of the tmp-directory. Then I removed tmp and tried
to build again. This time the building froze after the second pstage package
(coreutils-native) was installed.

Last few rows of the build output shows this:

NOTE: Running task 20 of 2123 (ID: 169,
.../oe/os/openembedded/recipes/coreutils/coreutils-native_7.2.bb, do_setscene)
NOTE: Running task 21 of 2123 (ID: 64,
.../oe/os/openembedded/recipes/quilt/quilt-native_0.48.bb, do_setscene)
Unpacking staging-coreutils-native-i686-linux...Unpacking
staging-quilt-native-i686-linux...Done.
Configuring staging-quilt-native-i686-linux...Done.
Done.
Configuring staging-coreutils-native-i686-linux...Done.
(never goes any further)

If I remove coreutils-native package from PSTAGE_DIR and rebuild, same happens
with a different package. I did not find any reason for this from logs (even
with bitbake -DDD).

I'm building on i686 Debian lenny with bitbake 1.8.18 and OE
06fff17991cf5105cb29d3cec2640995ace329b5 (5/19/2010).

Previously, with OE from April (before packaged-staging.bbclass rewrite) I
didn't have these problems. One difference now is that there used to be only
one DEPLOY_PSTAGE_DIR, but now there is PSTAGE_DIR and PSTAGE_WORKDIR. Should I
define them both outside TMPDIR to be able to reuse staging packages?

-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.