Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1863729 - rubygem-puma: FTBFS in Fedora rawhide/f33
Summary: rubygem-puma: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-puma
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Valena
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 17:15 UTC by Fedora Release Engineering
Modified: 2020-09-25 16:53 UTC (History)
4 users (show)

Fixed In Version: rubygem-puma-4.3.6-1.fc34 rubygem-puma-4.3.6-1.eln103 rubygem-puma-4.3.6-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-09 14:50:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (deleted)
2020-08-03 17:15 UTC, Fedora Release Engineering
no flags Details
root.log (deleted)
2020-08-03 17:15 UTC, Fedora Release Engineering
no flags Details
state.log (deleted)
2020-08-03 17:15 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-08-03 17:15:44 UTC
rubygem-puma failed to build from source in Fedora rawhide/f33

https://koji.fedoraproject.org/koji/taskinfo?taskID=47965119


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix rubygem-puma at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
rubygem-puma will be orphaned. Before branching of Fedora 34,
rubygem-puma will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2020-08-03 17:15:46 UTC
Created attachment 1704705 [details]
build.log

Comment 2 Fedora Release Engineering 2020-08-03 17:15:47 UTC
Created attachment 1704706 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2020-08-03 17:15:48 UTC
Created attachment 1704707 [details]
state.log

Comment 4 Jun Aruga 2020-08-07 10:01:13 UTC
There is a PR to upgrade puma to the latest version.
https://src.fedoraproject.org/rpms/rubygem-puma/pull-request/4

Comment 5 Ben Cotton 2020-08-11 14:06:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 6 Fedora Update System 2020-09-09 14:50:15 UTC
FEDORA-2020-93c5e457f0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-09-09 14:56:55 UTC
FEDORA-2020-fe354f24e8 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe354f24e8

Comment 8 Fedora Update System 2020-09-10 15:48:32 UTC
FEDORA-2020-fe354f24e8 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fe354f24e8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe354f24e8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-09-15 15:03:38 UTC
FEDORA-2020-bb88636805 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-09-25 16:53:50 UTC
FEDORA-2020-fe354f24e8 has been pushed to the Fedora 33 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.