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
Bug 1800304 - plplot: FTBFS in Fedora rawhide/f32
Summary: plplot: FTBFS in Fedora rawhide/f32
Alias: None
Product: Fedora
Classification: Fedora
Component: plplot
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F32FTBFS
TreeView+ depends on / blocked
Reported: 2020-02-06 20:34 UTC by Fedora Release Engineering
Modified: 2020-05-21 02:52 UTC (History)
1 user (show)

Fixed In Version: plplot-5.15.0-11.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-21 02:52:23 UTC
Type: ---

Attachments (Terms of Use)
build.log (deleted)
2020-02-06 20:34 UTC, Fedora Release Engineering
no flags Details
root.log (deleted)
2020-02-06 20:34 UTC, Fedora Release Engineering
no flags Details
state.log (deleted)
2020-02-06 20:34 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-02-06 20:34:11 UTC
plplot failed to build from source in Fedora rawhide/f32

For details on the mass rebuild see:
Please fix plplot 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,
plplot will be orphaned. Before branching of Fedora 33,
plplot will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Fedora Release Engineering 2020-02-06 20:34:14 UTC
Created attachment 1661527 [details]

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

Comment 2 Fedora Release Engineering 2020-02-06 20:34:16 UTC
Created attachment 1661528 [details]

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

Comment 3 Fedora Release Engineering 2020-02-06 20:34:17 UTC
Created attachment 1661529 [details]

Comment 4 Ben Cotton 2020-02-11 16:40:46 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:23:05 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.


Comment 6 Orion Poplawski 2020-02-22 20:18:27 UTC
Tests fail on s390x only with:

1: ./ line 32: 1560451 Segmentation fault      (core dumped) $DEBUG_CMD "$cdir"/x${index}${lang} -dev $device -o "${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> c_${device}_test.error >| "${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt

Comment 7 Fedora Update System 2020-05-12 14:57:06 UTC
FEDORA-2020-bb0c6f11f5 has been submitted as an update to Fedora 32.

Comment 8 Fedora Update System 2020-05-13 03:55:52 UTC
FEDORA-2020-bb0c6f11f5 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-bb0c6f11f5`
You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 9 Fedora Update System 2020-05-21 02:52:23 UTC
FEDORA-2020-bb0c6f11f5 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.