Bug 1675694
| Summary: | purple-plugin_pack: FTBFS in Fedora rawhide/f30 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | purple-plugin_pack | Assignee: | Jan Synacek <jsynacek> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 31 | CC: | ivazqueznet, jsynacek, jwboyer, karsten, kasal, kevin, nushio, panovotn, praiskup | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | purple-plugin_pack-2.7.0-11.fc32 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-10-14 08:02:50 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1674516 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2019-02-11 21:30:43 UTC
Created attachment 1532106 [details]
build.log
file build.log too big, will only attach last 1024 bytes
Created attachment 1532107 [details]
root.log
file root.log too big, will only attach last 1024 bytes
Created attachment 1532108 [details]
state.log
Dear Maintainer, your package has not been built successfully in f30. 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. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Dear Maintainer, your package has not been built successfully in f30. 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. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Dear Maintainer, your package has not been built successfully in f30. 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. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule So the problem seems to be: .. checking for PURPLE... yes checking for PIDGIN... yes checking for FINCH... no no checking for GLIB... yes checking for GTK... yes checking for GNT... no ... BUILDSTDERR: co./configure: line 14473: no: command not found BUILDSTDERR: ./configure: line 14482: no: command not found + make -j6 BUILDSTDERR: /bin/sh: no: command not found BUILDSTDERR: /bin/sh: no: command not found BUILDSTDERR: make: *** [Makefile:844: plugin_pack.stats] Error 127 BUILDSTDERR: make: *** Waiting for unfinished jobs.... BUILDSTDERR: make: *** [Makefile:847: plugin_pack.list] Error 127 ... The infrastructure tooling doesn't seem to like the "no" all by itself on a line. I can build the package without any problems when I execute rpmbuild manually. I have no idea what the correct component to fix this in should be, so I'm reassigning it to distribution to hopefully get wider audience. Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule Dear Maintainer, your package has not been built successfully in 30. 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 31 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 30 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/31/Schedule This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. This is not a 'distribution' bug. Looks like something is wrong in your configure script, but not sure what... moving over to autoconf to see if they can help out. (see Makefile, and the line 'PYTHON = no', that's because /bin/python is missing) |