Created attachment 896967 [details] x11-wm:xpra-6.0.1:20240704-112729.log =x11-wm/xpra-6.0.1 fails to install due to a file collision with www-apps/xpra-html5 (which it depends on via USE=html), namely the file /usr/share/xpra/www/index.html . This happens whether xpra-html5 is version 10.1 or 13.
Created attachment 896968 [details] emerge-info.txt
I think this report may be bogus. The log shows that src_test failed due to failing tests, so it therefore didn't execute the last line that removes this file. You then somehow proceeded with the install phases anyway. Overriding regular behaviour with the ebuild command?
FEATURES=test-fail-continue was applied using /etc/portage/package.env, to let Portage make progress on the Python 3.12 transition despite the test failure (which I had planned to report if I could reproduce it once the rest of the system was up-to-date and consistent). If the file is only installed to the staging area in src_test(), perhaps either the cleanup could be moved to src_install(), or the "die" could be postponed to after the cleanup line?
Ah, apologies! I didn't know about that feature. I'll fix it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46a9dd4de7bca2152a3403726e50375563e37003 commit 46a9dd4de7bca2152a3403726e50375563e37003 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2024-07-06 14:08:41 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2024-07-06 14:08:41 +0000 x11-wm/xpra: Fix file collision caused by failed tests Closes: https://bugs.gentoo.org/935476 Signed-off-by: James Le Cuirot <chewi@gentoo.org> x11-wm/xpra/xpra-6.0.1-r1.ebuild | 8 ++++++-- x11-wm/xpra/xpra-6.9999.ebuild | 8 ++++++-- x11-wm/xpra/xpra-9999.ebuild | 8 ++++++-- 3 files changed, 18 insertions(+), 6 deletions(-)
