* Detected file collision(s): * * /usr/bin/rackup * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-ruby/rack-2.0.8:2.0::gentoo * /usr/bin/rackup * * Package 'dev-ruby/rack-2.1.1' NOT merged due to file collisions. If ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-libressl-20200121-072921 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.40.0 * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 3.15.0 [icedtea-8] *) IcedTea JDK 3.14.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] icedtea-bin-8 system-vm repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sun, 26 Jan 2020 08:26:14 +0000 emerge -qpvO dev-ruby/rack [ebuild NS ] dev-ruby/rack-2.1.1 [2.0.8] USE="-doc -test" RUBY_TARGETS="ruby24 ruby25 -ruby26 -ruby27%"
Created attachment 604554 [details] emerge-info.txt
Created attachment 604556 [details] dev-ruby:rack-2.1.1:20200126-092209.log
Created attachment 604558 [details] emerge-history.txt
Created attachment 604560 [details] etc.portage.tbz2
Created attachment 604562 [details] logs.tbz2
For what it's worth, same is true if RUBY_TARGETS="ruby24 ruby25 ruby26".
I suppose, since it's meant to be a new slot, the name has to be changed or there has to be another way to dynamically or manually change the specific version of dev-ruby/rack; e.g. eselect-rackup or /usr/bin/rackup-2.1
Alternatively, this should be a simple update, unless there are tools that rely on the specific, older version of dev-ruby/rack-2.0.8.
(In reply to Amel Hodzic from comment #8) > Alternatively, this should be a simple update, unless there are tools that > rely on the specific, older version of dev-ruby/rack-2.0.8. And there are: dev-ruby/actionpack-5.2.4.1 (ruby_targets_ruby24 ? >=dev-ruby/rack-2.0.8:2.0[ruby_targets_ruby24(-)]) (ruby_targets_ruby25 ? >=dev-ruby/rack-2.0.8:2.0[ruby_targets_ruby25(-)]) (ruby_targets_ruby26 ? >=dev-ruby/rack-2.0.8:2.0[ruby_targets_ruby26(-)]) dev-ruby/actionpack-6.0.2.1 (ruby_targets_ruby25 ? dev-ruby/rack:2.0[ruby_targets_ruby25(-)]) (ruby_targets_ruby26 ? dev-ruby/rack:2.0[ruby_targets_ruby26(-)]) dev-ruby/activesupport-5.2.4.1 (test ? dev-ruby/rack[ruby_targets_ruby24(-)]) which cause rack-2.0.8 to get installed even though I removed it to avoid the file collision when installing rack-2.1.1
Well, what you actually mean of course is if actionpack would not work with 2.1.1. And that I don't know :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=78ffdf3aadd4a15063fdde99ff25d4301831b332 commit 78ffdf3aadd4a15063fdde99ff25d4301831b332 Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2020-01-29 07:15:14 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2020-01-29 07:16:00 +0000 dev-ruby/rack: fix slot file collision Add 2.0 slot without binaries and make the 2.1 slot block on 2.0 versions with the binaries. Closes: https://bugs.gentoo.org/706410 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/rack/rack-2.0.8-r1.ebuild | 44 ++++++++++++++++++++++++++++++++++++++ dev-ruby/rack/rack-2.1.1.ebuild | 2 +- 2 files changed, 45 insertions(+), 1 deletion(-)
