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
Bug 1924745 - required libcatalyst version not available
Summary: required libcatalyst version not available
Status: CLOSED DUPLICATE of bug 1923074
Alias: None
Product: Fedora
Classification: Fedora
Component: paraview
Version: rawhide
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-03 14:38 UTC by George R. Goffe
Modified: 2021-02-04 03:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-04 03:19:59 UTC
Type: Bug

Attachments (Terms of Use)

Description George R. Goffe 2021-02-03 14:38:58 UTC
Description of problem: system upgrade for paraview requires libcatalyst version that is not availble

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.see below

Actual results:
see below

Expected results:

Additional info:

 Problem 1: cannot install the best update candidate for package paraview-5.8.1-7.fc34.x86_64
  - problem with installed package paraview-5.8.1-7.fc34.x86_64
  - nothing provides needed by paraview-5.9.0-1.fc34.x86_64
 Problem 2: cannot install the best update candidate for package paraview-data-5.8.1-7.fc34.noarch
  - problem with installed package paraview-data-5.8.1-7.fc34.noarch
  - package paraview-data-5.9.0-1.fc34.noarch requires paraview = 5.9.0-1.fc34, but none of the providers can be installed
  - nothing provides needed by paraview-5.9.0-1.fc34.i686
  - nothing provides needed by paraview-5.9.0-1.fc34.x86_64

Comment 1 Orion Poplawski 2021-02-04 03:19:59 UTC

*** This bug has been marked as a duplicate of bug 1923074 ***

Note You need to log in before you can comment on or make changes to this bug.