Description of problem: When upgrading Mageia8 to cauldron with Mageia9-alpha1 isos, i get a fatal error: "unable to open rpmdb (9)" attaching log screen. Version-Release number of selected component (if applicable): Mageia9-alpha1 isos How reproducible: launch installation, choose upgrade to Mageia9.
Created attachment 13447 [details] CTRL+F1 log
Created attachment 13448 [details] CTRL+F3 log
From bug 29364 which I've just reopened due to this bug report. run "rpm --rebuilddb" as root.
CC: (none) => davidwhodgins
Thank you for the report. Assigning to the MageiaTools group re the Installer.
Assignee: bugsquad => mageiatoolsSummary: Installer does "unable to open rpmdb (9)" => Installer does "unable to open rpmdb (9)" doing Mageia8 to 9 upgrade.
CC: (none) => mageia
This occurs because when urpm::select::migrate_forward_rpmdb_db_if_needed() calls _rpm_version(), the underlying call to 'rpm --version' fails with the error: rpm: symbol lookup error: /mnt/lib64/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE I guess this is because the rpm command comes from the installed system (/mnt/usr/bin/rpm) but it is using the glibc from the installer environment. Indeed, if in the installed debug shell I do chroot /mnt rpm --version then it works without error. Changing LD_LIBRARY_PATH to exclude the installer environment merely results in rpm failing with a segementation fault.
CC: (none) => mageia, thierry.vignaudPriority: Normal => release_blocker
I tried to work round this by adding the rpm command to the installer stage 2 environment. That got me a bit further - it now fails with: * chrooted db version used by librpm is at least as good as non-rooted one * Migrating chrooted db * urpmi error: rpm db conversion failed. You will not be able to run rpm >= 4.17
Fixed in drakx-installer-stage2 18.51. To be verified with next ISO build.
Source RPM: (none) => drakx-installer-stage2
What about people using the cli to upgrade by switching repos from m8 to m9?
(In reply to Dave Hodgins from comment #8) > What about people using the cli to upgrade by switching repos from m8 to m9? urpmi is supposed to handle that. If it doesn't work, open a new bug report.
(In reply to Martin Whitaker from comment #7) > Fixed in drakx-installer-stage2 18.51. > To be verified with next ISO build. Thank you yet again for a fix. Looks good to close pending feedback. @Daniel Please can *you* try this, & report back.
CC: (none) => lewyssmith
CC: (none) => bequimao.de
(In reply to Martin Whitaker from comment #7) > Fixed in drakx-installer-stage2 18.51. > @Daniel > Please can *you* try this, & report back If Daniel does not reply soon, this will be closed fixed.
Sorry, do not had time to test. will be tested next days.
Hi, That's all good. Upgrade made this day, no problems. Thanks
Resolution: (none) => FIXEDStatus: NEW => RESOLVED