-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
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.
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.
The nix-update issue got fixed in the meantime, so restored the flag.
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: |
I've build and linked the gradle package from this PR locally and verified I can build projects, so from that PoV this change is good. I've also noticed that this upgrade fixes gradle/gradle#32006, so we should merge it rather sooner than later. In order to fix the console issue above I had to remove |
|
|
gotenberg does not depend on gradle. It's Go application:
So I think we're fine to merge this. |
Forget what I said, gotenberg depends on gradle transitively via pdftk. |
I built pdftk and gotenberg both on my machine without problems. |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-24.11
git worktree add -d .worktree/backport-356109-to-release-24.11 origin/release-24.11
cd .worktree/backport-356109-to-release-24.11
git switch --create backport-356109-to-release-24.11
git cherry-pick -x 9ca9394a64f76ec0eedb37ba20407a6e78afe23d 6082098609b0c9ef65939c5e64523043a69a7947 29503f955b8e94ce97824a20192484eb10e6f1ff 779b6255fd6e477290b9bd3e3956bfe79d60d7a9 cd6a44e1b73455c5abe91482e57e10609853c904 a3b161e1f6aef25df3ae51a5f9eee8fc338fd011 eb43df3e281f05d50107e5771a3b1ddc47bb62e6 f26a825e8bba322f0862e2cd4c6f86d548637e97 abf3eaf9337a04b5cadd960fa9f9936b43123b76 |
@FliegendeWurst I suspect the backport failed because this PR included a reformat commit. |
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.