gitver problems

gitver problems

[Cliff Brake]

Hello,

I'm trying to put together some examples of using srctree/gitver, and
running into a few issues.

My example is in a bitbake overlay:

git://git.bec-systems.com/openembedded.custom
http://cgit.bec-systems.com/cgit.cgi/openembedded.custom/

This overlay includes a submodule for:

git://git.bec-systems.com/openembedded.custom
http://cgit.bec-systems.com/cgit.cgi/autotools-demo/

and a recipe to build the above submodule:

http://cgit.bec-systems.com/cgit.cgi/openembedded.custom/tree/recipes/autotools-demo/autotools-demo.bb

===================
# recipe to build the ics-test-app in the working tree

inherit srctree gitver autotools

PV = "${GITVER}"
S = "${OEDIR}/openembedded.custom/work/autotools-demo"
==================


When I try 'bitbake autotools-demo', I get the following:

cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
NOTE: Handling BitBake files: / (4602/8385) [54 %]ERROR: 'NoneType'
object has no attribute 'startswith' while parsing
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
attribute 'startswith' while evaluating:
${@get_git_pv('/scratch/oe/oe-build/oe/openembedded.custom/work/autotools-demo',
d)}
NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
attribute 'startswith' while evaluating:
${GITVER}
NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
attribute 'startswith' while evaluating:
${PN}-${EXTENDPE}${PV}-${PR}
NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
attribute 'startswith' while evaluating:
${FILE_DIRNAME}/${PF}/${MACHINE}
ERROR: 'NoneType' object has no attribute 'startswith' while parsing
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
NOTE: Handling BitBake files: \ (8384/8385) [99 %]Command execution
failed: Traceback (most recent call last):
  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/command.py", line 85,
in runAsyncCommand
    self.cooker.updateCache()
  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/cooker.py", line 802,
in updateCache
    if not self.parser.parse_next():
  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/cooker.py", line 995,
in parse_next
    raise ParsingErrorsFound
ParsingErrorsFound

Any suggestions as to what might be going wrong with gitver?

Thanks,
Cliff

Re: gitver problems

[Cliff Brake]

As I continue to ponder this, it seem it makes sense to simple include
the bitbake recipe directly in the application source.  This makes it
very easy and consistent to set the source directory 'S'.  The big
advantage with this is we easily know the location of the source tree
-- its just the same place as the bitbake recipe.

============================
# recipe to build the autotools-demo in the working tree

inherit srctree autotools gitver

PV = "${GITVER}"
S = "${FILE_DIRNAME}"
============================

Now, anyone can add this application to their recipe tree very simply by:

cd <oe>/recipes
git clone git://git.bec-systems.com/autotools-demo
cd -
bitbake autotools-demo

Now, I no longer see the below errors, so that is good.  However, I
see following problem:

cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
NOTE: Handling BitBake files: \ (8385/8385) [100 %]
Parsing of 8385 .bb files complete (7917 cached, 468 parsed). 8306
targets, 333 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 723 of 733 (ID: 0,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_populate_sysroot)
NOTE: Running task 724 of 733 (ID: 6,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_distribute_sources)
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
do_populate_sysroot: Started
NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_configure
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_configure: Started
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
do_distribute_sources: Started
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
do_distribute_sources: Succeeded
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_configure: Succeeded
NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_qa_configure
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_qa_configure: Started
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_qa_configure: Succeeded
NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_compile
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_compile: Started
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_compile: Succeeded
NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_install
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_install: Started
NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_install: Succeeded
FATAL: Unable to start to 'None' UI due to exception: 23634.
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_qa_staging failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_package failed

If anyone is interested in reproducing this problem, it should be very
simple by running the above instructions.

This concept seems fairly useful to me in that it allows device
developers to easily add their custom applications to an OE build, and
everything is on one place.  I think the existing separation of recipe
and work tree makes sense for canned stuff that OE provides, but
device developers need an easier way to do iterative target
development, and I think a working srctree/gitver gives us that.  The
git submodule mechanism is very exciting in that it gives us a
standard way to lock down versions of various submodules without
reverting to manually specifying hash values in recipes, etc.

