Bug 1505641
| Summary: | nothing provides libtomcrypt.so.0()(64bit) needed by python2-crypto-2.6.1-17.fc27.s390x | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Randy Barlow <randy> |
| Component: | libtomcrypt | Assignee: | Simone Caronni <negativo17> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | jeremy, negativo17, pcahyna |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-10-26 10:02:35 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
Randy Barlow
2017-10-24 03:45:42 UTC
I've triggered a rebuild and an update of libtomcrypt yesterday, but this seems unrelated. The current libtomcrypt package is still in the repository: https://koji.fedoraproject.org/koji/buildinfo?buildID=928909 It seems the buildroot is getting the wrong packages. By pulling the udpates that I just pushed I can't reproduce the problem: https://bodhi.fedoraproject.org/updates/FEDORA-2017-53fedf1c92 $ sudo rpm -Uvh \ https://kojipkgs.fedoraproject.org//packages/libtomcrypt/1.18.0/1.fc27/x86_64/libtomcrypt-1.18.0-1.fc27.x86_64.rpm \ https://kojipkgs.fedoraproject.org//packages/python-crypto/2.6.1/19.fc27/x86_64/python2-crypto-2.6.1-19.fc27.x86_64.rpm I think you may be correct, as I am able to install python2-crypto in a container: $ sudo docker run --rm registry.fedoraproject.org/fedora:27 dnf install python2-crypto -y I've reported it to releng to ask if they know what is going on: https://pagure.io/releng/issue/7110 Ok, as explained by Igor, in the end the issue was that the rebuild was pulling in the override I created on libtomcrypt and of course there was no python-crypto override, as no one had the need for it. The override has expired, so whether the update goes to stable or not it does not matter as the dependencies are satisfied in both cases. Closing this ticket. |