| View previous topic :: View next topic |
| Author |
Message |
ranumm
n00b
Joined: 16 Aug 2019
Posts: 25
|
 Posted: Mon Jan 06, 2025 4:20 pm Post subject: [dev-ruby/typeprof] Slot conflict, failed system update. |
 |
|
Hi there,
I have been unable to update my system for several days now due to “typeprof”.
| Code: | !!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-ruby/typeprof:0
(dev-ruby/typeprof-0.30.1:0/0::gentoo, installed) USE="-test" RUBY_TARGETS="ruby32 ruby33 ruby34" pulled in by
>=dev-ruby/typeprof-0.30.1[ruby_targets_ruby34(-)] required by (dev-lang/ruby-3.4.1:3.4/3.4::gentoo, installed) USE="gdbm ssl -berkdb -debug -doc -examples (-jemalloc) -jit -socks5 (-static-libs) -systemtap -tk -valgrind -xemacs"
^^ ^^^^^^
(dev-ruby/typeprof-0.21.11:0/0::gentoo, ebuild scheduled for merge) USE="-test" RUBY_TARGETS="ruby31 ruby32 ruby33" pulled in by
>=dev-ruby/typeprof-0.12.2[ruby_targets_ruby31(-)] required by (dev-lang/ruby-3.1.6-r2:3.1/3.1::gentoo, ebuild scheduled for merge) USE="gdbm ipv6 ssl -berkdb -debug -doc -examples (-jemalloc) -jit -socks5 (-static-libs) -systemtap -tk -valgrind -xemacs" |
I set in "make.conf":
| Code: | | RUBY_TARGETS="ruby32 ruby33 ruby34" |
I set in "/etc/portage/package.use/00Ruby":
| Code: | | */* RUBY_TARGETS: ruby32 ruby33 ruby34" |
I also used "--backtrack=30" with no success. Could someone help me? Thanks. |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3936
|
| Posted: Mon Jan 06, 2025 4:33 pm Post subject: |
|
|
Try to set
| Code: |
RUBY_TARGETS="-* ruby32 ruby33"
|
in package.use
_________________
Last edited by alamahant on Mon Jan 06, 2025 4:37 pm; edited 1 time in total |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31401
Location: here
|
| Posted: Mon Jan 06, 2025 4:35 pm Post subject: |
|
|
It looks like you still have ruby 3.1 installed which depends on <dev-ruby/typeprof-0.30.1 so portage can't upgrade to dev-ruby/typeprof-0.30.1.
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
ranumm
n00b
Joined: 16 Aug 2019
Posts: 25
|
| Posted: Mon Jan 06, 2025 6:05 pm Post subject: |
|
|
| alamahant wrote: | Try to set
| Code: |
RUBY_TARGETS="-* ruby32 ruby33"
|
in package.use |
Same issue.
| fedeliallalinea wrote: | | It looks like you still have ruby 3.1 installed which depends on <dev-ruby/typeprof-0.30.1 so portage can't upgrade to dev-ruby/typeprof-0.30.1. |
I have already removed ruby version 3.1 and tried to update my system by selecting all available {eselect} profiles (ruby32 - ruby33 - ruby34); same issue. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22954
|
| Posted: Mon Jan 06, 2025 6:11 pm Post subject: |
|
|
| How did you remove ruby:3.1? The output says that it is scheduled to be installed. |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31401
Location: here
|
| Posted: Mon Jan 06, 2025 7:01 pm Post subject: |
|
|
Please share the full emerge output.
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
ranumm
n00b
Joined: 16 Aug 2019
Posts: 25
|
| Posted: Mon Jan 06, 2025 9:18 pm Post subject: |
|
|
| Hu wrote: | | How did you remove ruby:3.1? The output says that it is scheduled to be installed. |
I remove from @world with:
| Code: | | emerge --deselect ruby |
then:
| Code: | emerge --depclean --ask --verbose =dev-lang/ruby-3.1.6-r2
Calculating dependencies... done!
dev-lang/ruby-3.1.6-r1 pulled in by:
dev-ruby/bundler-2.6.2 requires dev-lang/ruby:3.1
dev-ruby/date-3.4.1 requires dev-lang/ruby:3.1
dev-ruby/did_you_mean-1.6.3 requires dev-lang/ruby:3.1
dev-ruby/did_you_mean-2.0.0 requires dev-lang/ruby:3.1
dev-ruby/io-console-0.8.0 requires dev-lang/ruby:3.1
dev-ruby/irb-1.14.3 requires dev-lang/ruby:3.1
dev-ruby/json-2.9.1 requires dev-lang/ruby:3.1
dev-ruby/kpeg-1.3.3 requires dev-lang/ruby:3.1
dev-ruby/logger-1.6.4 requires dev-lang/ruby:3.1
dev-ruby/minitest-5.25.4 requires dev-lang/ruby:3.1
dev-ruby/net-imap-0.3.7 requires dev-lang/ruby:3.1
dev-ruby/power_assert-2.0.5 requires dev-lang/ruby:3.1
dev-ruby/psych-5.2.2 requires dev-lang/ruby:3.1
dev-ruby/racc-1.8.1 requires dev-lang/ruby:3.1
dev-ruby/rake-13.2.1 requires dev-lang/ruby:3.1
dev-ruby/rbs-3.8.1 requires dev-lang/ruby:3.1
dev-ruby/rdoc-6.10.0 requires dev-lang/ruby:3.1
dev-ruby/reline-0.6.0 requires dev-lang/ruby:3.1
dev-ruby/rexml-3.4.0 requires dev-lang/ruby:3.1
dev-ruby/rss-0.3.1 requires dev-lang/ruby:3.1
dev-ruby/rubygems-3.6.2 requires dev-lang/ruby:3.1
dev-ruby/stringio-3.1.2 requires dev-lang/ruby:3.1
dev-ruby/strscan-3.1.2 requires dev-lang/ruby:3.1
dev-ruby/test-unit-3.6.7 requires dev-lang/ruby:3.1
dev-ruby/typeprof-0.21.11 requires dev-lang/ruby:3.1
virtual/ruby-ssl-15 requires dev-lang/ruby:3.1[ssl], dev-lang/ruby:3.1
virtual/rubygems-21-r1 requires dev-lang/ruby:3.1
>>> No packages selected for removal by depclean |
Unfortunately, I had to force the uninstallation with:
| Code: | | emerge --unmerge -C =dev-lange/ruby-3.1.6-r2 |
|
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22954
|
| Posted: Mon Jan 06, 2025 9:38 pm Post subject: |
|
|
| You should not use emerge --unmerge, because that does not check dependency information. You removed ruby:3.1 without removing all the reasons you need it, so Portage is now trying to bring it back. You should have used emerge --ask --depclean to remove ruby:3.1 and all packages that hard-require it. I suspect from your output that these other packages conditionally require it based on RUBY_TARGETS. What is the output of emerge --pretend --verbose virtual/ruby-ssl virtual/rubygems all-installed-packages-in-dev-ruby? |
|
| Back to top |
|
|
ranumm
n00b
Joined: 16 Aug 2019
Posts: 25
|
| Posted: Tue Jan 07, 2025 7:42 pm Post subject: |
|
|
| Hu wrote: | | You should not use emerge --unmerge, because that does not check dependency information. You removed ruby:3.1 without removing all the reasons you need it, so Portage is now trying to bring it back. You should have used emerge --ask --depclean to remove ruby:3.1 and all packages that hard-require it. I suspect from your output that these other packages conditionally require it based on RUBY_TARGETS. What is the output of emerge --pretend --verbose virtual/ruby-ssl virtual/rubygems all-installed-packages-in-dev-ruby? |
I reinstalled ruby:3.1 but I don't understand why by checking the local USE flag (all required packages) 'ruby31' is enabled. Why? |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22954
|
| Posted: Tue Jan 07, 2025 8:32 pm Post subject: |
|
|
| Assuming your Gentoo Portage tree is relatively current, the answer is that ruby-3.1 is not enabled by the upstream tree. As I read the history, this was changed in profiles/base/make.defaults: drop ruby31 from RUBY_TARGETS in October 2024. Therefore, either your tree is notably out of date or you have a local modification in /etc/portage that is enabling it. What is the output of grep -inr RUBY_TARGETS /etc/portage/make.conf /etc/portage/package.use? |
|
| Back to top |
|
|
ranumm
n00b
Joined: 16 Aug 2019
Posts: 25
|
| Posted: Wed Jan 08, 2025 7:10 pm Post subject: |
|
|
| Hu wrote: | | Assuming your Gentoo Portage tree is relatively current, the answer is that ruby-3.1 is not enabled by the upstream tree. As I read the history, this was changed in profiles/base/make.defaults: drop ruby31 from RUBY_TARGETS in October 2024. Therefore, either your tree is notably out of date or you have a local modification in /etc/portage that is enabling it. What is the output of grep -inr RUBY_TARGETS /etc/portage/make.conf /etc/portage/package.use? |
grep -inr RUBY_TARGETS /etc/portage/make.conf
| Quote: | | 16:RUBY_TARGETS="ruby32 ruby33 ruby34" |
grep -inr RUBY_TARGETS /etc/portage/package.use
| Code: | | https://paste.gentoo.zip/GBFuVNcx |
|
|
| Back to top |
|
|
|
Portage & Programming
