Bug 1366041 - libcrypt conflicts with libcrypt-nss
Summary: libcrypt conflicts with libcrypt-nss
Keywords:
Status: CLOSED DUPLICATE of bug 1360781
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 25
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-10 21:03 UTC by David Vásquez
Modified: 2016-08-10 21:26 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-10 21:26:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Vásquez 2016-08-10 21:03:04 UTC
Description of problem:
Using "mock" , the chroot failed when it tries install libcrypto-nss

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

libcrypt-2.24-1  and libcrypt-nss-2.24-1


How reproducible:

mock -r fedora-25-x86_64 foo.src.rpm

Steps to Reproduce:
1. mock --init fedora-25-x86_64
2. mock -r fedora-25-x86_64 foo.src.rpm
3.

Actual results:

Error: libcrypt-nss conflicts with libcrypt-2.24-1.fc25.x86_64
 You could try using --skip-broken to work around the problem
Error: libcrypt conflicts with libcrypt-nss-2.24-1.fc25.x86_64
 You could try running: rpm -Va --nofiles --nodigest
ERROR: Exception(/home/makerpm/rpmbuild/SRPMS/opera-39.0.2256.48-1.fc24.src.rpm) Config(fedora-25-x86_64) 6 minutes 48 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-25-x86_64/result
ERROR: Command failed. See logs for output.
 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-25-x86_64/root/ --releasever 25 install @buildsys-build



Expected results:

a simple done...

Additional info:
complete log here
https://da.gd/ebrP

Comment 1 Carlos O'Donell 2016-08-10 21:26:11 UTC
Your log shows you are using yum to construct the chroot, so this is most likely bug 1360781. The related bug is 1324623.

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


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