Bug 1774628

Summary: Cannot install scilab
Product: [Fedora] Fedora Reporter: Zirneklitis <k_a_r_l_o_>
Component: scilabAssignee: James Paul Turner <jamesturner246>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: c.david86, extras-orphan, kelevel+redhat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-16 11:16:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zirneklitis 2019-11-20 15:15:19 UTC
Description of problem:

Impossible to install scilab due to missing dependencies.

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

scilab-6.0.2-2.fc31.x86_64

How reproducible:
always

Steps to Reproduce:

$ dnf install scilab

Actual results:

Last metadata expiration check: 0:31:25 ago on Wed 20 Nov 2019 03:56:03 PM EET.
Dependencies resolved.

 Problem: conflicting requests
  - nothing provides jeuclid needed by scilab-6.0.2-2.fc31.x86_64
  - nothing provides jrosetta needed by scilab-6.0.2-2.fc31.x86_64

Expected results:

Successful installation.

Comment 1 Ben Cotton 2019-11-27 14:21:57 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 Ben Cotton 2019-11-27 15:57:55 UTC
This bug was accidentally closed due to a query error. Reopening.

Comment 3 James Paul Turner 2019-12-16 11:16:52 UTC

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