bitbake package-index broken?

bitbake package-index broken?

[Gary Thomas]

With a recent build, bitbake package-index doesn't seem to do anything.
e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
are no changes.

I tried to build a simple package and add it to my database.  Sadly,
it's not being updated at all, so the new package does not appear on
the board.

Any ideas what might be wrong?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: bitbake package-index broken?

[Gary Thomas]

On 11/24/2010 03:56 AM, Gary Thomas wrote:
> With a recent build, bitbake package-index doesn't seem to do anything.
> e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
> are no changes.
>
> I tried to build a simple package and add it to my database. Sadly,
> it's not being updated at all, so the new package does not appear on
> the board.
>
> Any ideas what might be wrong?

A quick check shows that do_build() in the package-index recipe is never
really run!

I found a workaround by just building an image which has a root file system.
This also forces a package database rebuild.  It would be nice to figure out
what's broken though (it certainly _used_ to work)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: bitbake package-index broken?

[Joshua Lock]

On Wed, 2010-11-24 at 04:33 -0700, Gary Thomas wrote:
> On 11/24/2010 03:56 AM, Gary Thomas wrote:
> > With a recent build, bitbake package-index doesn't seem to do anything.
> > e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
> > are no changes.
> >
> > I tried to build a simple package and add it to my database. Sadly,
> > it's not being updated at all, so the new package does not appear on
> > the board.
> >
> > Any ideas what might be wrong?
> 
> A quick check shows that do_build() in the package-index recipe is never
> really run!
> 
> I found a workaround by just building an image which has a root file system.
> This also forces a package database rebuild.  It would be nice to figure out
> what's broken though (it certainly _used_ to work)
> 

I'm not really familiar with the ipk classes so can't offer a quick
solution, could I ask you to file a bug so that we can track this issue
and assign resources to fix?

Thanks,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre

Re: bitbake package-index broken?

[Gary Thomas]

On 11/24/2010 04:47 AM, Joshua Lock wrote:
> On Wed, 2010-11-24 at 04:33 -0700, Gary Thomas wrote:
>> On 11/24/2010 03:56 AM, Gary Thomas wrote:
>>> With a recent build, bitbake package-index doesn't seem to do anything.
>>> e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
>>> are no changes.
>>>
>>> I tried to build a simple package and add it to my database. Sadly,
>>> it's not being updated at all, so the new package does not appear on
>>> the board.
>>>
>>> Any ideas what might be wrong?
>>
>> A quick check shows that do_build() in the package-index recipe is never
>> really run!
>>
>> I found a workaround by just building an image which has a root file system.
>> This also forces a package database rebuild.  It would be nice to figure out
>> what's broken though (it certainly _used_ to work)
>>
>
> I'm not really familiar with the ipk classes so can't offer a quick
> solution, could I ask you to file a bug so that we can track this issue
> and assign resources to fix?

Done - bug #544

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: bitbake package-index broken?

[Richard Purdie]

