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 1893469 - nspr in rawhide fails with dependencies for nspr-devel
Summary: nspr in rawhide fails with dependencies for nspr-devel
Keywords:
Status: CLOSED DUPLICATE of bug 1892874
Alias: None
Product: Fedora
Classification: Fedora
Component: nspr
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-31 20:22 UTC by Michal Jaegermann
Modified: 2020-11-02 07:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-02 07:39:51 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Michal Jaegermann 2020-10-31 20:22:57 UTC 
Description of problem:

In rawhide updating nspr together with nspr-devel fails in the following way:

 Problem: package nspr-devel-4.29.0-1.fc34.x86_64 requires nspr = 4.29.0-1.fc34, but none of the providers can be installed
  - cannot install both nspr-4.29.0-2.fc34.x86_64 and nspr-4.29.0-1.fc34.x86_64
  - problem with installed package nspr-devel-4.29.0-1.fc34.x86_64
  - cannot install the best update candidate for package nspr-4.29.0-1.fc34.x86_64
  - nothing provides nspr = 4.29.0-2 needed by nspr-devel-4.29.0-2.fc34.x86_64


Version-Release number of selected component (if applicable):
nspr-4.29.0-2.fc34

How reproducible:
always

Steps to Reproduce:
Try to update

Additional info:
Removing nspr-devel, which breaks dependencies for other '-devel' packages, allows to update nspr to 4.29.0-2 without an undue fuss.
Comment 1 Daiki Ueno 2020-11-02 07:39:51 UTC 
Thank you for the report. It should be fixed in the next compose, which should have 4.29.0-7 (see bug 1892874 for the details).

*** This bug has been marked as a duplicate of bug 1892874 ***
Note You need to log in before you can comment on or make changes to this bug.