Am Freitag 14 Januar 2011, 14:01:27 schrieb Carsten Munk: > 2011/1/14 Martin Mohring <[email protected]>: > > On 01/14/2011 02:09 PM, Jan-Simon Möller wrote: > >>> installing rpm-libs-4.8.1-2.2 > >>> installing rpm-libs-x86-arm-4.8.1-7.1 > >>> installing libtool-2.2.6b-1.3 > >>> installing rpm-4.8.1-2.2 > >>> installing cross-armv7l-gcc-accel-armv7l-4.5.1-2.4 > >>> rpmdb: Build signature doesn't match environment > >>> error: db3 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: > >>> Database environment version mismatch > >>> error: cannot open Packages index using db3 - (-30971) > >>> error: cannot open Packages database in /var/lib/rpm > >>> exit ... > >> > >> What happens here: > >> We're re-installing an arm rpm package and thus accessing the rpm-db > >> written by x86 rpm+db4 . This fails in newer db4 versions (picky > >> checking feature). > >> > >> So: meego needs to update its _internal_ version build script release ss > >> this is be addressed there. > >> As it works != kvm, the workers seem to have the right version already. > >> > >> @carsten: can you try this ? Should be as easy as rolling a new build > >> package. > > > > I have cross checked, when the worker runs in KVM mode (same build > > script), it complains with the above error. > > > > When I do a local build without KVM or when the workers are running in > > chroot mode, they do work. > > > > So it must be some install change relating to Virtual Machines that > > causes this. All cases *do use the same build script version*. > > > > Is there a fix for the build script in git, when was it done? > > But what about the 'build' package inside MeeGo? that's likely not the > same version? (At least, that's what I think Jan-Simon is pointing at) > > /Carsten
Exactly. Remember: A VM-Worker picks up the build script of the distribution being built. Best, Jan-Simon _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
