Bug 697842
| Summary: | paraview bundles copy of VTK library | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Horák <dan> |
| Component: | paraview | Assignee: | Orion Poplawski <orion> |
| Status: | ASSIGNED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dennis.schridde, dominik, neteler, orion, pertusus, twhitehead |
| Target Milestone: | --- | Keywords: | Tracking |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://gitlab.kitware.com/paraview/paraview/issues/19515 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | 504493 | ||
|
Description
Dan Horák
2011-04-19 12:22:27 UTC
Yeah, not sure how possible it will be to separate. Kitware is the developer of both paraview and vtk and their development are intertwined, but paraview often depends on a very specific at possibly modified vtk. I'll poke them about it though. There is an important fix needed, see bug 838228#10 which points to bug 744434: Citation: "you have to compile VTK without -DVTK_OPENGL_HAS_OSMESA:BOOL=ON, but paraview was missed as it has it's own copy." I've dropped -DVTK_OPENGL_HAS_OSMESA:BOOL=ON for paraview 3.98.0. We're closer to unbundling vtk, maybe next release. Any chance this could get fixed in the F17 paraview as well? Thanks! Wow! That was crazy quick. Thanks again so very much! This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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. The link to upstream bug report doesn't seem to be valid anymore. (In reply to Dominik 'Rathann' Mierzejewski from comment #9) > The link to upstream bug report doesn't seem to be valid anymore. The upstream bug was moved to: http://www.paraview.org/Bug/view.php?id=12106 Current upstream issue seems to be https://gitlab.kitware.com/paraview/paraview/issues/19515 |