* Press Ctrl-C to Stop * * net-analyzer/ostinato-1.1-r2:0::gentoo * /usr/bin/drone * * Package 'dev-util/drone-cli-1.7.0' NOT merged due to file collisions. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_plasma_systemd-20230811-000505 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.6 Python 3.11.4 Available Rust versions: [1] rust-1.71.1 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.7_p7 [openjdk-bin-17] 2) Eclipse Temurin JDK 8.372_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 system-vm php cli (if any): go version go1.21.0 linux/amd64 HEAD of ::gentoo commit 2a5619f196a0bd3974a7dd07057d97f3fd8c82f7 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Aug 13 20:51:37 2023 +0000 2023-08-13 20:51:36 UTC emerge -qpvO dev-util/drone-cli [ebuild N ] dev-util/drone-cli-1.7.0
Created attachment 867831 [details] emerge-info.txt
Created attachment 867832 [details] dev-util:drone-cli-1.7.0:20230813-224517.log.xz
Created attachment 867833 [details] emerge-history.txt
Created attachment 867834 [details] etc.clang.tar.xz
Created attachment 867835 [details] etc.portage.tar.xz
Created attachment 867836 [details] logs.tar.xz
@zerochaos: What do you think the best way to resolve this is? I don't feel comfortable renaming the "drone" binary in dev-util/drone-cli since it is a user runnable binary. What about your package --net-analyzer/ostinato -- is drone a utility users would run in that package? If it is, i guess we can have our packages block each other. Let me know if you have another idea. William
I renamed drone to ostinato-drone in ostinato-1.2.0 since it turned out to be safe and simple. I'll have it pushed to the tree in a little bit here, still testing deps to close the other open ostinato bugs.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab1e58d84d22776c5546da327e2e729aaa518eac commit ab1e58d84d22776c5546da327e2e729aaa518eac Author: Rick Farina <zerochaos@gentoo.org> AuthorDate: 2023-08-21 16:54:48 +0000 Commit: Rick Farina <zerochaos@gentoo.org> CommitDate: 2023-08-21 17:07:12 +0000 net-analyzer/ostinato: add 1.2.0 Additionally rename drone to ostinato-drone Bug: https://bugs.gentoo.org/show_bug.cgi?id=912264 Signed-off-by: Rick Farina <zerochaos@gentoo.org> net-analyzer/ostinato/Manifest | 1 + net-analyzer/ostinato/ostinato-1.2.0.ebuild | 44 +++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a817f2790d1e55440001aae85fe3544a0df87914 commit a817f2790d1e55440001aae85fe3544a0df87914 Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2023-08-21 18:10:04 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2023-08-21 18:10:23 +0000 dev-util/drone-cli: block older versions of ostinato Closes: https://bugs.gentoo.org/912264 Signed-off-by: William Hubbs <williamh@gentoo.org> dev-util/drone-cli/drone-cli-1.7.0.ebuild | 2 ++ 1 file changed, 2 insertions(+)
