rpm 5.x in Th

[Paweł Gołaszewski]

On Sat, 22 Sep 2012, Jan Rękorajski wrote:
> RPM 5 is now officially the package manager of PLD Th.
> Complete package set (rpm, poldek, etc.) is available in th-test,
> and builders have been upgraded to new rpm.
> 
> Some basic information is available on http://www.pld-linux.org/RPM5
> feel free to add whatever you think may be important.

Wieści z upgrade:

1. Nie wiem czy ten komunikat jest ważny czy nie:
I rpm-5.4.10-12.i686  rpm-base-5.4.10-12.i686  rpm-build-5.4.10-12.i686  rpm-build-macros-1.653-1.noarch  
I rpm-lib-5.4.10-12.i686  rpm-utils-5.4.10-12.i686
D poldek-0.30-1.rc6.2.i686  poldek-libs-0.30-1.rc6.2.i686
R poldek-0.30-1.rc5.14.i686  poldek-libs-0.30-1.rc5.14.i686  rpm-4.5-69.i686  rpm-base-4.5-69.i686  rpm-build-4.5-69.i686  
R rpm-build-macros-1.650-2.noarch  rpm-lib-4.5-69.i686  rpm-utils-4.5-69.i686
[...]
rpmdb_checkversion: BDB0126 mmap: Invalid argument


2. Próba upgrade pakietów z ready _przed_ nowym rpm daje coś takiego:
[...]
  45:QtWebKit               ########################################### [ 58%]
  46:QtXmlPatterns          ########################################### [ 60%]
rpm: rpmdb.c:3429: rpmdbAdd: Warunek zapewnienia `(dlen & 1) == 0' nie został spełniony.
błąd: /bin/rpm terminated by signal Przerwane
Freeing read locks for locker 0x414: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x416: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x417: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x418: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x419: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41a: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41b: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41c: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41d: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41e: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x41f: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x420: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x421: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x422: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x423: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
Freeing read locks for locker 0x424: 18854/3071866688
rpmdb: Thread/process 18854/3071866688 failed: locker has write locks
błąd: błąd db4(-30974) z dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
błąd: Uruchamianie db->verify...


Czy wszystkie nowobudowane pakiety nie powinny mieć wymagania nowego 
rpm-a?

3. Uruchomienie poldka po upgrade:
# poldek -n th -n th-ready
BDB0641 __db_meta_setup: /var/lib/rpm/Requirename: unexpected file type or format
Wczytywanie [pndir]th...
Wczytywanie [pndir]th...
Wczytywanie [pndir]th...
Wczytywanie [pndir]th...
Wczytywanie [pndir]th-ready...
Wczytywanie [pndir]th-ready...
Przeczytano 40408 pakietów
Usunięto 18993 zdublowane pakiety z listy dostępnych
Wczytywanie [rpmdbcache]/var/lib/rpm...
rpmdb: BDB0126 mmap: Zły argument
rpmdb: /var/lib/rpm/Packages: BDB0088 DB_SECONDARY_BAD: Secondary index inconsistent with primary
błąd: db3cget:db3.c:1406: dbcursor->get(-30972): BDB0088 DB_SECONDARY_BAD: Secondary index inconsistent with primary
poldek: rpmdb.c:2346: rpmmiNext: Warunek zapewnienia `0' nie został spełniony.
Przerwane
#

Dopiero zrobienie dbconvert załatwiło sprawę.

4. Czy w związku z tym dbconvert nie powinno być zawsze przy upgrade 
uruchamiane?

-- 
pozdr.  Paweł Gołaszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.