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 1734864 - python-fedmsg-meta-fedora-infrastructure: FTBFS in Fedora rawhide/f31
Summary: python-fedmsg-meta-fedora-infrastructure: FTBFS in Fedora rawhide/f31
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-fedmsg-meta-fedora-infrastructure
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1735395 (view as bug list)
Depends On:
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
 
Reported: 2019-07-31 16:04 UTC by Fedora Release Engineering
Modified: 2019-11-02 21:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-02 21:55:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (1.28 KB, text/plain)
2019-07-31 16:04 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2019-07-31 16:04 UTC, Fedora Release Engineering 		no flags Details
state.log (539 bytes, text/plain)
2019-07-31 16:04 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2019-07-31 16:04:38 UTC 
python-fedmsg-meta-fedora-infrastructure failed to build from source in Fedora rawhide/f31

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix python-fedmsg-meta-fedora-infrastructure 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,
python-fedmsg-meta-fedora-infrastructure will be orphaned. Before branching of Fedora 32,
python-fedmsg-meta-fedora-infrastructure 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 2019-07-31 16:04:40 UTC 
Created attachment 1595163 [details]
build.log
Comment 2 Fedora Release Engineering 2019-07-31 16:04:42 UTC 
Created attachment 1595164 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2019-07-31 16:04:44 UTC 
Created attachment 1595165 [details]
state.log
Comment 4 Ben Cotton 2019-08-13 16:59:09 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 5 Ben Cotton 2019-08-13 18:43:01 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.
Comment 6 Miro Hrončok 2019-08-20 15:40:51 UTC 
*** Bug 1735395 has been marked as a duplicate of this bug. ***
Comment 7 Miro Hrončok 2019-08-20 15:43:55 UTC 
This blocks the rebuild for Python 3.8. The following packages are impacted:


$ repoquery --repo=rawhide{,-source} --whatrequires python3-fedmsg-meta-fedora-infrastructure
datagrepper-0:0.9.5-4.fc31.noarch
datagrepper-0:0.9.5-4.fc31.src
datanommer-commands-0:0.7.2-5.fc31.noarch
datanommer-commands-0:0.7.2-5.fc31.src
koschei-backend-fedora-0:2.4.0-6.fc31.noarch
python-datanommer-models-0:0.9.1-8.fc31.src


$ repoquery --repo=rawhide{,-source} --whatrequires python3-datanommer-models
datagrepper-0:0.9.5-4.fc31.noarch
datagrepper-0:0.9.5-4.fc31.src
datanommer-0:0.2.0-16.fc31.noarch
datanommer-0:0.2.0-16.fc31.src
datanommer-commands-0:0.7.2-5.fc31.noarch
datanommer-commands-0:0.7.2-5.fc31.src
python-datanommer-consumer-0:0.8.1-7.fc31.src
python3-datanommer-consumer-0:0.8.1-7.fc31.noarch
Comment 8 Fedora Release Engineering 2019-09-22 04:22:49 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 9 Fedora Release Engineering 2019-09-29 04:25:23 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 10 Fedora Release Engineering 2019-10-06 04:22:25 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 11 Fedora Release Engineering 2019-10-13 04:22:22 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 12 Fedora Release Engineering 2019-10-20 04:22:24 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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 32 according to the schedule [3],
any packages not successfully rebuilt at least on 30 will be
retired regardless of the status of this bug.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 13 Fedora Release Engineering 2019-10-27 04:22:20 UTC 
Dear Maintainer,

your package has not been built successfully in 31. 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 32 according to the schedule [3],
any packages not successfully rebuilt at least on 30 will be
retired regardless of the status of this bug.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 14 Kevin Fenzi 2019-11-02 21:55:42 UTC 
This now builds fine in rawhide.
Note You need to log in before you can comment on or make changes to this bug.