-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
gradle: 8.10.2 -> 8.12 #356109
base: master
Are you sure you want to change the base?
gradle: 8.10.2 -> 8.12 #356109
Conversation
# Gradle’s .0 releases are tagged as `vX.Y.0`, but the actual | ||
# release version omits the `.0`, so we’ll wanto to only capture | ||
# the version up but not including the the trailing `.0`. | ||
"--version-regex=^v(\\d+\\.\\d+(?:\\.[1-9]\\d?)?)(\\.0)?$" |
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.
Right now this’ll cause nix-update to crash, but I’ll open an issue.
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.
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.
I'm not sure how to feel about including this flag while it's broken in upstream nix-update. Maybe we should comment it out and/or add it once it's fixed upstream?
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.
Sure, commented out.
jadx fails to build (succeeds on master)
|
@FliegendeWurst thanks. It looks like since the MITM cache in #272380 we (may) have to run dependency update for Gradle-built packages. I’ll run the updates and add refreshed |
Each version of Gradle bundles different versions of various embedded stuff. There's not too much documentation on this, but from what I can tell the Kotlin DSL version is set here. It's further used here in code generation. Then, at build time, if the version doesn't match the hardcoded version, it may issue a warning here, but I don't see why it can't be overridden in theory. Since this hardcoded version is likely possible to override, it's also possible to extend the Gradle build scripts to look for whatever Kotlin DSL plugin is in the cache and use that. Howver, Gradle docs say:
I don't actually think the old FOD-style derivations would've avoided this issue, it seems unrelated to mitm-cache, but maybe Gradle has some weird logic where if a repo is local it uses whatever version is available instead of whatever version is set. |
Result of 1 package marked as broken and skipped:
5 packages failed to build:
49 packages built:
|
All of those build failures are already known: |
|
that's a lot of build failures, was there a breaking change in Gradle? |
|
Ghidra build fails at |
Gradle release 8.12
Turns out the update script couldn’t deal with an update to .0. Even though the tag is
v8.11.0
the actual version number is8.11
.Fixes #355951.
Incorporates changes from #364871.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.