On Wed, 2010-11-24 at 05:35 -0700, Gary Thomas wrote:
> On 11/24/2010 04:47 AM, Joshua Lock wrote:
> > On Wed, 2010-11-24 at 04:33 -0700, Gary Thomas wrote:
> >> On 11/24/2010 03:56 AM, Gary Thomas wrote:
> >>> With a recent build, bitbake package-index doesn't seem to do anything.
> >>> e.g. if I look at tmp/deploy/ipk/*/Packages.gz before and after, there
> >>> are no changes.
> >>>
> >>> I tried to build a simple package and add it to my database. Sadly,
> >>> it's not being updated at all, so the new package does not appear on
> >>> the board.
> >>>
> >>> Any ideas what might be wrong?
> >>
> >> A quick check shows that do_build() in the package-index recipe is never
> >> really run!
> >>
> >> I found a workaround by just building an image which has a root file system.
> >> This also forces a package database rebuild.  It would be nice to figure out
> >> what's broken though (it certainly _used_ to work)
> >>
> >
> > I'm not really familiar with the ipk classes so can't offer a quick
> > solution, could I ask you to file a bug so that we can track this issue
> > and assign resources to fix?
> 
> Done - bug #544

I've a fix I'll push shortly. The reason was that we marked do_build as
noexec and package-index did all its work in do_build. The updates
changes this and marks more tasks in that recipe as noexec to make
things more efficient.

Cheers,

Richard

Re: bitbake package-index broken?

[Robert Berger]

Hi,

On 11/28/2010 06:19 PM, Richard Purdie wrote:
>> Done - bug #544
>
> I've a fix I'll push shortly. The reason was that we marked do_build as
> noexec and package-index did all its work in do_build. The updates
> changes this and marks more tasks in that recipe as noexec to make
> things more efficient.
>
> Cheers,
>
> Richard

I use edison-6.0 for arm and package-index does not work as well.

BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        =
"edison-6.0_LOCAL:1924f52cc894d4dd6b9d9c1a2248b32fc0a24c8c"

...

| + '[' -e /work/rber/poky-edison-6.0/tmp/deploy/rpm/any/ ']'
| + for pkgdir in '$packagedirs'
| + '[' -e /work/rber/poky-edison-6.0/tmp/deploy/rpm/all/ ']'
| + echo 'Generating solve db for
/work/rber/poky-edison-6.0/tmp/deploy/rpm/all...'
| Generating solve db for /work/rber/poky-edison-6.0/tmp/deploy/rpm/all...
| + echo /work/rber/poky-edison-6.0/tmp/deploy/rpm/all/solvedb
| + '[' -d /work/rber/poky-edison-6.0/tmp/deploy/rpm/all/solvedb ']'
| + mkdir -p /work/rber/poky-edison-6.0/tmp/deploy/rpm/all/solvedb
| + echo '# Dynamically generated solve manifest'
| + find /work/rber/poky-edison-6.0/tmp/deploy/rpm/all -maxdepth 1 -type f
| + rpm -i --replacepkgs --replacefiles --oldpackage -D '_dbpath
/work/rber/poky-edison-6.0/tmp/deploy/rpm/all/solvedb' --justdb --noaid
--ERROR: Function 'do_package_index' failed (see
/work/rber/poky-edison-6.0/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/package-index-1.0-r0/temp/log.do_package_index.19108
for further information)
| nodeps --noorder --noscripts --notriggers --noparentdirs --nolinktos
--stats --ignoresize --nosignature --nodigest -D '__dbi_txn create
nofsync' /work/rber/poky-edison-6.0/tmp/deploy/rpm/all/solvedb/manifest
|    total:               1      0.000000 MB      0.100765 secs
|    fingerprint:        87      0.003250 MB      0.001950 secs
|    install:            29      0.000000 MB      0.047942 secs
|    dbadd:              29      0.000000 MB      0.046870 secs
|    dbget:             578      0.000000 MB      0.000258 secs
|    dbput:              29      0.250688 MB      0.038620 secs
|    readhdr:           291      0.502176 MB      0.000617 secs
|    hdrload:           145      0.746272 MB      0.001261 secs
|    hdrget:           4794      0.000000 MB      0.002301 secs
| + createrepo /work/rber/poky-edison-6.0/tmp/deploy/rpm
| Traceback (most recent call last):
|   File
"/work/rber/poky-edison-6.0/tmp/sysroots/i686-linux/usr/share/createrepo/genpkgmetadata.py",
line 26, in <module>
|     import rpm
| ImportError: No module named rpm
NOTE: package package-index-1.0-r0: task do_package_index: Failed
ERROR: Task 8 (/work/rber/poky/meta/recipes-core/meta/package-index.bb,
do_package_index) failed with exit code '1'
ERROR: '/work/rber/poky/meta/recipes-core/meta/package-index.bb' failed


I tried to apply your patch:

diff --git a/meta/recipes-core/meta/package-index.bb
b/meta/recipes-core/meta/package-index.bb
index bf3922f..dfb4c1b 100644
--- a/meta/recipes-core/meta/package-index.bb
+++ b/meta/recipes-core/meta/package-index.bb
@@ -19,11 +19,12 @@ do_package_write_deb[noexec] = "1"
 do_populate_sysroot[noexec] = "1"

 do_package_index[nostamp] = "1"
-do_package_index[depends] += "${PACKAGEINDEXDEPS}"
+do_package_index[depends] += "${DEPLOY_DIR_IPK}"
+

 do_package_index() {
        set -ex
-       ${PACKAGEINDEXES}
+       package_update_index_ipk
        set +ex
 }
 addtask do_package_index before do_build


But this does not work as well:

Loading cache...done.
Loaded 1036 entries from dependency cache.
Parsing recipes...done.
Parsing of 795 .bb files complete (794 cached, 1 parsed). 1035 targets,
36 skipped, 0 masked, 0 errors.
ERROR: Error for
/work/rber/poky/meta/recipes-core/meta/package-index.bb, dependency
/work/rber/poky-edison-6.0/tmp/deploy/ipk does not contain ':' character
. Task 'depends' should be specified in the form 'packagename:task'
ERROR: Command execution failed: Exited with 1


Is there a patch against Edison 6.0 to make package-index work?

Regards,

Robert..."If Java had true garbage collection, most programs would
delete themselves upon execution." - Robert Sewell

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1