Arch Linux User Repository

It is a known fact that ruby-rails is in a bad state in Archlinux right now. And since part of it is in the repos and part in AUR this can't be fixed by AUR alone.

I was already on the way to building a split package for this in 2022 when I was derailed by a broken ruby setup in general. I'm getting close to releasing ruby 3.2 to the official repos which will improve the entire situation.

But the real fix for ruby-rails is a split package that builds all rails related gems at the same time and in the same version.

It is a known fact that ruby-rails is in a bad state in Archlinux right now. And since part of it is in the repos and part in AUR this can't be fixed by AUR alone.

I was already on the way to building a split package for this in 2022 when I was derailed by a broken ruby setup in general. I'm getting close to releasing ruby 3.2 to the official repos which will improve the entire situation.

But the real fix for ruby-rails is a split package that builds all rails related gems at the same time and in the same version.

This doesn't work. You need to update this + all ruby-action* and ruby-active* deps all at once.

Then it also probably wouldn't, because ruby-activesupport from repos is at version 6.x.

@Segaja, apologies, I filled orphan request for ruby-activemodel, didn't see your comment here. But do you maybe have any update on the situation? It has been 8 months.

@clarfonthey, I know that these packages are ood and I'm already working on a split package for this in the official [community] repo, but this is a lot of work. Especially the testing part of this.

I'm sorry it takes so long, but as I said I'm already working on it.

I marked this package and multiple of its dependencies as out of date, since Rails 7 is now released.

Personally, I think that this package should be made into a split package that provides each of its various dependencies (ruby-activerecord, etc.) since they all require downloading the Rails code to build, and ultimately, they all will need to be installed together anyway. Users will still have the option to partially install the packages once their built, but there really isn't much of a need to download the same source multiple times to build each package.

There's also ruby-activesupport, which is in community, which I would also consider as something that should be part of this package. I've been particularly having trouble upgrading the AUR packages for Rails without updating that one.

error: packages failed to build: ruby-railties-6.1.4.1-2 ruby-actionview-6.1.4.1-4 ruby-activerecord-6.1.4.1-2 ruby-actionmailer-6.1.4.1-1 ruby-sprockets-rails-3.4.1-1 ruby-actioncable-6.1.4.1-1 ruby-rails-6.1.4.7-1 ruby-activemodel-6.1.4.1-2 ruby-actionpack-6.1.4.1-4

@linuxninja, you can install ruby-activemodel by installing it the first time without check() calls, as ruby-rails is only a checkdepends for that package.

Afterwards you can install ruby-rails.

At the end you can then reinstall ruby-activemodel normally to get the checks run once.

@mehalter, you might want to check the dependency list for this package sure to use depends, makedeepnds, checkdepends properly. I doubt this package needs all these dependencies at runtime.

Looks like we have an AUR circular dependency:

ruby-rails has a dependency on ruby-activemodel ruby-activemodel has a dependency on ruby-rails

Neither can be installed as each depends on the other.

This package is missing the dependency to https://aur.archlinux.org/packages/ruby-actioncable/ according to the https://rubygems.org/gems/rails dependencies list.

Once my orphaned request on ruby-actioncable gets through i will update this to 6.1.4.1

@mehalter no worries. I know updating ruby packages can take time.

If any of my packages give you trouble please let me know and I'm sure we can figure something out. I'm also available on IRC if needed.