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

Re: ruby upgrade problems

Reply #15 –
I did get ruby-debug installed before it got pulled again.  Is there anything I can do to test potential problems, or perhaps prove there aren't any?
 

Re: ruby upgrade problems

Reply #16 –
ruby-debug-1.7.1-1.2-x86_64.pkg.tar.zst is my problem here … it's not available on most mirrors (404), and the one that is finally fetched from wherever has an invalid signature … still a server sync problem I guess?

Re: ruby upgrade problems

Reply #18 –
Thanks for the follow-up!

Building the package manually doesn't work though, it fails here with
Code: [Select]
<internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- test/unit/rr (LoadError)
        from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /home/tobias/tmp/artix/my_AUR/ruby-debug/src/ruby-debug/test/console/color_test.rb:6:in `<top (required)>'
        from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in `block in <main>'
        from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in `select'
        from /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in `<main>'
rake aborted!
Command failed with status (1)

Tasks: TOP => test_console
(See full trace by running task with --trace)
==> ERROR: A failure occurred in check().
    Aborting...

Re: ruby upgrade problems

Reply #19 –
You might run into issues if you have out-of-date dependencies. Otherwise makepkg -si works. Maybe --nocheck will take care of it.

Re: ruby upgrade problems

Reply #20 –
--nocheck did the trick. Most probably, my system was too out of date. However, I could now update my system with the self-built package being installed. Thanks a lot again for the help :-)

Re: ruby upgrade problems

Reply #21 –
Experiencing the same ruby-debug package issue, with that package being unheard of. If it were a real package would it be located at a World or Extra repo ? - i.e., would it be stored @ the Artix or the Arch repo's?

Will this issue self-correct as the Artix / Arch maintainers operate?

Any further advice for newbies, re manually building the required file? Or better to wait until the system self-corrects?

Thanks in advance, thanks all  - - -

Re: ruby upgrade problems

Reply #22 –
Quote from: protoshop – on
If it were a real package would it be located at a World or Extra repo ? - i.e., would it be stored @ the Artix or the Arch repo's?
ruby-debug is a real package. It's supposed to be in Artix's world repo.
Quote from: protoshop – on
Will this issue self-correct as the Artix / Arch maintainers operate?
We're aware of the issue and hopefully will get it resolved soon. Read the rest of the thread for more info.
Quote from: protoshop – on
Any further advice for newbies, re manually building the required file? Or better to wait until the system self-corrects?
I'll temporarily make ruby-debug an optional dependency so it doesn't block upgrades. If you really need ruby-debug you'll have to build it yourself. makepkg --nocheck -si ought to do it if you absolutely need to.

Re: ruby upgrade problems

Reply #23 –
"'ll temporarily make ruby-debug an optional dependency so it doesn't block upgrades."

Great idea.

Tried ignoring ruby-debug in /etc/pacman.conf, which didn't work. (It usually does).

Re: ruby upgrade problems

Reply #24 –
Hello, just wanted to ask if there's any solution in sight.
Still getting 404 errors for "ruby-debug" on all mirrors, stalling updates - rechecked my mirrorlist, did -Syyu but to no avail.

I tried manually building this package with "makepkg --nocheck -si", however then the attempted system update resulted in a bunch of "file already exists" errors, which led me to downgrading again. Probably a stupid move to begin with.

Is it safe to alternatively install this package from Arch repo temporarily?

Thank you.

Re: ruby upgrade problems

Reply #26 –
I had to exclude ruby stuff for weeks now when updating.

https://packages.artixlinux.org/packages/world/x86_64/ruby-debug/ > Download from Mirror > 404

All of my mirrors in /etc/pacman.d/mirrorlist rerturn 404 (mirrors generated 2024-07-24)

-Syyu doesn't help


What are command to safely replace artix ruby-debug with arch package? (they are not same version as well `1.7.1-1` and `1.7.1-1.2` btw)

Re: ruby upgrade problems

Reply #27 –
Quote from: protoshop – on
I had similar ruby upgrade issues today. Here's the pacman -Syu print out ;

