Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED] In 5.2.0 release the list of RIO is empty #37

Closed
xambroz opened this issue Apr 17, 2021 · 5 comments
Closed

[FIXED] In 5.2.0 release the list of RIO is empty #37

xambroz opened this issue Apr 17, 2021 · 5 comments
Assignees

Comments

@xambroz
Copy link
Contributor

xambroz commented Apr 17, 2021

Environment Details

# copypaste this script into your shell and replace it with the output
iaito -v
date
r2 -v
uname -ms

iaito -v
QCommandLineParser: already having an option named "w"
iaito 0.1.0
date
2021-04-17T04:36:42 CEST
r2 -v
radare2 5.2.0 0 @ linux-x86-64 git.5.2.0
commit: unknown build: 2021-04-16__00:49:31
uname -ms
Linux x86_64

Description

In the release 5.2.0 the list of RIO plugins is empty.

Screenshot from 2021-04-17 04-34-36

As a result even the file select dialogue is not displaying any other means accessing data then "file://".

@trufae
Copy link
Collaborator

trufae commented Apr 17, 2021

Please dont fill issues for the releases. Just do it for git. And yes ;this one is also in my list to be fixed for 5.2.1. Its not fixed in git yet

thanks

@trufae trufae self-assigned this Apr 17, 2021
@trufae
Copy link
Collaborator

trufae commented Apr 17, 2021

Fixed in 14afa87 will be available in 5.2.1

@trufae trufae changed the title In 5.2.0 release the list of RIO is empty [FIXED] In 5.2.0 release the list of RIO is empty Apr 17, 2021
@trufae
Copy link
Collaborator

trufae commented Apr 18, 2021

im fine to keep issues open if they are fixed in git but not in the last release. prefixing the issue title with [FIXED] or [5.2.0] or whatever makes it visually less disturbing to me. we can use labels for that, but the title (or using emojis) is visually nicer i think

@xambroz
Copy link
Contributor Author

xambroz commented Apr 21, 2021

Hello pancake ... once there is a fix in a form of commit/PR or new release we can close, no need to keep it open.
I can cherrypick the commit/PR for backporting to the release package.

@xambroz xambroz closed this as completed Apr 21, 2021
@trufae
Copy link
Collaborator

trufae commented Apr 21, 2021

Ill telease this week. Dont spend time backportint all the patches :p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants