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 1864189 - netcdf: FTBFS in Fedora rawhide/f33
Summary: netcdf: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: netcdf
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 18:21 UTC by Fedora Release Engineering
Modified: 2020-09-25 16:49 UTC (History)
6 users (show)

Fixed In Version: netcdf-4.7.3-4.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-25 16:49:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2020-08-03 18:21 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 18:21 UTC, Fedora Release Engineering
no flags Details
state.log (957 bytes, text/plain)
2020-08-03 18:21 UTC, Fedora Release Engineering
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openucx ucx issues 5535 0 None open Segmentation fault in netcdf test with more than 2 mpi processes 2020-09-18 02:26:00 UTC

Description Fedora Release Engineering 2020-08-03 18:21:14 UTC
netcdf failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix netcdf 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,
netcdf will be orphaned. Before branching of Fedora 34,
netcdf 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 18:21:16 UTC
Created attachment 1706005 [details]
build.log

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

Comment 2 Fedora Release Engineering 2020-08-03 18:21:18 UTC
Created attachment 1706006 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-08-03 18:21:19 UTC
Created attachment 1706007 [details]
state.log

Comment 4 Orion Poplawski 2020-08-06 01:27:09 UTC
This appears to be a ucx issue.  Re-assigning to bring in the ucx packages just to give them a heads up.

Comment 5 Orion Poplawski 2020-08-06 01:28:18 UTC
koschei also seems to agree that it happened with ucx 1.6.1 -> 1.8.1 (1.7.0-> 1.8.0 in my testing)
https://koschei.fedoraproject.org/package/netcdf

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

Comment 7 Fedora Update System 2020-09-07 04:05:39 UTC
FEDORA-2020-bf0800a635 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bf0800a635

Comment 8 Fedora Update System 2020-09-07 21:44:35 UTC
FEDORA-2020-bf0800a635 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-bf0800a635`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bf0800a635

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

Comment 9 Fedora Update System 2020-09-25 16:49:22 UTC
FEDORA-2020-bf0800a635 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.