Code: [Select]
# pacman -Syu
:: Synchronizing package databases...
 system is up to date
 world                   4.8 MiB   798 KiB/s 00:06 [######################] 100%
 galaxy is up to date
 lib32 is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 universe is up to date
:: Starting full system upgrade...
warning: gnome-desktop: local (1:44.0-1.1) is newer than world (1:44.0-1)
warning: gnome-desktop-common: local (1:44.0-1.1) is newer than world (1:44.0-1)
warning: rsync-openrc: local (20210505-2) is newer than world (20210502-1)
:: Replace ruby-abbrev with world/ruby? [Y/n] n
:: Replace ruby-abbrev with extra/ruby? [Y/n] n
:: Replace ruby-base64 with world/ruby? [Y/n] n
:: Replace ruby-base64 with extra/ruby? [Y/n] n
:: Replace ruby-benchmark with world/ruby? [Y/n] n
:: Replace ruby-benchmark with extra/ruby? [Y/n] n
:: Replace ruby-bigdecimal with world/ruby? [Y/n] n
:: Replace ruby-bigdecimal with extra/ruby? [Y/n] n
:: Replace ruby-bundledgems with world/ruby-bundled-gems? [Y/n] n
:: Replace ruby-cgi with world/ruby? [Y/n] n
:: Replace ruby-cgi with extra/ruby? [Y/n] n
:: Replace ruby-csv with world/ruby? [Y/n] n
:: Replace ruby-csv with extra/ruby? [Y/n] n
:: Replace ruby-date with world/ruby? [Y/n] n
:: Replace ruby-date with extra/ruby? [Y/n] n
:: Replace ruby-delegate with world/ruby? [Y/n] n
:: Replace ruby-delegate with extra/ruby? [Y/n] n
:: Replace ruby-did_you_mean with world/ruby? [Y/n] n
:: Replace ruby-did_you_mean with extra/ruby? [Y/n] n
:: Replace ruby-digest with world/ruby? [Y/n] n
:: Replace ruby-digest with extra/ruby? [Y/n] n
:: Replace ruby-drb with world/ruby? [Y/n] n
:: Replace ruby-drb with extra/ruby? [Y/n] n
:: Replace ruby-english with world/ruby? [Y/n] n
:: Replace ruby-english with extra/ruby? [Y/n] n
:: Replace ruby-etc with world/ruby? [Y/n] n
:: Replace ruby-etc with extra/ruby? [Y/n] n
:: Replace ruby-fcntl with world/ruby? [Y/n] n
:: Replace ruby-fcntl with extra/ruby? [Y/n] n
:: Replace ruby-fiddle with world/ruby? [Y/n] n
:: Replace ruby-fiddle with extra/ruby? [Y/n] n
:: Replace ruby-fileutils with world/ruby? [Y/n] n
:: Replace ruby-fileutils with extra/ruby? [Y/n] n
:: Replace ruby-find with world/ruby? [Y/n] n
:: Replace ruby-find with extra/ruby? [Y/n] n
:: Replace ruby-forwardable with world/ruby? [Y/n] n
:: Replace ruby-forwardable with extra/ruby? [Y/n] nn
:: Replace ruby-getoptlong with world/ruby? [Y/n] n
:: Replace ruby-getoptlong with extra/ruby? [Y/n] n
:: Replace ruby-io-console with world/ruby? [Y/n] n
:: Replace ruby-io-console with extra/ruby? [Y/n] n
:: Replace ruby-io-nonblock with world/ruby? [Y/n] n
:: Replace ruby-io-nonblock with extra/ruby? [Y/n] n
:: Replace ruby-io-wait with world/ruby? [Y/n] n
:: Replace ruby-io-wait with extra/ruby? [Y/n] n
:: Replace ruby-ipaddr with world/ruby? [Y/n] n
:: Replace ruby-ipaddr with extra/ruby? [Y/n] n
:: Replace ruby-json with world/ruby? [Y/n] n
:: Replace ruby-json with extra/ruby? [Y/n] n
:: Replace ruby-logger with world/ruby? [Y/n] n
:: Replace ruby-logger with extra/ruby? [Y/n] n
:: Replace ruby-mutex_m with world/ruby? [Y/n] n
:: Replace ruby-mutex_m with extra/ruby? [Y/n] n
:: Replace ruby-net-http with world/ruby? [Y/n] n
:: Replace ruby-net-http with extra/ruby? [Y/n] n
:: Replace ruby-open-uri with world/ruby? [Y/n] n
:: Replace ruby-open-uri with extra/ruby? [Y/n] n
:: Replace ruby-psych with world/ruby? [Y/n] n
:: Replace ruby-psych with extra/ruby? [Y/n] n
:: Replace ruby-reline with world/ruby? [Y/n] n
:: Replace ruby-reline with extra/ruby? [Y/n] n
:: Replace ruby-ruby2_keywords with world/ruby? [Y/n] n
:: Replace ruby-ruby2_keywords with extra/ruby? [Y/n] n
:: Replace ruby-stringio with world/ruby? [Y/n] n
:: Replace ruby-stringio with extra/ruby? [Y/n] n
:: Replace ruby-time with world/ruby? [Y/n] n
:: Replace ruby-time with extra/ruby? [Y/n] n
:: Replace ruby-tmpdir with world/ruby? [Y/n] n
:: Replace ruby-tmpdir with extra/ruby? [Y/n] n
:: Replace ruby-uri with world/ruby? [Y/n] n
:: Replace ruby-uri with extra/ruby? [Y/n] n
resolving dependencies...
looking for conflicting packages...
:: ruby-3.2.4-1.1 and ruby-abbrev-0.1.0-5 are in conflict. Remove ruby-abbrev? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: ruby-3.2.4-1.1 and ruby-abbrev-0.1.0-5 are in conflict

Answering "yes"  to the yes or no questions soon found further conflicts, too.

Then I considered removing Ruby as I don't use it. However "ruby" appears in many program titles. "Pacman -Rs"  requires exact knowledge of Ruby and it's derivatives. So this approach fell short too.

Am wondering what is the pacman command to uninstall any program with a "ruby" in the title ?
*
Or should I wait a few days while the repos catch up with their ruby versioning?
*
Or should I answer yes to each of these type of pacman requests ?;
"
:: ruby-3.2.4-1.1 and ruby-abbrev-0.1.0-5 are in conflict. Remove ruby-abbrev? [y/N] n
"
*
Thanks in advance -   - -


I had the exact same issue. I did this to fix it:


sudo pacman -S archlinux-keyring

Re: ruby upgrade problems

Reply #28 –
@DirtDog, didn't help in my case

Re: ruby upgrade problems

Reply #29 –
Dang, it worked for me. It took 15 minutes to upgrade. No more Ruby issues afterwards