[oe] gitver problems

[Cliff Brake]

On Wed, Jun 2, 2010 at 12:36 PM, Cliff Brake <cliff.brake at gmail.com> wrote:

>> ERROR: Logfile of failure stored in:
>> /scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-3-gd30ab94-r0/temp/log.staging_packager.25337
>> Log data follows:
>> | *** Error: CONTROL/control is missing field Source
>> | The Source field contain the URL's or filenames of the source code
>> and any patches
>> | used to build this package.  Either gnu-style tarballs or Debian
>> source packages
>> | are acceptable.  Relative filenames may be used if they are
>> distributed in the same
>> | directory as the .ipk file.
>> |
>> | ipkg-build: Please fix the above errors and try again.
>> | ERROR: Function staging_packager failed

This patch fixes this issue:

diff --git a/classes/packaged-staging.bbclass b/classes/packaged-staging.bbclass
index 83f3578..6413afb 100644
--- a/classes/packaged-staging.bbclass
+++ b/classes/packaged-staging.bbclass
@@ -374,7 +374,7 @@ staging_packager () {
        if [ "$srcuri" == "" ]; then
                srcuri="OpenEmbedded"
        fi
-       echo "Source: ${SRC_URI}"               >>
${PSTAGE_TMPDIR_STAGE}/CONTROL/control
+       echo "Source: ${srcuri}"               >>
${PSTAGE_TMPDIR_STAGE}/CONTROL/control

        # Deal with libtool not supporting sysroots
        # Need to remove hardcoded paths and fix these when we install the

I'll post the patch in a separate email for review.

The control file in the ipk file then contains:
Package: autotools-demo
Version: 1.0-28-g3a96627-r0.5
Description: Version 1.0-28-g3a96627-r0 of package autotools-demo
Section: base
Priority: optional
Maintainer: Angstrom Developers <angstrom-distro-devel at linuxtogo.org>
License: unknown
Architecture: armv5te
OE: autotools-demo
Homepage: unknown
Depends: libc6, libstdc++6, libgcc1
Source: /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb

Which seems sane, but at some point it might be nice to be able to
specify a URI here without confusing bitbake.

Cliff