FC4 anaconda upgrade into rawhide-20060307 has a scriptlet error when it runs %post of scim-libs. The PreReq listed below should be DTRT but somehow fails in the anaconda upgrade case. A fresh install of rawhide-20060307 installs in the correct order. scim.spec contains: =================== %package libs Summary: Smart Common Input Method libraries Group: System Environment/Libraries # for update-gtk-immodules PreReq: gtk2 > 2.8 Obsoletes: iiimf-libs <= 1:12.2 %post libs /sbin/ldconfig %{_bindir}/update-gtk-immodules %{_target_platfo upgrade.log 37%: ================ Upgrading scim-libs-1.4.4-9.i386. Cannot load module /usr/lib/gtk-2.0/immodules/im-scim.so: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory /usr/lib/gtk-2.0/immodules/im-scim.so does not export GTK+ IM module API: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory error: %post(scim-libs-1.4.4-9.i386) scriptlet failed, exit status 1 upgrade.log 48%: ================ Upgrading pango-1.11.99-1.i386. upgrade.log 49%: ================ Upgrading gtk2-2.8.13-3.i386.
Created attachment 125777 [details] upgrade.log Example upgrade.log
Replicated both inside and outside installer.
Created attachment 125828 [details] Ordering from a fc4 system Steps taken for attached order details: import yum y = yum.YumBase() y.doConfigSetup() y.doTsSetup() y.doRpmDBSetup() y.repos.disableRepo('*') y.repos.enableRepo('local*') y.doRepoSetup() y.doGroupSetup() y.doSackSetup() y.update() y.initActionTs() y.populateTs() y.ts.check() import rpm rpm.setVerbosity(rpm.RPMLOG_DEBUG) y.ts.ts.order()
Try adding whiteout to remove the loops.
This is necessary even though scim-libs has a PreReq on gtk2 > 2.8, and FC4 had gtk2-2.6?
I said "Try adding whiteout to remove the loops." Did you?
*** Bug 187261 has been marked as a duplicate of this bug. ***
Jeff, what does "whiteout" mean? Who was that question addressed?
My reply was to warren. The term "whiteout" comes from typewriters, messy goo to fix typos on paper. In this context, whiteout means breaking dependency loops at precisely one known point between 2 package nodes, as rpm ignores all Requires: in a loop, leading to a difficult to QA indeterminism in package ordering. Warren should know what "whiteout" is, if not, well, he has no business asking stupid questions.
Is it a yum problem in prioritizing the package installation/upgrade order? If so, would it be appropriate to change the involved component to "yum"?
AFAIR this doesn't happen for final FC5 so I think we can close this.