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 1716462
| Summary: | gdcm fails to build | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
| Component: | gdcm | Assignee: | Ankur Sinha (FranciscoD) <sanjay.ankur> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | igor.raits, neuro-sig, sanjay.ankur, sebp |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://copr.fedorainfracloud.org/coprs/g/python/python3.8/package/gdcm/ | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-04 14:43:03 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: | 1686977 | ||
|
Description
Miro Hrončok
2019-06-03 14:35:18 UTC
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.0JsFuv
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf GDCM-2.8.9
+ /usr/bin/gzip -dc /builddir/build/SOURCES/gdcm-2.8.9.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd GDCM-2.8.9
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/bin/git init -q
+ /usr/bin/git config user.name rpm-build
+ /usr/bin/git config user.email '<rpm-build>'
+ /usr/bin/git add .
+ /usr/bin/git commit -q --allow-empty -a --author 'rpm-build <rpm-build>' -m 'gdcm-2.8.9 base'
+ cd /builddir/build/BUILD
+ cd GDCM-2.8.9
+ /usr/bin/gzip -dc /builddir/build/SOURCES/gdcmData.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'Patch #1 (0001-Use-copyright.patch):'
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
+ echo 'Patch #2 (0002-Increase-xslt-maxdepth.patch):'
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
error: Bad exit status from /var/tmp/rpm-tmp.0JsFuv (%prep)
Bad exit status from /var/tmp/rpm-tmp.0JsFuv (%prep)
Patch #1 (0001-Use-copyright.patch):
patching file CMake/UseCopyright.cmake
Patch #2 (0002-Increase-xslt-maxdepth.patch):
patching file Utilities/doxygen/CMakeLists.txt
Hunk #1 FAILED at 252.
1 out of 1 hunk FAILED -- saving rejects to file Utilities/doxygen/CMakeLists.txt.rej
Seems that Ankur pushed commit "Update to 2.8.9: DOES NOT BUILD YET". Which of course is not the proper way to do it. Ankur, please submit PRs for WIP things. This requires a lot of work, and if I did it in a fork, others would not be aware of the progress that I've made. I'm working on gdcm and will push a build when it does build. Please leave it for me. > others would not be aware of the progress that I've made.
If you open a WIP pull request, they would.
Sorry. Please revert it etc and proceed if you need to. Can we make it build instead of reverting? We still have time for 3.8 to be pushed to rawhide. I do not have an ETA on that. Sorry. The new versions require all patches to be re-checked/rebased so it isn't a trivial update. Now, the 3.0.0 version requires a CharLS version bump so I'm working on that. I have a successful build here now. Will have a PR open before the end of the day. There's no python 3.8 related issues with building so I'll close this now. This has still not been fixed, please don't close before it is. Hrm, sorry. I dont understand. It isnt a Python 3.8 related bug. It's an unrelated FTBFS for which yet another bug is open.. Please refer to the other relevant bugs for updates. *** This bug has been marked as a duplicate of bug 1735238 *** |