I'm currently assuming this has something to do with the hardened profile since this package will not install correctly on a SELinux VM, but works just fine on my non-SELinux host. The VM is currently not enforcing. >>> Installing (1 of 1) app-misc/ca-certificates-20140927.3.17.2::gentoo * Removing /usr/share/doc >>> Setting SELinux security labels !!! Failed to move /var/tmp/portage/app-misc/ca-certificates-20140927.3.17.2/image/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt to /usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt !!! [Errno 2] No such file or directory: '/var/tmp/portage/app-misc/ca-certificates-20140927.3.17.2/image/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt' -> '/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt' Not sure what is going on. The file exists. ls -l /var/tmp/portage/app-misc/ca-certificates-20140927.3.17.2/image/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt -rw-r--r--. 1 root root 2004 Jan 22 18:48 /var/tmp/portage/app-misc/ca-certificates-20140927.3.17.2/image/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt Reproducible: Always
I have just switch to “hardened/linux/amd64/selinux” and updated this package. What about “/usr/share/ca-certificates/mozilla/Certinomis_-_Autorité_Racine.crt”? Does it exist/be writable? I do know how it ca-cert works. But it uses symbolic links on “/etc/ssl/certs/”. Is it broken?
(In reply to Sébastien P. from comment #1) > I have just switch to “hardened/linux/amd64/selinux” and updated this > package. And I did not meet this issue…
you must attach `emerge --info` and full build logs with every report if it's still failing for you, please post try building with --debug
Well, I would post info, but this is from a virtual machine, and it seems my libvirt is broken now. I'll see if this is still an issue once I get libvirt sorted out.
Ok, finally got libvirt working again. (a stale lock file for ebtables was gumming up the works) Install is still failing. I'm attaching the build log.
Created attachment 400120 [details] Build Log
Created attachment 400122 [details] Build Log (with debugging turned on)
Figured it out. I noticed that the CA cert had a non-english character in it so I checked to see what my locale was set to. It was en_US. Changed it to en_US.utf8 and it installed without any problems.
