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 1583381 - openmx: FTBFS in Fedora 28
Summary: openmx: FTBFS in Fedora 28
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: openmx
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1605326 (view as bug list)
Depends On:
Blocks: F28FTBFS F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-05-28 22:07 UTC by Fedora Release Engineering
Modified: 2019-05-28 22:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:14:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (86.11 KB, text/plain)
2018-05-28 22:07 UTC, Fedora Release Engineering 		no flags Details
build.log (1.36 MB, text/plain)
2018-05-28 22:07 UTC, Fedora Release Engineering 		no flags Details
state.log (619 bytes, text/plain)
2018-05-28 22:07 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2018-05-28 22:07:31 UTC 
openmx failed to build from source in Fedora 28

https://koji.fedoraproject.org/koji/taskinfo?taskID=27245124
https://koji.fedoraproject.org/koji/buildinfo?buildID=1086193


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Please fix openmx 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,
openmx will be orphaned. Before branching of Fedora 29,
openmx 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 2018-05-28 22:07:37 UTC 
Created attachment 1444236 [details]
root.log
Comment 2 Fedora Release Engineering 2018-05-28 22:07:44 UTC 
Created attachment 1444240 [details]
build.log
Comment 3 Fedora Release Engineering 2018-05-28 22:07:47 UTC 
Created attachment 1444243 [details]
state.log
Comment 4 marcindulak 2018-06-08 19:51:33 UTC 
The package is already orphaned:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/threa
d/POQPJIW5NGZGZRI7RKPLBO7K64ROCGCZ/
Comment 5 marcindulak 2018-07-05 22:41:31 UTC 
Last build attempt, with bundled elpa https://koji.fedoraproject.org/koji/taskinfo?taskID=28043496
Comment 6 Zbigniew Jędrzejewski-Szmek 2018-07-09 04:15:22 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 7 Zbigniew Jędrzejewski-Szmek 2018-07-09 04:20:18 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 8 marcindulak 2018-07-09 15:29:28 UTC 
I've already orphaned openmx, and left the rawhide spec in the best state I could (build still failing). Only waiting now until this bug gets automatically handled and closed.
Comment 9 marcindulak 2018-08-26 09:05:00 UTC 
*** Bug 1605326 has been marked as a duplicate of this bug. ***
Comment 10 Ben Cotton 2019-05-02 21:02:00 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 11 Ben Cotton 2019-05-28 22:14:28 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.