Bug 1792740

Summary: z3-doc subpackage is different across architectures
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: z3Assignee: Jerry James <loganjerry>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: loganjerry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 15:16:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard W.M. Jones 2020-01-19 14:49:03 UTC
Description of problem:

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

z3 FTBFS in Fedora Rawhide because the -doc subpackage contains
different content across architectures.  I think this is a new
test that Koji has started doing.

BuildError: The following noarch package built differently on different architectures: z3-doc-4.8.7-4.fc32.noarch.rpm
rpmdiff output was:
removed     /usr/share/doc/z3-doc/html/inherit_graph_128.dot
removed     /usr/share/doc/z3-doc/html/inherit_graph_128.map
removed     /usr/share/doc/z3-doc/html/inherit_graph_128.md5
removed     /usr/share/doc/z3-doc/html/inherit_graph_128.png
removed     /usr/share/doc/z3-doc/html/inherit_graph_129.dot
removed     /usr/share/doc/z3-doc/html/inherit_graph_129.map
removed     /usr/share/doc/z3-doc/html/inherit_graph_129.md5
removed     /usr/share/doc/z3-doc/html/inherit_graph_129.png

Version-Release number of selected component (if applicable):

z3 4.8.7-4.fc32

How reproducible:

At least once.

Steps to Reproduce:
1. Build the package in Koji.

Comment 1 Jerry James 2020-01-22 04:09:41 UTC
I've been staring at the mk_api_doc.py script, and I just don't see why this is happening.  I'm going to make -doc archful for now, but I'll try to figure out what is going on.  Thanks for the report!

Comment 2 Ben Cotton 2020-02-11 17:30:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 3 Fedora Program Management 2021-04-29 16:02:15 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 4 Ben Cotton 2021-05-25 15:16:45 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.