Bug 994505
| Summary: | New version request | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Meng <i> |
| Component: | libtommath | Assignee: | Simone Caronni <negativo17> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | rawhide | CC: | negativo17 |
| Target Milestone: | --- | Flags: | negativo17:
needinfo+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libtommath-0.42.0-2.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-18 21:30:07 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 615088 | ||
|
Description
Christopher Meng
2013-08-07 12:18:11 UTC
libtommath has been built, waiting on another component and will push updates for all branches. libtommath-0.42.0-2.el6,libtomcrypt-1.17-20.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/libtommath-0.42.0-2.el6,libtomcrypt-1.17-20.el6 libtommath-0.42.0-2.fc18,libtomcrypt-1.17-20.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/libtommath-0.42.0-2.fc18,libtomcrypt-1.17-20.fc18 libtommath-0.42.0-2.fc19,libtomcrypt-1.17-20.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libtommath-0.42.0-2.fc19,libtomcrypt-1.17-20.fc19 Yeah, if you can change stable karma to 1 I can push them to stable today. But you didn't. Can you test all branches? I can test f19 and el6. dropbear need its latest version, which was released almost 3 years ago. I tihnk there should have no problem. Package libtommath-0.42.0-2.fc19, libtomcrypt-1.17-20.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libtommath-0.42.0-2.fc19 libtomcrypt-1.17-20.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14482/libtommath-0.42.0-2.fc19,libtomcrypt-1.17-20.fc19 then log in and leave karma (feedback). Hi, I don't know how you installed the headers, comparing with Debian I found this library has different location. http://pkgs.org/debian-sid/debian-main-amd64/libtommath-dev_0.42.0-1_amd64.deb.html http://pkgs.org/fedora-rawhide/fedora-i386/libtommath-devel-0.42.0-2.fc20.i686.rpm.html And because dropbear author develops software under non-Fedora OS, and since this library is not used by any other softwares in Fedora, will you change the location? If not I will write patches again... (In reply to Christopher Meng from comment #9) > And because dropbear author develops software under non-Fedora OS, and since > this library is not used by any other softwares in Fedora, will you change > the location? I inherited ownership of the working package a couple of months ago so I did not made any bug change to it. I don't see any problem in this, I just need to simplify the spec file; both tommath and tomcrypt have very specific prefixes in header files. (In reply to Simone Caronni from comment #10) > not made any bug change to it. *big* change, sorry. libtommath-0.42.0-2.fc18, libtomcrypt-1.17-20.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. libtommath-0.42.0-2.fc19, libtomcrypt-1.17-20.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. libtommath-0.42.0-2.el6, libtomcrypt-1.17-20.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |