| Summary: | radare2, portable reverse engineering framework and toolset | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Anton Kochkov <anton.kochkov> |
| Component: | New RPM package request | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | geiger.david68210, guichard.adrien, luigiwalser, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://radare.org | ||
| Whiteboard: | |||
| Source RPM: | radare2 | CVE: | |
| Status comment: | |||
| Attachments: | WiP radare.spec | ||
|
Description
Anton Kochkov
2018-05-20 04:55:27 CEST
That looks good :-) Assigning this package request to all packagers collectively. On a voluntary basis, one of them might, if there are no license or other legal issues, want to integrate it to the distribution and maintain it for bug and security fixes. You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager Severity:
normal =>
enhancement Created attachment 10176 [details]
WiP radare.spec
Here is a "work in progress" spec file.
There is one issue, binary depends on "*.so" files, instead of "*.so.2.6.0-git" files. Hence, we are obliged to install devel package.CC:
(none) =>
guichard.adrien package radare2 now imported on Cauldron! http://svnweb.mageia.org/packages?view=revision&revision=1230585 CC:
(none) =>
geiger.david68210 and now package radare2-cutter also imported to Cauldron. radare2 2.6.0 was released yesterday with many fixes/improvements: https://github.com/radare/radare2/releases/tag/2.6.0 (In reply to Anton Kochkov from comment #5) > radare2 2.6.0 was released yesterday with many fixes/improvements: > https://github.com/radare/radare2/releases/tag/2.6.0 Hmmmm! unfortablely it fails to build: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20180522044401.daviddavid.duvel.11132/log/radare2-2.6.0-1.mga7/build.0.20180522044506.log So this was fixed. Will be part of 2.7.0 release in ~2 weeks. Marking as FIXED as the package was imported. Opening new bug for security issue(s) fixed in 2.6.0. Status:
NEW =>
RESOLVED |