Bug 1106644
| Summary: | glite-lbjp-common-gsoap-plugin: FTBFS in rawhide | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dennis Gilmore <dennis> | ||||||||
| Component: | glite-lbjp-common-gsoap-plugin | Assignee: | František Dvořák <valtri> | ||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | valtri | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-06-12 21:55:16 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: | 1105908 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Dennis Gilmore
2014-06-09 16:56:35 UTC
Created attachment 904899 [details]
build.log
Created attachment 904900 [details]
root.log
Created attachment 904901 [details]
state.log
It looks like the failure is not easily reproducible. I suspect the problem is with parallel build (some header were probably not fully generated by gsoap when used). Repeated build succeeded. Fixed upstream: https://github.com/CESNET/glite-lb/commit/5692fb4608dbf6a480bc21b1b4377929491b3205 Local patch in Fedora isn't needed, new release is planned within a month. glite-lb-client-6.0.10-1.fc20,glite-lb-client-java-2.0.7-1.fc20,glite-lb-common-9.1.1-1.fc20,glite-lbjp-common-gss-3.2.16-1.fc20,glite-lbjp-common-jp-interface-2.3.11-1.fc20,glite-lbjp-common-log-1.3.11-1.fc20,glite-lbjp-common-maildir-2.3.11-1.fc20,glite-lbjp-common-server-bones-2.3.11-1.fc20,glite-lbjp-common-trio-2.3.13-1.fc20,glite-lb-logger-2.4.23-1.fc20,glite-lb-state-machine-2.0.9-1.fc20,glite-lb-types-2.0.10-1.fc20,glite-lb-ws-interface-4.0.9-1.fc20,glite-lbjp-common-gsoap-plugin-3.2.12-1.fc20,glite-lbjp-common-db-3.2.11-1.fc20,glite-jobid-api-java-1.3.9-1.fc20,glite-jobid-api-cpp-1.3.10-1.fc20,glite-jobid-api-c-2.2.13-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/glite-lb-client-6.0.10-1.fc20,glite-lb-client-java-2.0.7-1.fc20,glite-lb-common-9.1.1-1.fc20,glite-lbjp-common-gss-3.2.16-1.fc20,glite-lbjp-common-jp-interface-2.3.11-1.fc20,glite-lbjp-common-log-1.3.11-1.fc20,glite-lbjp-common-maildir-2.3.11-1.fc20,glite-lbjp-common-server-bones-2.3.11-1.fc20,glite-lbjp-common-trio-2.3.13-1.fc20,glite-lb-logger-2.4.23-1.fc20,glite-lb-state-machine-2.0.9-1.fc20,glite-lb-types-2.0.10-1.fc20,glite-lb-ws-interface-4.0.9-1.fc20,glite-lbjp-common-gsoap-plugin-3.2.12-1.fc20,glite-lbjp-common-db-3.2.11-1.fc20,glite-jobid-api-java-1.3.9-1.fc20,glite-jobid-api-cpp-1.3.10-1.fc20,glite-jobid-api-c-2.2.13-1.fc20 glite-jobid-api-c-2.2.13-1.fc19,glite-jobid-api-cpp-1.3.10-1.fc19,glite-jobid-api-java-1.3.9-1.fc19,glite-lb-client-6.0.10-1.fc19,glite-lb-client-java-2.0.7-1.fc19,glite-lb-common-9.1.1-1.fc19,glite-lbjp-common-db-3.2.11-1.fc19,glite-lbjp-common-gsoap-plugin-3.2.12-1.fc19,glite-lbjp-common-gss-3.2.16-1.fc19,glite-lbjp-common-jp-interface-2.3.11-1.fc19,glite-lbjp-common-log-1.3.11-1.fc19,glite-lbjp-common-maildir-2.3.11-1.fc19,glite-lbjp-common-server-bones-2.3.11-1.fc19,glite-lbjp-common-trio-2.3.13-1.fc19,glite-lb-logger-2.4.23-1.fc19,glite-lb-state-machine-2.0.9-1.fc19,glite-lb-types-2.0.10-1.fc19,glite-lb-ws-interface-4.0.9-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/glite-jobid-api-c-2.2.13-1.fc19,glite-jobid-api-cpp-1.3.10-1.fc19,glite-jobid-api-java-1.3.9-1.fc19,glite-lb-client-6.0.10-1.fc19,glite-lb-client-java-2.0.7-1.fc19,glite-lb-common-9.1.1-1.fc19,glite-lbjp-common-db-3.2.11-1.fc19,glite-lbjp-common-gsoap-plugin-3.2.12-1.fc19,glite-lbjp-common-gss-3.2.16-1.fc19,glite-lbjp-common-jp-interface-2.3.11-1.fc19,glite-lbjp-common-log-1.3.11-1.fc19,glite-lbjp-common-maildir-2.3.11-1.fc19,glite-lbjp-common-server-bones-2.3.11-1.fc19,glite-lbjp-common-trio-2.3.13-1.fc19,glite-lb-logger-2.4.23-1.fc19,glite-lb-state-machine-2.0.9-1.fc19,glite-lb-types-2.0.10-1.fc19,glite-lb-ws-interface-4.0.9-1.fc19 glite-lb-client-6.0.10-1.fc20, glite-lb-client-java-2.0.7-1.fc20, glite-lb-common-9.1.1-1.fc20, glite-lbjp-common-gss-3.2.16-1.fc20, glite-lbjp-common-jp-interface-2.3.11-1.fc20, glite-lbjp-common-log-1.3.11-1.fc20, glite-lbjp-common-maildir-2.3.11-1.fc20, glite-lbjp-common-server-bones-2.3.11-1.fc20, glite-lbjp-common-trio-2.3.13-1.fc20, glite-lb-logger-2.4.23-1.fc20, glite-lb-state-machine-2.0.9-1.fc20, glite-lb-types-2.0.10-1.fc20, glite-lb-ws-interface-4.0.9-1.fc20, glite-lbjp-common-gsoap-plugin-3.2.12-1.fc20, glite-lbjp-common-db-3.2.11-1.fc20, glite-jobid-api-java-1.3.9-1.fc20, glite-jobid-api-cpp-1.3.10-1.fc20, glite-jobid-api-c-2.2.13-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. glite-jobid-api-c-2.2.13-1.fc19, glite-jobid-api-cpp-1.3.10-1.fc19, glite-jobid-api-java-1.3.9-1.fc19, glite-lb-client-6.0.10-1.fc19, glite-lb-client-java-2.0.7-1.fc19, glite-lb-common-9.1.1-1.fc19, glite-lbjp-common-db-3.2.11-1.fc19, glite-lbjp-common-gsoap-plugin-3.2.12-1.fc19, glite-lbjp-common-gss-3.2.16-1.fc19, glite-lbjp-common-jp-interface-2.3.11-1.fc19, glite-lbjp-common-log-1.3.11-1.fc19, glite-lbjp-common-maildir-2.3.11-1.fc19, glite-lbjp-common-server-bones-2.3.11-1.fc19, glite-lbjp-common-trio-2.3.13-1.fc19, glite-lb-logger-2.4.23-1.fc19, glite-lb-state-machine-2.0.9-1.fc19, glite-lb-types-2.0.10-1.fc19, glite-lb-ws-interface-4.0.9-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |