diffball colliosion.

These are the packages that would be merged, in order:

Calculating dependencies... done!
[binary  N    *] dev-util/diffball-1.0.1-1::gentoo  USE="-debug" 0 KiB

Total: 1 package (1 new, 1 binary), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] yes
>>> Emerging binary (1 of 1) dev-util/diffball-1.0.1::gentoo
>>> Installing (1 of 1) dev-util/diffball-1.0.1::gentoo
>>> Failed to install dev-util/diffball-1.0.1, Log file:
>>>  '/var/log/portage/dev-util:diffball-1.0.1:20180703-233009.log'
>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 0.61, 0.29, 0.14
>>> Extracting info
 * Package:    dev-util/diffball-1.0.1
 * Repository: gentoo
 * USE:        kernel_linux arm64 elibc_glibc userland_GNU
 * FEATURES:   compressdebug distcc preserve-libs sandbox splitdebug userpriv usersandbox
>>> cfg-update-1.8.2-r1: Skipping checksum index updating...
>>> Extracting dev-util/diffball-1.0.1
 * checking 47 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *      /usr/lib64/libcfile.la
 *      /usr/lib64/libcfile.a
 *      /usr/lib64/libcfile.so
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * dev-libs/libcfile-20180102:0::pentoo
 *      /usr/lib64/libcfile.a
 *      /usr/lib64/libcfile.la
 *      /usr/lib64/libcfile.so
 *
 * Package 'dev-util/diffball-1.0.1' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 *
 * The following package has failed to build, install, or execute postinst:
 *
 *  (dev-util/diffball-1.0.1-1:0/0::gentoo, binary scheduled for merge), Log file:
 *   '/var/log/portage/dev-util:diffball-1.0.1:20180703-233009.log'
 *

 * GNU info directory index is up-to-date.

!!! existing preserved libs:
>>> package: dev-libs/mpfr-4.0.1
 *  - /usr/lib64/libmpfr.so.4
 *  - /usr/lib64/libmpfr.so.4.1.6
 *      used by /usr/bin/luatex (app-text/texlive-core-2017-r4)
 *      used by /usr/bin/mpost-texlive-core-2017 (app-text/texlive-core-2017-r4)
 *      used by /usr/bin/pmpost (app-text/texlive-core-2017-r4)
 *      used by 32 other files
>>> package: net-dns/libidn-1.35
 *  - /usr/lib64/libidn.so.11
 *  - /usr/lib64/libidn.so.11.6.16
 *      used by /usr/lib64/libgs.so.9.21 (app-text/ghostscript-gpl-9.21)
 *      used by /usr/lib64/perl5/vendor_perl/5.26.2/aarch64-linux/auto/Net/LibIDN/LibIDN.so (dev-perl/Net-LibIDN-0.120.0-r1)
Use emerge @preserved-rebuild to rebuild packages using these libraries

 * IMPORTANT: 34 config files in '/etc' need updating.
 * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.

 * IMPORTANT: 1 news items need reading for repository 'perl-experimental'.
 * IMPORTANT: 15 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

scw-0321f9 / # uanme -?
bash: uanme: command not found
scw-0321f9 / # uname ?
uname: extra operand ‘?’
Try 'uname --help' for more information.
scw-0321f9 / # uname --help
Usage: uname [OPTION]...
Print certain system information.  With no OPTION, same as -s.

  -a, --all                print all information, in the following order,
                             except omit -p and -i if unknown:
  -s, --kernel-name        print the kernel name
  -n, --nodename           print the network node hostname
  -r, --kernel-release     print the kernel release
  -v, --kernel-version     print the kernel version
  -m, --machine            print the machine hardware name
  -p, --processor          print the processor type (non-portable)
  -i, --hardware-platform  print the hardware platform (non-portable)
  -o, --operating-system   print the operating system
      --help     display this help and exit
      --version  output version information and exit

GNU coreutils online help: <https://www.gnu.org/software/coreutils/>
Full documentation at: <https://www.gnu.org/software/coreutils/uname>
or available locally via: info '(coreutils) uname invocation'
scw-0321f9 / # uname -srvmpoia
Linux scw-0321f9 4.9.93-mainline-rev1 #1 SMP Tue Apr 10 09:54:46 UTC 2018 aarch64 GNU/Linux


scw-0321f9 / # cat /var/log/portage/dev-util:diffball-1.0.1:20180703-233009.log
>>> Extracting info
 * Package:    dev-util/diffball-1.0.1
 * Repository: gentoo
 * USE:        kernel_linux arm64 elibc_glibc userland_GNU
 * FEATURES:   compressdebug distcc preserve-libs sandbox splitdebug userpriv usersandbox
>>> cfg-update-1.8.2-r1: Skipping checksum index updating...
>>> Extracting dev-util/diffball-1.0.1
 * checking 47 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *      /usr/lib64/libcfile.la
 *      /usr/lib64/libcfile.a
 *      /usr/lib64/libcfile.so
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * dev-libs/libcfile-20180102:0::pentoo
 *      /usr/lib64/libcfile.a
 *      /usr/lib64/libcfile.la
 *      /usr/lib64/libcfile.so
 *
 * Package 'dev-util/diffball-1.0.1' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.