Bug 1800023 - rubygem-pry: FTBFS in Fedora rawhide/f32
Summary: rubygem-pry: FTBFS in Fedora rawhide/f32
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-pry
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F32FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-02-06 19:51 UTC by Fedora Release Engineering
Modified: 2020-05-01 00:36 UTC (History)
3 users (show)

Fixed In Version: rubygem-pry-0.13.1-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-01 00:36:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (30.99 KB, text/plain)
2020-02-06 19:51 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-02-06 19:51 UTC, Fedora Release Engineering
no flags Details
state.log (1002 bytes, text/plain)
2020-02-06 19:51 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-02-06 19:51:22 UTC
rubygem-pry failed to build from source in Fedora rawhide/f32

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix rubygem-pry 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-pry will be orphaned. Before branching of Fedora 33,
rubygem-pry 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-02-06 19:51:24 UTC
Created attachment 1660737 [details]
build.log

Comment 2 Fedora Release Engineering 2020-02-06 19:51:26 UTC
Created attachment 1660738 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-02-06 19:51:27 UTC
Created attachment 1660739 [details]
state.log

Comment 4 Ben Cotton 2020-02-11 16:49:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 5 Fedora Release Engineering 2020-02-16 04:28:47 UTC
Dear Maintainer,

your package has not been built successfully in 32. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
will be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 33 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 31 will be
retired regardless of the status of this bug.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/33/Schedule

Comment 6 Fedora Update System 2020-04-21 07:12:48 UTC
FEDORA-2020-156102bc21 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-156102bc21

Comment 7 Fedora Update System 2020-04-21 18:43:30 UTC
FEDORA-2020-156102bc21 has been pushed to the Fedora 32 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-156102bc21`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-156102bc21

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

Comment 8 Fedora Update System 2020-05-01 00:36:02 UTC
FEDORA-2020-156102bc21 has been pushed to the Fedora 32 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.