Bug 2371179 - rack-cors is going to be broken by update to Rack 3.x+
Summary: rack-cors is going to be broken by update to Rack 3.x+
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-rack-cors
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: František Dvořák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-09 15:52 UTC by Vít Ondruch
Modified: 2025-11-14 03:52 UTC (History)
2 users (show)

Fixed In Version: rubygem-rack-cors-1.1.1-15.fc44
Clone Of:
Environment:
Last Closed: 2025-11-14 03:52:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2025-06-09 15:52:18 UTC
I am soon going to update rubygem-rack to Rack 3.x+ due to update of Ruby on Rails 8. Here is the PR:

https://src.fedoraproject.org/rpms/rubygem-rack/pull-request/5

But this is going to break rubygem-rack-cors. The test suite fails with errors such as:

~~~
  1) Error:
Rack::Cors#test_0022_should not allow everything if Origin is configured as blank string:
NameError: uninitialized constant Rack::Builder
    test/unit/cors_test.rb:65:in 'load_app'
    test/unit/cors_test.rb:77:in 'block (2 levels) in <top (required)>'
~~~

I would appreciate your help and if this can be fixed prior RoR 8 lands

Reproducible: Always

Actual Results:
Test suite fails testing against Rack 3.x+

Expected Results:
Test suite pass testing against Rack 3.x+

Comment 1 Fedora Update System 2025-11-14 03:49:09 UTC
FEDORA-2025-e5a2a451f5 (rubygem-rack-cors-1.1.1-15.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e5a2a451f5

Comment 2 Fedora Update System 2025-11-14 03:52:27 UTC
FEDORA-2025-e5a2a451f5 (rubygem-rack-cors-1.1.1-15.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.