Thanks,
Cliff

On Mon, May 31, 2010 at 5:12 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
> Hello,
>
> I'm trying to put together some examples of using srctree/gitver, and
> running into a few issues.
>
> My example is in a bitbake overlay:
>
> git://git.bec-systems.com/openembedded.custom
> http://cgit.bec-systems.com/cgit.cgi/openembedded.custom/
>
> This overlay includes a submodule for:
>
> git://git.bec-systems.com/openembedded.custom
> http://cgit.bec-systems.com/cgit.cgi/autotools-demo/
>
> and a recipe to build the above submodule:
>
> http://cgit.bec-systems.com/cgit.cgi/openembedded.custom/tree/recipes/autotools-demo/autotools-demo.bb
>
> ===================
> # recipe to build the ics-test-app in the working tree
>
> inherit srctree gitver autotools
>
> PV = "${GITVER}"
> S = "${OEDIR}/openembedded.custom/work/autotools-demo"
> ==================
>
>
> When I try 'bitbake autotools-demo', I get the following:
>
> cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
> NOTE: Handling BitBake files: / (4602/8385) [54 %]ERROR: 'NoneType'
> object has no attribute 'startswith' while parsing
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
> NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
> attribute 'startswith' while evaluating:
> ${@get_git_pv('/scratch/oe/oe-build/oe/openembedded.custom/work/autotools-demo',
> d)}
> NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
> attribute 'startswith' while evaluating:
> ${GITVER}
> NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
> attribute 'startswith' while evaluating:
> ${PN}-${EXTENDPE}${PV}-${PR}
> NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
> attribute 'startswith' while evaluating:
> ${FILE_DIRNAME}/${PF}/${MACHINE}
> ERROR: 'NoneType' object has no attribute 'startswith' while parsing
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
> NOTE: Handling BitBake files: \ (8384/8385) [99 %]Command execution
> failed: Traceback (most recent call last):
>  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/command.py", line 85,
> in runAsyncCommand
>    self.cooker.updateCache()
>  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/cooker.py", line 802,
> in updateCache
>    if not self.parser.parse_next():
>  File "/scratch/oe/oe-build/oe/bitbake/lib/bb/cooker.py", line 995,
> in parse_next
>    raise ParsingErrorsFound
> ParsingErrorsFound
>
> Any suggestions as to what might be going wrong with gitver?
>
> Thanks,
> Cliff
>

Re: gitver problems

[Chris Larson]

On Mon, May 31, 2010 at 2:54 PM, Cliff Brake <cliff.brake@gmail.com> wrote:

> As I continue to ponder this, it seem it makes sense to simple include
> the bitbake recipe directly in the application source.  This makes it
> very easy and consistent to set the source directory 'S'.  The big
> advantage with this is we easily know the location of the source tree
> -- its just the same place as the bitbake recipe.
>
> ============================
> # recipe to build the autotools-demo in the working tree
>
> inherit srctree autotools gitver
>
> PV = "${GITVER}"
> S = "${FILE_DIRNAME}"
> ============================
>
> Now, anyone can add this application to their recipe tree very simply by:
>
> cd <oe>/recipes
> git clone git://git.bec-systems.com/autotools-demo
> cd -
> bitbake autotools-demo
>
> Now, I no longer see the below errors, so that is good.  However, I
> see following problem:
>
> cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
> NOTE: Handling BitBake files: \ (8385/8385) [100 %]
> Parsing of 8385 .bb files complete (7917 cached, 468 parsed). 8306
> targets, 333 skipped, 1 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Running task 723 of 733 (ID: 0,
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb,
> do_populate_sysroot)
> NOTE: Running task 724 of 733 (ID: 6,
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb,
> do_distribute_sources)
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
> do_populate_sysroot: Started
> NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_configure
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_configure: Started
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
> do_distribute_sources: Started
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task
> do_distribute_sources: Succeeded
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_configure:
> Succeeded
> NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_qa_configure
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_qa_configure:
> Started
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_qa_configure:
> Succeeded
> NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_compile
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_compile: Started
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_compile: Succeeded
> NOTE: autotools-demo-1.0-1-ga33ef01-r0: executing task do_install
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_install: Started
> NOTE: package autotools-demo-1.0-1-ga33ef01-r0: task do_install: Succeeded
> FATAL: Unable to start to 'None' UI due to exception: 23634.
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb
> do_qa_staging failed
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb
> do_package failed
>
> If anyone is interested in reproducing this problem, it should be very
> simple by running the above instructions.
>
> This concept seems fairly useful to me in that it allows device
> developers to easily add their custom applications to an OE build, and
> everything is on one place.  I think the existing separation of recipe
> and work tree makes sense for canned stuff that OE provides, but
> device developers need an easier way to do iterative target
> development, and I think a working srctree/gitver gives us that.  The
> git submodule mechanism is very exciting in that it gives us a
> standard way to lock down versions of various submodules without
> reverting to manually specifying hash values in recipes, etc.
>

