The latest ebuild has: rm -v "${ED}"usr/share/parti/{parti.,}README \ "${ED}"usr/share/xpra/{webm/LICENSE,xpra.README} \ "${ED}"usr/share/wimpiggy/wimpiggy.README || die However, webm/LICENSE doesn't exist in my server (I assume it's because I use -webp) and {parti.,}README don't exist in my client (-webp -server). This results in: Server: removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/parti/parti.README’ removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/parti/README’ rm: cannot remove ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/xpra/webm/LICENSE’: No such file or directory removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/xpra/xpra.README’ removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/wimpiggy/wimpiggy.README’ Client: rm: cannot remove ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/parti/parti.README’: No such file or directory rm: cannot remove ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/parti/README’: No such file or directory rm: cannot remove ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/xpra/webm/LICENSE’: No such file or directory removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/xpra/xpra.README’ removed ‘/var/tmp/portage/x11-wm/xpra-0.8.0/image/usr/share/wimpiggy/wimpiggy.README’ and the emerge fails. Either remove the "|| die", add a -f or make sure those files exist. Reproducible: Always Steps to Reproduce: 1. emerge xpra with -server or -webp 2. see it fail 3.
xpra has been updated to 0.8.1... and this bug is still there :/
(In reply to comment #1) > xpra has been updated to 0.8.1... and this bug is still there :/ Sry, I didn't get your report, because I had not checked the bug queue and the bug was not assigned to me (bug wranglers must be slacking ;-). Fixed in cvs, resync in 1-2 hours. +*xpra-0.8.1-r1 (05 Feb 2013) +*xpra-0.8.0-r1 (05 Feb 2013) + + 05 Feb 2013; Michael Weber <xmw@gentoo.org> -xpra-0.8.0.ebuild, + +xpra-0.8.0-r1.ebuild, -xpra-0.8.1.ebuild, +xpra-0.8.1-r1.ebuild: + Fix README removals on reduced USE flag situations (thanks Francisco Vazquez + for reporting bug 455098) +