Description of problem: missing files during installation of exim to external root (maybe into normal root) Version-Release number of selected component (if applicable): exim-4.63-3.el5.x86_64 rhel54-Server-20090708.nightly How reproducible: always Steps to Reproduce: 1. yum --installroot=/tmp/tmp.sfPCdk6328 install exim -y --disablerepo=\*rhts-noarch\* Actual results: .... Installing : rsyslog [66/71] Installing : initscripts [67/71] Installing : exim [68/71] chown: cannot access `/etc/pki/tls/private/exim.pem': No such file or directory chown: cannot access `/etc/pki/tls/certs/exim.pem': No such file or directory chmod: cannot access `/etc/pki/tls/private/exim.pem': No such file or directory chmod: cannot access `/etc/pki/tls/certs/exim.pem': No such file or directory error: %post(exim-4.63-3.el5.x86_64) scriptlet failed, exit status 1 Installing : mcstrans [69/71] Installing : python [70/71] Installing : cracklib [71/71] .... ----------------- no files in /tmp/tpm.sfPCdk6328/etc/pki/tls/certs/exim.pem /tmp/tpm.sfPCdk6328/etc/pki/tls/private/exim.pem Expected results: clear installation of exim Additional info: # rpm -ivh /mnt/redhat/brewroot/packages/exim/4.63/3.el5/x86_64/exim-4.63-3.el5.x86_64.rpm --root=/tmp/tmp.sfPCdk6328 --replacepkgs warning: /mnt/redhat/brewroot/packages/exim/4.63/3.el5/x86_64/exim-4.63-3.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 897da07a Preparing... ########################################### [100%] 1:exim ########################################### [100%] chown: cannot access `/etc/pki/tls/private/exim.pem': No such file or directory chown: cannot access `/etc/pki/tls/certs/exim.pem': No such file or directory chmod: cannot access `/etc/pki/tls/private/exim.pem': No such file or directory chmod: cannot access `/etc/pki/tls/certs/exim.pem': No such file or directory error: %post(exim-4.63-3.el5.x86_64) scriptlet failed, exit status 1
*** This bug has been marked as a duplicate of bug 515553 ***
Re-opening, this isn't really a dupe of 515553.
Bug #517013 is corresponding Fedora bug.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1627.html