If you look at srctree, you'll see that it sets S to FILE_DIRNAME
automatically, so there's no need to do so in the recipe itself.  This is
the sort of thing I intended it to be used for.  submodule is a good idea as
one approach for it.  I have an old repository where I was able to
successfully build busybox, shasum-native, and linux from local source trees
with a '.bb' and '.native.bb' in each, and 'PN' set from the directory name.

I'll see if I can reproduce your issue with your instructions, hopefully we
can get this fixed.  Personally, I really like the idea of having an entire
bitbake/oe overlay where there's no fetch/unpack/patch involved at all, just
builds in local trees.  It would make it so much easier for someone to see
what's happening in a build, in my opinion.  Things aren't 42 levels deep in
TMPDIR.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: gitver problems

[Michael Smith]

On Mon, 31 May 2010, Cliff Brake wrote:

> git submodule mechanism is very exciting in that it gives us a
> standard way to lock down versions of various submodules without
> reverting to manually specifying hash values in recipes, etc.

Before I used OpenEmbedded, I had a custom build system with submodules. 
It was a usability nightmare - there were a lot of cases where the 
submodule tree was pushed but the parent wasn't committed and pushed, or 
vice versa, or somebody reverted to a previous rev of a submodule because 
they didn't "git submodule update" and ran "git commit -a" without 
checking.

For our srctree/gitver projects we almost always want to track the latest 
version, so a shell script that runs "git pull" in every directory works 
much better for us than submodules did.

Mike

Re: gitver problems

[Leon Woestenberg]

Hello,

On Mon, May 31, 2010 at 11:12 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
>
> I'm trying to put together some examples of using srctree/gitver, and
> running into a few issues.
>
> cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
> NOTE: Handling BitBake files: / (4602/8385) [54 %]ERROR: 'NoneType'
> object has no attribute 'startswith' while parsing
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
> NOTE: <type 'exceptions.AttributeError'>:'NoneType' object has no
> attribute 'startswith' while evaluating:

Would like to add a "me too".  I recently hit this problem with
overlays only, I wasn't even playing with srctree nor gitver.

Apart from a non-conclusive IRC discussion, I didn't investigate
further, expecting a misconfiguration on my side somewhere.

Regards,
-- 
Leon

Re: gitver problems

[Cliff Brake]

-vvvv provides a little more info ...


NOTE: Running task 729 of 733 (ID: 8,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage)
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_package_stage failed
NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage: Started
ERROR: Task 8 (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage) failed with 256
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed
ERROR: Function staging_packager failed
NOTE: Task failed: ('function staging_packager failed',
'/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-2-ga58ca94-r0/temp/log.staging_packager.26542')
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-2-ga58ca94-r0/temp/log.staging_packager.26542
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
NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage: Failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_package_stage failed
ERROR: Task 8 (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage) failed with 256
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed

So we need a way to provide Source URL's for packaging ...

Cliff

Re: gitver problems

[Chris Larson]

On Mon, May 31, 2010 at 3:04 PM, Cliff Brake <cliff.brake@gmail.com> wrote:

