Today I was perusing my system and found a couple of odd files in my root directory: 20K -rw-r--r-- 1 root root 20K Mar 23 06:38 control.tar.gz 164K -rw-r--r-- 1 root root 162K Mar 23 06:38 data.tar.gz 4.0K -rw-r--r-- 1 root root 4 Mar 23 06:38 debian-binary The data.tar.gz file contains ssl certificate files. I was starting to think my machine had been compromized. I then looked at my build box/binserver. It had the same files in the root dir. When I googled I discovered these were debian files. Then I checked my build box's distdir to see if there were any .debs? ca-certificates_20120623_all.deb ca-certificates_20130119_all.deb ca-certificates_20121114_all.deb Looking at my emerge logs I do see that I installed app-misc/ca-certificates-20130119 on 23 March at around 06:38. Further inquiry shows that those files are indeed in the package's manifest: obj /data.tar.gz ac9c767aae0468f93f5bf3ea78784fc0 1364035131 obj /debian-binary 3cf918272ffa5de195752d73f3da3e5e 1364035131 obj /control.tar.gz d46af0f6d6092867f458c6b3a426ebf5 1364035131
*** This bug has been marked as a duplicate of bug 458658 ***
Solution is to simply re-sync your portage-tree and then re-emerge the package again.
