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 1556041 - libhfi1: FTBFS in F28
Summary: libhfi1: FTBFS in F28
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libhfi1
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: dennis.dalessandro
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1550861 (view as bug list)
Depends On:
Blocks: F28FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-03-14 23:06 UTC by Fedora Release Engineering
Modified: 2018-07-11 21:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-09 08:30:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (deleted)
2018-05-28 22:30 UTC, Fedora Release Engineering 		no flags Details
root.log (deleted)
2018-05-28 22:30 UTC, Fedora Release Engineering 		no flags Details
state.log (deleted)
2018-05-28 22:30 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2018-03-14 23:06:44 UTC 
Your package libhfi1 failed to build from source in current F28.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Comment 1 dennis.dalessandro 2018-03-15 00:52:57 UTC 
I suspect this package can be removed from Fedora. It has been obsoleted by rdma-core. What's the procedure here? What have the other RDMA/IB verbs providers done?
Comment 2 Fedora Release Engineering 2018-05-28 22:30:21 UTC 
Created attachment 1444736 [details]
build.log
Comment 3 Fedora Release Engineering 2018-05-28 22:30:25 UTC 
Created attachment 1444737 [details]
root.log
Comment 4 Fedora Release Engineering 2018-05-28 22:30:28 UTC 
Created attachment 1444738 [details]
state.log
Comment 5 Honggang LI 2018-06-12 00:56:46 UTC 
(In reply to dennis.dalessandro from comment #1)
> I suspect this package can be removed from Fedora. It has been obsoleted by
> rdma-core. What's the procedure here? What have the other RDMA/IB verbs
> providers done?

Please retire the package and then close this bug as NOTABUG.

https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Comment 6 dennis.dalessandro 2018-06-28 14:03:43 UTC 
So what have the other RDMA/IB providers done? Is rdma-core fully supported now?
Comment 7 dennis.dalessandro 2018-06-28 14:08:01 UTC 
*** Bug 1550861 has been marked as a duplicate of this bug. ***
Comment 8 Honggang LI 2018-06-29 00:03:21 UTC 
(In reply to dennis.dalessandro from comment #6)
> So what have the other RDMA/IB providers done?

Most of other RDMA/IB provides has been retired. We had opened bugs to ask them to retire the package if they did not.

> Is rdma-core fully supported now?

yes.
Comment 9 Zbigniew Jędrzejewski-Szmek 2018-07-09 04:07:42 UTC 
Dear Maintainer,

your package has not been built successfully in F28. 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.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://fedoraproject.org/wiki/Fails_to_build_from_source#Package_Removal_for_Long-standing_FTBFS_bugs
Comment 10 Igor Raits 2018-07-09 08:30:59 UTC 
I've retired it (hopefully).
Comment 11 dennis.dalessandro 2018-07-11 21:21:51 UTC 
Thanks! I was just getting a chance to look at this bug and seen that. Appreciate it.
Note You need to log in before you can comment on or make changes to this bug.