> -vvvv provides a little more info ...
>
>
> NOTE: Running task 729 of 733 (ID: 8,
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb,
> do_package_stage)
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb
> do_package_stage failed
> NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage:
> Started
> ERROR: Task 8
> (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb,
> do_package_stage) failed with 256
> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb'
> failed
> ERROR: Function staging_packager failed
> NOTE: Task failed: ('function staging_packager failed',
>
> '/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-2-ga58ca94-r0/temp/log.staging_packager.26542')
> 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-2-ga58ca94-r0/temp/log.staging_packager.26542
> 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
> NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage:
> Failed
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb
> do_package_stage failed
> ERROR: Task 8
> (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb,
> do_package_stage) failed with 256
> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb'
> failed
> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
> autotools-demo.bb'
> failed
>
> So we need a way to provide Source URL's for packaging ...


Last time I looked at that part of the packaging classes and SRC_URI, they
fell back to ${FILE} if SRC_URI was unset, which while not particularly
useful, seems a reasonable way to do it.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: gitver problems

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01-06-10 00:21, Chris Larson wrote:
> On Mon, May 31, 2010 at 3:04 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
> 
>> -vvvv provides a little more info ...
>>
>>
>> NOTE: Running task 729 of 733 (ID: 8,
>> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb,
>> do_package_stage)
>> ERROR: TaskFailed event exception, aborting
>> ERROR: Build of
>> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb
>> do_package_stage failed
>> NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage:
>> Started
>> ERROR: Task 8
>> (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb,
>> do_package_stage) failed with 256
>> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb'
>> failed
>> ERROR: Function staging_packager failed
>> NOTE: Task failed: ('function staging_packager failed',
>>
>> '/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-2-ga58ca94-r0/temp/log.staging_packager.26542')
>> 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-2-ga58ca94-r0/temp/log.staging_packager.26542
>> 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
>> NOTE: package autotools-demo-1.0-2-ga58ca94-r0: task do_package_stage:
>> Failed
>> ERROR: TaskFailed event exception, aborting
>> ERROR: Build of
>> /scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb
>> do_package_stage failed
>> ERROR: Task 8
>> (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb,
>> do_package_stage) failed with 256
>> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb'
>> failed
>> ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/
>> autotools-demo.bb'
>> failed
>>
>> So we need a way to provide Source URL's for packaging ...
> 
> 
> Last time I looked at that part of the packaging classes and SRC_URI, they
> fell back to ${FILE} if SRC_URI was unset, which while not particularly
> useful, seems a reasonable way to do it.

If it's unset yet, not if it's empty. Doing SRC_URI = "" will trigger
such bugs.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMBKx3MkyGM64RGpERAjWLAKCsM0RCKkRWy1ONqsbaKrqqRFgbqgCcCDt8
OXAWpfhG1YeKsi7S5fyQwtg=
=2zoW
-----END PGP SIGNATURE-----

Re: gitver problems

[Cliff Brake]

Working on this some more this morning ...

As mentioned previously, the example located:

http://cgit.bec-systems.com/cgit.cgi/autotools-demo/

Can simply be cloned into your recipes directory, and then 'bitbake
autotools-demo'

I'm still getting a several errors, but the interesting thing is that
if I run bitbake 3 times, it finally succeeds.

Cliff

cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
NOTE: Handling BitBake files: - (8388/8388) [100 %]
Parsing of 8388 .bb files complete (7920 cached, 468 parsed). 8310
targets, 333 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 723 of 733 (ID: 0,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_populate_sysroot)
NOTE: Running task 724 of 733 (ID: 6,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_distribute_sources)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_populate_sysroot: Started
NOTE: autotools-demo-1.0-3-gd30ab94-r0: executing task do_configure
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_configure: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_distribute_sources: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_distribute_sources: Succeeded
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_configure: Succeeded
NOTE: autotools-demo-1.0-3-gd30ab94-r0: executing task do_qa_configure
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_qa_configure: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_qa_configure: Succeeded
NOTE: autotools-demo-1.0-3-gd30ab94-r0: executing task do_compile
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_compile: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_compile: Succeeded
NOTE: autotools-demo-1.0-3-gd30ab94-r0: executing task do_install
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_install: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_install: Succeeded
FATAL: Unable to start to 'None' UI due to exception: 23868.




cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
NOTE: Handling BitBake files: - (8388/8388) [100 %]
Parsing of 8388 .bb files complete (7921 cached, 467 parsed). 8310
targets, 333 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 724 of 733 (ID: 5,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package: Succeeded
NOTE: Running task 727 of 733 (ID: 10,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_write_ipk)
Packaged contents of autotools-demo-dbg into
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/deploy/glibc/ipk/armv5te/autotools-demo-dbg_1.0-3-gd30ab94-r0.5_armv5te.ipk
Packaged contents of autotools-demo into
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/deploy/glibc/ipk/armv5te/autotools-demo_1.0-3-gd30ab94-r0.5_armv5te.ipk
Packaged contents of autotools-demo-dev into
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/deploy/glibc/ipk/armv5te/autotools-demo-dev_1.0-3-gd30ab94-r0.5_armv5te.ipk
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_package_write_ipk: Started
NOTE: Not creating empty archive for autotools-demo-doc-1.0-3-gd30ab94-r0.5
NOTE: Not creating empty archive for autotools-demo-static-1.0-3-gd30ab94-r0.5
NOTE: Not creating empty archive for autotools-demo-locale-1.0-3-gd30ab94-r0.5
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_package_write_ipk: Succeeded
NOTE: Running task 728 of 733 (ID: 4,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_write)
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-3-gd30ab94-r0/staging-pkg/deploy/glibc/ipk/armv5te/
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-3-gd30ab94-r0/staging-pkg/deploy/glibc/ipk/armv5te/
/scratch/oe/oe-build/oe/build/angstrom-2008.1/tmp/work/armv5te-angstrom-linux-gnueabi/autotools-demo-1.0-3-gd30ab94-r0/staging-pkg/deploy/glibc/ipk/armv5te/
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package_write: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package_write: Succeeded
NOTE: Running task 729 of 733 (ID: 8,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage)
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_package_stage failed
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package_stage: Started
ERROR: Task 8 (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage) failed with 256
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed
ERROR: Function staging_packager failed
NOTE: Task failed: ('function staging_packager failed',
'/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')
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
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_package_stage: Failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb
do_package_stage failed
ERROR: Task 8 (/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage) failed with 256
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed
ERROR: '/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb'
failed




cbrake@happy:/scratch/oe/oe-build/oe$ bitbake autotools-demo
NOTE: Handling BitBake files: - (8388/8388) [100 %]
Parsing of 8388 .bb files complete (7921 cached, 467 parsed). 8310
targets, 333 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 728 of 733 (ID: 7,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_package_stage_all)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_package_stage_all: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task
do_package_stage_all: Succeeded
NOTE: Running task 731 of 733 (ID: 2,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_build)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_build: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_build: Succeeded
NOTE: Running task 732 of 733 (ID: 9,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_rm_work)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_rm_work: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_rm_work: Succeeded
NOTE: Running task 733 of 733 (ID: 1,
/scratch/oe/oe-build/oe/openembedded.custom/recipes/autotools-demo/autotools-demo.bb,
do_rm_work_all)
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_rm_work_all: Started
NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_rm_work_all: Succeeded
NOTE: Tasks Summary: Attempted 733 tasks of which 729 didn't need to
be rerun and 0 failed.

Re: gitver problems

[Cliff Brake]

> NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_install: Started
> NOTE: package autotools-demo-1.0-3-gd30ab94-r0: task do_install: Succeeded
> FATAL: Unable to start to 'None' UI due to exception: 23868.

Some bitbake fixes that fix the above error:

http://cgit.bec-systems.com/cgit.cgi/bitbake/log/?h=cbrake/1.10-srctree-fixes

The first patch is just for logging.  The second patch fixes an issue
where we are deleting an empty dictionary.  I'm not sure if this is a
valid fix, but perhaps someone who understands bitbake task handling
can review.

Working on the following error now.

> 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

Cliff

Re: gitver problems

[Cliff Brake]

On Wed, Jun 2, 2010 at 12:36 PM, Cliff Brake <cliff.brake@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@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