[meta-intel] Retaining of rpm database issue

[Randy MacLeod]

On 2018-01-04 08:30 AM, Raj srinivas wrote:
> Hi all,
> 
> I am using yocto 1.7.3 ,


That version was released in 2014 and is only supported by people in the
community who have time to help:
    https://wiki.yoctoproject.org/wiki/Releases

Can you simplify your workflow and try it on a supported release?

If not, some companies:
    https://www.yoctoproject.org/ecosystem/showcase
including Wind River, do provide Yocto support and services so
you might want to investigate that option.


> I want to get the rpm database in sdk, for that 
> i have added package-management in IMAGE FEATURES, after extracting the 
> sdk, I am not able to rebuild the database , I have tried deleting the db 
> files, still I'm facing below issue, any body can please help on below 
> error,
> 
> bash-3.2# rpm --rebuilddb
> rpmdb: BDB1538 Program version 5.3 doesn't match environment version 6.0
> rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000007: 
> unsupported log version 21
> rpmdb: BDB2527 Invalid log file: log.0000000007: Invalid argument
> rpmdb: BDB0061 PANIC: Invalid argument
> ==> rpmdbe_event_notify(0x2d618, PANIC(0), 0xf6ffd2bc) app_private (nil)
> rpmdb: BDB1546 unable to join the environment
> 
> error: cannot open Packages(0) index: (-30973)
>          DB: Berkeley DB 5.3.28: (September  9, 2013)
> error: cannot open Packages database in /var/lib/rpm
> 
> 
> bash-3.2# rpm -qa
> rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000007: 
> unsupported log version 21
> rpmdb: BDB2527 Invalid log file: log.0000000007: Invalid argument
> rpmdb: BDB0061 PANIC: Invalid argument
> ==> rpmdbe_event_notify(0x2d780, PANIC(0), 0xf6ffe184) app_private (nil)
> rpmdb: BDB1546 unable to join the environment
> 

I don't use the SDK or eSDK much so I could be wrong
but I'm not sure that rebuilding the rpm db in that environment
was supported then or even now in 2.4/master.
I always expect that people will use the SDK to develop their app
then add it back to the build system for production image builds
and deployment. Can you do that?

Anyway, I've found a commit below with a similar signature
that indicates that rpm is trying to access the wrong version of
Berkeley DB so it seems likely that running rpm in the SDK either
has a bug or isn't supported as explained above.

../Randy

> 
> Regards,
> raj
> 
> 

commit e5a40391dfa12c44f31bdb7550df1275edda3864
Author: Hongxu Jia <hongxu.jia at windriver.com>
Date:   Mon Oct 20 19:36:28 2014 +0800

     default-versions.inc: match version of db and db-native while 
"AGPL-3.0" in ${INCOMPATIBLE_LICENSE}

     The db 6.0.30's LICENSE is 'AGPL-3.0', and db 5.3.28 LICENSE is
     'Sleepycat'

     While building rpm image with "AGPL-3.0" in ${INCOMPATIBLE_LICENSE},
     db 6.0.30 and db-native 5.3.28 were built, the different versions
     caused the rpm doesn't work on target.

     ...
     root at qemux86-64:~# rpm -qa
     |rpmdb: BDB2531 Unacceptable log file 
/var/lib/rpm/./log/log.0000000001:
     unsupported log version 21
     |rpmdb: BDB2527 Invalid log file: log.0000000001: Invalid argument
     |rpmdb: BDB0061 PANIC: Invalid argument

$ git branch --contains e5a40391dfa12c44f31bdb7550df1275edda3864
   fido
   jethro
   krogoth
   krogoth-next
   master
* master-next
   morty
   pyro
   rocko


-- 
# Randy MacLeod.  WR Linux
# Wind River an Intel Company