Ruby on Rails 8.1 #259
Labels
No labels
Ansible
basic support
Ansible
NFS server
Ansible/pxe
Ansible/Wildfly
distribution
bug
distribution
release test
distribution
rfe
documentation
improvement
documentation
new
documentation
review request
documentation
update required
meeting
need info
project
backup&restore
project
home server spin-off
project
LocalKDC
project
strengthening updates
status
in progress
status
on hold
status
pending activity
Working Group Organization
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
server/tickets#259
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ruby on Rails 8.1 is the latest version of well known web framework written in Ruby.
See also: https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_8.1
Following https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_8.1
For F45 Beta 1.3 and I can't get any of the default app deployment examples to work at all. All of them fail with missing dependencies.
If I use the last example, which should deploy using Fedora only dependencies, I get:
/usr/share/rubygems/rubygems/resolver.rb:228:in 'Gem::Resolver#search_for': Unable to resolve dependency: 'rdoc (>= 4.0.0)' requires 'rbs (>= 4.0.0)' (Gem::UnsatisfiableDependencyError)
If I check package versions:
Name : rubygem-rbs
Epoch : 0
Version : 3.10.0
I tried a gem install, but I had to install the ruby-devel packages and then the rbs compilation failed.
I did a
dnf group install development-toolsand that meant the rbs gem compiled and I had 4.2.0 available.The default app then deploys.
It would be great if we could update the rubgem-rbs package to the latest version in the F45 repos so that the default app deploys without extra devel requirements on the user side.
I mailed the Ruby SIG to find out how we should proceed with this and whether they want a bug filed in bugzilla.
Once rubygem-rbs is updated, everything works as expected.
The issue here was down to a lack of attention on my part, and a change to how DNF functions. So the test instructions were slightly wrong.
Basically
dnf group install "Ruby on Rails"had failed because dnf5 doesn't respect group names any more. You have to specify the ID.I retested on a fresh vm and everything worked smoothly. Some documentation might need updating. I have spoken to the Ruby folks about this.