package installation does not stop at 100%

Bug #726161 reported by Paweł Zuzelski on 2011-02-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RPM
Undecided
Unassigned
PLD Linux
Undecided
Marcin Banasiak

Bug Description

I sturted full upgrade on one of my th/x86_64 machines (inside a vserver). I started poldek and executed "upgrade *". It upgraded some packages sucessfully. But it failed to upgrade git-core. It did not stop installing it when the progress bar reached 100%. It continued it, drawing a few screens of '#' characters and increasing a counter. It reached ~ 6000% or something like that. Finally I interupted it with Ctrl+C. I tried to install it again, and it happened again. I tried to start a new instance of poldek and perform "upgrade *" there - same error:

Executing sudo /bin/rpm --upgrade -vh --root /...
warning: /home/users/z/tmp/poldek-cache-z/ftp_ftp.th.pld-linux.org.dists.th.PLD.x86.64.RPMS/git-core-1.7.4-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID e4f1bc2d
Preparing... ########################################### [100%]
Repackaging...
   1:git-core ###############################################################################################################################################################################################################################################################################################################################################################^CUpgrading... ##############(161%)
poldek:/all-avail>

I had seen it a few times before, but now, for the first time, it is reproducible.

I have attached a tarball containing a /var/lib/rpm from that machine.

Paweł Zuzelski (pawelz) wrote :
Paweł Zuzelski (pawelz) wrote :

<+arekm> pawelz: i teraz męcz zapewne megabajta

Changed in pld-linux:
assignee: nobody → Marcin Banasiak (megabajt)
Elan Ruusamäe (glen666) wrote :

it's not Poldek. it is RPM.

See if git-core has got some %ghost file packaged, which your size is 160 times biger than original (original is likely 0 bytes)

so to see it, it is needed to know what was your git-core package BEFORE upgrade.

tags: added: rpm
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers