-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Ghidra Software Reverse Engineering Suite #1068
Conversation
Queued test build for org.ghidra_sre.Desktop. |
Started test build 5341 |
Build 5341 failed |
It's a valid license, it's not the short name for that license though. I filed: |
Queued test build for org.ghidra_sre.Desktop. |
Started test build 5344 |
Build 5344 successful
|
Queued test build for org.ghidra_sre.Desktop. |
Started test build 5349 |
Build 5349 successful
|
bot, build org.ghidra_sre.Desktop |
Queued test build for org.ghidra_sre.Desktop. |
Started test build 5352 |
Build 5352 successful
|
From the Ghidra install docs: > NOTE: All 32-bit OS installations are now deprecated. Please contact the Ghidra team if you have a specific need. https://ghidra-sre.org/InstallationGuide.html
Queued test build for org.ghidra_sre.Desktop. |
Started test build 5369 |
Build 5369 successful
|
bot, build org.ghidra_sre.Desktop |
Queued test build for org.ghidra_sre.Desktop. |
There now seems to be a PR that adds support for XDG Base Directories: NationalSecurityAgency/ghidra#2529 @hadess Maybe adding this as a patch until it gets merged upstream and new Ghidra version is released could be a good idea? :-) |
We can't add this patch because it's impossible to build Ghidra offline. I guess having $HOME open will have to do. |
That seems to be fixed as Ghidra doesn't create $HOME/ghidra_scripts itself anymore, so it's possible to set another location in the Script Manager. It still create $HOME/.ghidra though. |
bot, build org.ghidra_sre.Desktop |
Queued test build for org.ghidra_sre.Desktop. |
Started test build 38709 |
Build 38709 successful
|
These days we have a checklist for new submissions, but I'm mostly interested if there's an upstream issue about maintaining a flatpak (ignored or not). |
|
bot, build org.ghidra_sre.Ghidra |
Queued test build for org.ghidra_sre.Ghidra. |
Started test build 38915 |
Build 38915 successful
|
/merge |
1 similar comment
/merge |
A repository for this has been created: https://github.com/flathub/org.ghidra_sre.Ghidra You will receive an invitation to be a collaborator which will grant you write access to the repository above. The invite can be also viewed here. If you have never maintained an application before, common questions are answered in the app maintenance guide. Thanks! |
Upstream website
Needs new screenshotsOnly compile-testedextensions need figuring outWould appreciate help from someone who's already used this...
Update: working now, updated todo list
Update 2: ready