| Summary: | rpm and urpmi segfaults during upgrade from mageia 2 to 3 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Paweł Susicki <spam> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | 3 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpm-4.11.0.1-1.mga3.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Paweł Susicki
2013-12-06 13:12:36 CET
You must have not upgraded a package rpm is relying on. You should try perform an upgrade with classic installer (ISO image) CC:
(none) =>
thierry.vignaud I tried classic installer booting ISO image. Upgrade segfaulted exactly in the same place. I have copy of rpmdb with Mageia2, so the bug may be investigated. (In reply to Thierry Vignaud from comment #1) > You must have not upgraded a package rpm is relying on. > You should try perform an upgrade with classic installer (ISO image) I tried classic installer booting ISO image. Upgrade segfaulted exactly in the same place. I have copy of rpmdb with Mageia2, so the bug may be investigated. Please attach the /root/drakx/report.bug.xz after this classic installer upgrade Keywords:
(none) =>
NEEDINFO (In reply to Thierry Vignaud from comment #4) > Please attach the /root/drakx/report.bug.xz after this classic installer > upgrade This upgrade segfaults at the beginning, trying to upgrade/remove package rpmdevtools. So there is no such thing as report after classic upgrade. I've done it manually patching librpm.so.3 and using urpmi --auto-select --auto --replacefiles. After this manual upgrade everything seems to be ok. I've a copy of whole root filesystem before upgrade. Maybe database in /var/lib/rpm would help ? urpmi/rpm expects at some point during check to read tag of string type, but it is of another. No. Mga2 is EOL and for most users the upgrade went smoothly. There's no way to know what had happened in your case Status:
NEW =>
RESOLVED (In reply to Thierry Vignaud from comment #6) > No. > Mga2 is EOL and for most users the upgrade went smoothly. > There's no way to know what had happened in your case OK, I'll recreate this bug on the next upgrade. |