Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: ruby upgrade problems (Read 2466 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: ruby upgrade problems

Reply #30 –
Hey ya'll. This package is still causing upgrade issues on my system.

ruby-debug just refuses to download.
 

Re: ruby upgrade problems

Reply #31 –
Quote from: Flmkane – on
Hey ya'll. This package is still causing upgrade issues on my system.

ruby-debug just refuses to download.


Solution is still to either build the package yourself or install from Arch. Or figure out why you need ruby-debug in the first place, as no Artix packages explicitly require it.

Re: ruby upgrade problems

Reply #32 –
Quote from: corysanin – on
Quote from: Flmkane – on
Hey ya'll. This package is still causing upgrade issues on my system.

ruby-debug just refuses to download.


Solution is still to either build the package yourself or install from Arch. Or figure out why you need ruby-debug in the first place, as no Artix packages explicitly require it.

Thanks for the response.

I do know WHY I need ruby. It's a dependency for asciidoctor, which is a dependency for Freecad.

Re: ruby upgrade problems

Reply #33 –
The only issue is a missing ruby-debug package, which is only necessary for debugging Ruby. Installing ruby itself and ruby-bundled-gems should, in theory, work.

Re: ruby upgrade problems

Reply #34 –
This is what worked for me:
1. Build and install ruby-debug 1.7.1-1.2 manually as indicated further above.
2. Run pacman -Syu. You get a bunch of lines like these:
Code: [Select]
ruby: /usr/lib/ruby/gems/3.2.0/gems/debug-1.7.1/CONTRIBUTING.md exists in filesystem (owned by ruby-debug)
ruby: /usr/lib/ruby/gems/3.2.0/gems/debug-1.7.1/Gemfile exists in filesystem (owned by ruby-debug)
ruby: /usr/lib/ruby/gems/3.2.0/gems/debug-1.7.1/LICENSE.txt exists in filesystem (owned by ruby-debug)
3. Rename/back up all these files.
4. Run pacman -Syu. The update completes normally.

Re: ruby upgrade problems

Reply #35 –
Might be premature in saying this 🤞 but going to declare this problem solved until proven otherwise. ruby-debug should be propagated to most mirrors at this time.