------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma_libressl-abi32+64_20180520-110759 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-vim/perl-support [ebuild N ] app-vim/perl-support-5.4 !!! The following installed packages are masked: - app-i18n/ibus-tutcode-1.0.2-r1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Akinori Hattori <hattya@gentoo.org> (27 May 2018) # Dead upstream, for old versions of iBus # Masked for removal in 30 days. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
Created attachment 533676 [details] emerge-info.txt
Created attachment 533678 [details] app-vim:perl-support-5.4:20180528-003247.log
Created attachment 533680 [details] emerge-history.txt
Created attachment 533682 [details] etc.portage.tbz2
Created attachment 533684 [details] logs.tbz2
app-vim/bash-support-4.2.1 also collide with perl-support and/or c-support. * package app-vim/perl-support-5.4 NOT merged * * Detected file collision(s): * * /usr/share/vim/vimfiles/autoload/mmtemplates/core.vim * /usr/share/vim/vimfiles/doc/templatesupport.txt * /usr/share/vim/vimfiles/syntax/template.vim * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-vim/bash-support-4.2.1:0::gentoo * /usr/share/vim/vimfiles/autoload/mmtemplates/core.vim * /usr/share/vim/vimfiles/doc/templatesupport.txt * /usr/share/vim/vimfiles/syntax/template.vim * * Package 'app-vim/perl-support-5.4' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message.