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 1965916 - Update of libreswan-4.3-1.fc33.x86_64 fails because of ldns
Summary: Update of libreswan-4.3-1.fc33.x86_64 fails because of ldns
Keywords:
Status: CLOSED DUPLICATE of bug 1965758
Alias: None
Product: Fedora
Classification: Fedora
Component: libreswan
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-31 06:37 UTC by A. Galama
Modified: 2021-05-31 17:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-31 17:57:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description A. Galama 2021-05-31 06:37:30 UTC 
Description of problem:

I was trying to upgrade from Fedora 33 to 34 but "dnf upgrade --refresh" gives the error message "package libreswan-4.3-1.fc33.x86_64 requires libldns.so.2()(64bit), but none of the providers can be installed"

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

libreswan-4.3-1.fc33.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. dnf upgrade --refresh

Actual results:

 Problem: package libreswan-4.3-1.fc33.x86_64 requires libldns.so.2()(64bit), but none of the providers can be installed
  - cannot install both ldns-1.7.1-4.fc33.x86_64 and ldns-1.7.0-32.fc33.x86_64
  - cannot install the best update candidate for package libreswan-4.3-1.fc33.x86_64
  - cannot install the best update candidate for package ldns-1.7.0-32.fc33.x86_64

Expected results:

Update to 4.3-1
Comment 1 Paul Wouters 2021-05-31 17:57:12 UTC 

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