If emerge-webrsync gets a corrupt download somehow, then it decides to delete the entire portage tree since no files exist in what it is rsyncing to. Here's some sample output: # emerge-webrsync Fetching most recent snapshot Syncing local tree... bzip2: (stdin) is not a bzip2 file. tar: Child returned status 2 tar: Error exit delayed from previous errors chown: cannot access `portage': No such file or directory /usr/sbin/emerge-webrsync: line 37: cd: portage: No such file or directory building file list ... 1 file to consider ./ deleting xfce-extra/xfwm4-themes/xfwm4-themes-4.0.6.ebuild deleting xfce-extra/xfwm4-themes/xfwm4-themes-4.0.5.ebuild deleting xfce-extra/xfwm4-themes/xfwm4-themes-4.0.4.ebuild <snip the other 10000 files being deleted> Reproducible: Always Steps to Reproduce:
Similar to Bug #25499 ?
Dupe of 25499. Re: webrsync deleting your local tree, only possible when upstream (gentoo servers) sign/md5 an incomplete snapshot. No way to fix that clientside though. *** This bug has been marked as a duplicate of 25499 ***
