Bug 22760

Summary: rpm crashes when finishing package installation
Product: Mageia Reporter: Christian Müller <chmos>
Component: RPM PackagesAssignee: RPM stack maintainers <rpmstack>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11, tmb
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: rpm-4.13.0.2-3.2.mga6 CVE:
Status comment:

Description Christian Müller 2018-03-13 20:46:10 CET
Description of problem:

When installing an rpm package using rpm, urpmi or rpmdrake, rpm crashes. Console output (in German):

rpm: backend/dbiset.c:62: dbiIndexSetUniq: Zusicherung »set->count > 0« nicht erfüllt.
Abgebrochen (Speicherabzug geschrieben)

Therefore /var/cache/urpmi/rpms is left unflushed when updates are installed.
Reproduced that on three different machines.

Version-Release number of selected component (if applicable):

RPM-Version 4.13.0.2
Marja Van Waes 2018-03-14 07:37:24 CET

Assignee: bugsquad => rpmstack
CC: (none) => marja11

Comment 1 Thomas Backlund 2018-03-14 08:39:49 CET
Please show full version-relelease of rpm from command:

rpm -qa rpm

There was a broken rpm in testing a while back that had similar problems

CC: (none) => tmb

Comment 2 Thomas Backlund 2018-03-14 08:40:53 CET
Actually looking at SRPM line, you have listed rpm-4.13.0.2-3.2.mga6 wich is the broken one...
Comment 3 Thomas Backlund 2018-03-14 13:53:08 CET
So to downgrade, check what packages for the broken rpm you have installed with

rpm -qa |grep 4.13.0.2-3.2

and you will probably get a list like:

lib64rpm7-4.13.0.2-3.2.mga6
python2-rpm-4.13.0.2-3.2.mga6
python3-rpm-4.13.0.2-3.2.mga6
rpm-4.13.0.2-3.2.mga6



Then to downgrade you do:

urpmi --downgrade rpm 


If you have other rpm packages installed like:
lib64rpmbuild7-4.13.0.2-3.2.mga6
lib64rpmsign7-4.13.0.2-3.2.mga6


then downgrade them with

urpmi --downgrade lib64rpmbuild7 lib64rpmsign7
Comment 4 Christian Müller 2018-03-19 18:43:48 CET
(In reply to Thomas Backlund from comment #3)
> So to downgrade, check what packages for the broken rpm you have installed
> with
> 
> rpm -qa |grep 4.13.0.2-3.2

I had indeed testing repos active, and rpm-4.13.0.2-3.2 installed. Downgrade to 4.13.0.2-3.1 solved the problem, thank you :)
Comment 5 Thomas Backlund 2018-03-19 18:46:23 CET
Great you got it fixed.

Closing the bug

Resolution: (none) => FIXED
Status: NEW => RESOLVED