-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
metasploit: 4.16.1 -> 5.0.1 #54405
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
metasploit: 4.16.1 -> 5.0.1 #54405
Conversation
@GrahamcOfBorg build metasploit |
At some point since this PR, this expression started failing to build on my workstations, as the hash of "metasploit-framework" in gemset.nix has changed. Since this is being pulled from git, I am unsure why this is. I originally followed the instructions from "default.nix" when updating, and stripped the dependencies from gemset.nix accordingly. However, since the expression for version 4.16.1 does not seem to strip these dependencies, this is my suspect. I have rebuilt gemset.nix with dependencies included, to match the previous version of the package, and I have updated the comments in default.nix to match. |
@GrahamcOfBorg build metasploit |
The build failed for me on NixOS:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Get it to build
@buckley310 They may be able to help you with this. |
Thanks. the issue I am running into is that the hash for "metasploit-framework" in "gemset.nix" keeps changing. It has done so twice now. I am not sure why this is, or how to proceed. |
The |
This package is, once again, building properly. The files that are not auto-generated now reference a specific revision, rather than a git tag. |
@GrahamcOfBorg build metasploit |
Well darn, it still doesn't build.
|
I ran a GC on my machine and updated the hash again, in case this was some kind of stale cache issue on my PC. At this point I expect it to break again, but you never know. If it breaks again, it may make sense to redo the PR with a newer version anyway, preferably after root-causing this. |
Yeah, at this point I'm really not sure what could cause this. |
Yep, broken again. |
It looks like whatever is pulling down the git repo is doing it wrong. Check this out, release 4.17.44 is newer than 5.0.1.
|
The hash has changed again. I saved the derivation from before, and indeed, the contents of the |
What changed? |
This is a diff between a backup from a few days ago, and how it builds now.
|
Only thing I can suggest here is having a look at the contents of the packfiles with git-verify-pack to see if you can figure out what's changed.
|
The git data actually knows about newer branches than 5.0.1. |
The git data actually knows about newer branches than 5.0.1.
Perhaps using the --single-branch argument to git clone would help.
|
So, I looked into the issue again, and have a potential fix at nix-community/bundix#51 |
Not working on my machine :\ blunder seems to require ".git" to exist currently. |
This request isn't going anywhere, I do not have the knowledge to debug the build system, and this version is outdated anyhow. |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)