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 697842 - paraview bundles copy of VTK library
Summary: paraview bundles copy of VTK library
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: paraview
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL: https://gitlab.kitware.com/paraview/p...
Whiteboard:
Depends On:
Blocks: DuplicSysLibsTracker
TreeView+ depends on / blocked
 
Reported: 2011-04-19 12:22 UTC by Dan Horák
Modified: 2020-02-27 08:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dan Horák 2011-04-19 12:22:27 UTC 
If I see correctly paraview bundles copy of VTK library that exists a separate package.
Comment 1 Orion Poplawski 2011-04-19 14:21:21 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.
Comment 2 markusN 2012-09-29 07:59:56 UTC 
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."
Comment 3 Orion Poplawski 2012-12-17 23:52:58 UTC 
I've dropped -DVTK_OPENGL_HAS_OSMESA:BOOL=ON for paraview 3.98.0.  We're closer to unbundling vtk, maybe next release.
Comment 4 Tyson Whitehead 2013-03-27 21:21:48 UTC 
Any chance this could get fixed in the F17 paraview as well?  Thanks!
Comment 5 Orion Poplawski 2013-03-29 02:33:02 UTC 
https://admin.fedoraproject.org/updates/paraview-3.14.1-4.fc17
Comment 6 Tyson Whitehead 2013-03-29 18:44:05 UTC 
Wow!  That was crazy quick.  Thanks again so very much!
Comment 7 Fedora End Of Life 2013-04-03 19:36:08 UTC 
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
Comment 8 Fedora End Of Life 2015-01-09 21:48:38 UTC 
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.
Comment 9 Dominik 'Rathann' Mierzejewski 2015-08-06 23:03:21 UTC 
The link to upstream bug report doesn't seem to be valid anymore.
Comment 10 Dennis Schridde 2016-01-26 16:32:28 UTC 
(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
Comment 11 Orion Poplawski 2020-02-27 04:54:29 UTC 
Current upstream issue seems to be https://gitlab.kitware.com/paraview/paraview/issues/19515
Note You need to log in before you can comment on or make changes to this bug.