Hi,

Today's yum update on Fedora 14 resulted in about 10 seconds long 100% CPU load 
on one of the cores 
and an error in scriptlet:

Running Transaction
   Updating       : farsight2-0.0.22-1.fc14.x86_64 
                                                    1/26
   Updating       : libcap-2.22-1.fc14.x86_64 
                                                    2/26
   Updating       : 1:cups-libs-1.4.8-2.fc14.x86_64
   Updating       : 1:cups-1.4.8-2.fc14.x86_64
   Updating       : farsight2-python-0.0.22-1.fc14.x86_64
   Updating       : BackupPC-3.2.1-4.fc14.x86_64
   Updating       : libvpx-0.9.7.1-1.fc14.x86_64
   Updating       : system-config-firewall-base-1.2.27-2.fc14.noarch
   Updating       : system-config-firewall-tui-1.2.27-2.fc14.noarch
   Updating       : system-config-firewall-1.2.27-2.fc14.noarch
   Updating       : libcap-devel-2.22-1.fc14.x86_64
   Updating       : rubygems-1.3.7-3.fc14.noarch
   Updating       : 1:cups-libs-1.4.8-2.fc14.i686
   Cleanup        : 1:cups-1.4.6-1.fc14.x86_64
   Cleanup        : farsight2-python-0.0.21-2.fc14.x86_64
   Cleanup        : farsight2-0.0.21-2.fc14.x86_64
   Cleanup        : 1:cups-libs-1.4.6-1.fc14
   Cleanup        : BackupPC-3.2.1-1.fc14.x86_64
Non-fatal POSTUN scriptlet failure in rpm package BackupPC
   Cleanup        : libvpx-0.9.6-1.fc14.x86_64
/var/tmp/rpm-tmp.99zFPZ: line 15: syntax error near unexpected token `fi'
/var/tmp/rpm-tmp.99zFPZ: line 15: `fi'
warning: %postun(BackupPC-3.2.1-1.fc14.x86_64) scriptlet failed, exit status 2
   Cleanup        : system-config-firewall-1.2.27-1.fc14.noarch
   Cleanup        : system-config-firewall-tui-1.2.27-1.fc14.noarch
   Cleanup        : libcap-devel-2.17-1.fc13.x86_64
   Cleanup        : libcap-2.17-1.fc13.x86_64
   Cleanup        : system-config-firewall-base-1.2.27-1.fc14.noarch
   Cleanup        : rubygems-1.3.7-2.fc14.noarch
   Cleanup        : 1:cups-libs-1.4.6-1.fc14

Cheers,
Dariusz
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to