This is probably more useful output:

-bash-4.2# rpm -i
/usr/src/rpm/RPMS/x86_64/rpm-libs-5.4.8-0.20120511.x86_64.rpm -vvv
D: pool fd:     created size 392 limit -1 flags 0
D: pool ts:     created size 1200 limit -1 flags 0
D: pool gi:     created size 176 limit -1 flags 0
D: pool dig:    created size 408 limit -1 flags 0
D: pool h:      created size 360 limit -1 flags 0
D: Expected size:      2986177 = lead(96)+sigs(920)+pad(0)+data(2985161)
D:   Actual size:      2986177
D: pool iob:    created size 48 limit -1 flags 0
D: pool ctx:    created size 112 limit -1 flags 0
D: pool bf:     created size 56 limit -1 flags 0
D: pool hkp:    created size 128 limit -1 flags 0
D: pool db:     created size 328 limit -1 flags 0
D: pool dbi:    created size 456 limit -1 flags 0
D: rpmdb: cpus 2 physmem 999Mb
D: opening  db environment /var/lib/rpm/Packages thread:lock:log:mpool:txn
rpmdb: BDB1546 unable to join the environment
error: db_init:db3.c:1085: dbenv->open(11): Resource temporarily unavailable
D: opening  db index       /var/lib/rpm/Packages thread:rdonly:auto_commit
mode=0x0
error: cannot open Packages(0) index: Resource temporarily unavailable(11)
        DB: Berkeley DB 5.3.15: (December 19, 2011)
error: cannot open Packages database in /var/lib/rpm
D:   PUB: 42691209 7AB62678 V4 DSA
D: ========== DSA pubkey id 42691209 7ab62678 (package)
D: /usr/src/rpm/RPMS/x86_64/rpm-libs-5.4.8-0.20120511.x86_64.rpm: Header V4
DSA signature: OK, key ID 7ab62678
D: pool te:     created size 368 limit -1 flags 0
D: pool ds:     created size 232 limit -1 flags 0
D: pool fi:     created size 560 limit -1 flags 0
D: pool al:     created size 64 limit -1 flags 0
D: opening  db environment /var/lib/rpm/Packages thread:lock:log:mpool:txn
rpmdb: BDB1546 unable to join the environment
error: db_init:db3.c:1085: dbenv->open(11): Resource temporarily unavailable
D: opening  db index       /var/lib/rpm/Packages thread:rdonly:auto_commit
mode=0x0
error: cannot open Packages database in /var/lib/rpm
D: pool ps:     created size 40 limit -1 flags 0
D: pool tsi:    created size 48 limit -1 flags 0
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, tree,
Ldepth, Rbreadth)
D:     0    0    0    1    0    0 +rpm-libs-5.4.8-0.20120511.x86_64
D: pool gi:     reused 0, alloc'd 1, free'd 1 items.
D: pool tsi:    reused 11, alloc'd 1, free'd 1 items.
D: pool ts:     reused 0, alloc'd 1, free'd 1 items.
D: pool te:     reused 0, alloc'd 1, free'd 1 items.
D: pool ps:     reused 0, alloc'd 1, free'd 1 items.
D: pool al:     reused 0, alloc'd 1, free'd 1 items.
D: pool ds:     reused 0, alloc'd 5, free'd 5 items.
D: pool fi:     reused 0, alloc'd 1, free'd 1 items.
D: pool db:     reused 1, alloc'd 1, free'd 1 items.
D: pool dbi:    reused 1, alloc'd 1, free'd 1 items.
D: pool h:      reused 0, alloc'd 2, free'd 2 items.
D: pool hkp:    reused 0, alloc'd 1, free'd 1 items.
D: pool bf:     reused 0, alloc'd 3, free'd 3 items.
D: pool ctx:    reused 3, alloc'd 2, free'd 2 items.
D: pool iob:    reused 1, alloc'd 1, free'd 1 items.
D: pool dig:    reused 0, alloc'd 1, free'd 1 items.
D: pool fd:     reused 3, alloc'd 1, free'd 1 items.
D: exit code: 1


On 11 May 2012 17:44, Tobias Gerschner <tobias.gersch...@gmail.com> wrote:

> I've recently built a LFS 64bit system and only put the additional
> requirements onto the system to compile RPM.
>
> I'm kinda stuck, getting the db initialized. I've got rpm installed and
> repackaged itself, i.e. I've recompiled rpm with itself using rpm into the
> first rpm pkg.
>
> However I can not install RPMs. I must be missing something to jump start
> the setup.
>
> -bash-4.2# rpm --rebuilddb
> rpmdb: BDB1546 unable to join the environment
> error: db_init:db3.c:1085: dbenv->open(11): Resource temporarily
> unavailable
> error: cannot open Packages(0) index: Resource temporarily unavailable(11)
>         DB: Berkeley DB 5.3.15: (December 19, 2011)
> error: cannot open Packages database in /var/lib/rpm
>
> I've been scouring over the changelog and examples / INSTALL etc. They all
> seem to be kinda outdated, ranging from citing an incorrect DB version to
> be used with rpm and so forth. So is there something that I should be aware
> of.
>
> Matthew could you use a hand with getting someone looking at the
> documentation side of things? I think I could manage that.
>
> --
> Tobias Gerschner
> Yoper Linux - www.yoper-linux.org
>
> Knowing is not enough; we must apply. Willing is not enough; we must do.
>



-- 
Tobias Gerschner
Yoper Linux - www.yoper-linux.org

Knowing is not enough; we must apply. Willing is not enough; we must do.

Reply via email to