* Detected file collision(s): * * /usr/bin/drone * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-analyzer/ostinato-0.9:0::gentoo * /usr/bin/drone * * Package 'dev-util/drone-cli-0.8.1' NOT merged due to file collisions. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib_libressl_20180113-212203 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] jython2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-util/drone-cli [ebuild N ] dev-util/drone-cli-0.8.0
Created attachment 515050 [details] emerge-info.txt
Created attachment 515052 [details] dev-util:drone-cli-0.8.1:20180115-221210.log
Created attachment 515054 [details] emerge-history.txt
Created attachment 515056 [details] etc.portage.tbz2
@zerochaos: Hey, is this still an issue? If so, we should probably file bugs with upstream for our packages and see if the drone binary can be renamed. Thanks, William
All versions of dev-util/drone in the tree now rename the executable to drone-server, so this hasn't been an issue for some time. Thanks, William
Sorry, I misread this bug, this is for drone-cli not drone.
It turns out that I asked about this issue a year ago on this bug and got no response, so I'm going to go ahead and close it assuming that /usr/bin/drone was renamed or moved in net-analyzer/ostinotto. If it wasn't, please re-open and we can work out a way to fix this. Thanks, William
