Unable to update to rpm-libs 4.8.1-19 and urpo 20150101-9

[Lewis Rosenthal]

We seem to have a problem making the upgrade:

Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating       : urpo-20150101-9.oc00.i386                                1/4

Error unpacking rpm package urpo-20150101-9.oc00.i386
error: unpacking of archive failed on file /@unixroot/usr/lib/urpo.dll: cpio: ch
own
  Updating       : rpm-libs-4.8.1-19.oc00.i386                              2/4

Error unpacking rpm package rpm-libs-4.8.1-19.oc00.i386
error: unpacking of archive failed on file /@unixroot/usr/lib/rpm.dll: cpio: cho
wn
urpo-20141223-7.oc00.i386 was supposed to be removed but is not!
rpm-libs-4.8.1-18.oc00.i386 was supposed to be removed but is not!

yum.log says:

Jan 01 22:19:15 urpo-20150101-9.oc00.i386: 100
Jan 01 22:19:24 Updated: rpm-4.8.1-19.oc00.i386
Jan 01 22:19:24 rpm-libs-4.8.1-19.oc00.i386: 100
Jan 01 22:19:33 Updated: rpm-build-4.8.1-19.oc00.i386
Jan 01 22:19:34 Updated: urpo-devel-20150101-9.oc00.i386
Jan 01 22:19:34 urpo-devel: ts_done name in te is rpm-libs should be urpo-devel

(not much help in the log)

There does not appear to be anything wrong with the rpms themselves. I see this on multiple systems, too.

As a result of multiple attempts, I am left with:

12-23-14  14:10           3,072    124   ___A_  urpo.dll
 1-01-15  22:19           3,207    124   ___A_  urpo.dll;54a60e33
 1-01-15  22:20           3,207    124   ___A_  urpo.dll;54a60e70
 1-01-15  22:21           3,207    124   ___A_  urpo.dll;54a60ed4
 1-01-15  22:40           3,207    124   ___A_  urpo.dll;54a61346

though I do seem to have ended up with the correct rpm.dll, somehow:

 1-01-15  22:42         268,875    124   ___A_  rpm.dll
 1-01-15  22:19         268,875    124   ___A_  rpm.dll;54a60e33
 1-01-15  22:20         268,875    124   ___A_  rpm.dll;54a60e70
 1-01-15  22:21         268,875    124   ___A_  rpm.dll;54a60ed4

[Lewis Rosenthal]

Manually replacing the old urpo.dll with the new one resolved the issue. So, we just need to figure out how to get that to happen during a yum or rpm transaction.

[Yuri Dario]

This happens because urpo-20141223 broke unlocking of dlls and thus it has been retired a few days after the release.

yum downgrade urpo

should be able to restore the old one, but depends on lock status of the dll.

No other ways to fix it automatically.

[Lewis Rosenthal]

Ah...

Understood, Yuri; thanks. Makes perfect sense, now. I should have thought of downgrading first.