navidrome: 0.60.0 -> 0.60.3#488091
Conversation
srcbot: Full Evaluation Results for PR #488091compared base commit Commandtarget/release/srcbot verify \
--full-eval \
--prs 488091 \
--aggressively-check-fods true \
--nixpkgs /home/jrestivo/dev/nixpkgs \
--remote-builder jrestivo@100.104.74.94 \
--remote-system aarch64-linux \
--remote-build-jobs 2 \
--build-jobs 2 \
--eval-workers 1 \
--false-positive \
--verify-full-drvs \
--save-location /srv/srcbot \
--log-base-url https://nixos-arm.tail5ca7.ts.net/srcbot-srv/ \
--remote-gc-threshold 180G \
--remote-gc-keep-days 1Status: 4/4 packages passed, 0 failed across 2 architectures x86_64-linux2 packages passed (all with tests)
aarch64-linuxTest Failures - 1 packages with failing tests
|
|
The failing test is (again) a false positive because the runner doesn't have kvm. |
|
0.60.3 was released. |
451a7d7 to
9f116f6
Compare
|
I tried to install Navidrome version 0.60.3 from this pull request using an overlay, but got the following error: This is the same error as I get with version 0.59.0, the version from nixpgs stable. The error is detailed in #481611 and seems related to the version of golang. In other words, it doesn't create a new error, but neither does it fix the existing one. |
|
@cimm isn't the default version of golang in 25.11 different from the default in unstable? If so the fact that this uses |
|
+1 I just wanted to add: I've been daily driving 0.60.2 and now 0.60.3 (as an overlay that's the same hashes as this PR). It's not 100% the same (I'm running a few of the new wasm plugins) and I'm not on stable. But just as some empirical data--I think this should reproducibly work on master. |
|
@tebriel You're absolutely right! I forgot I wasn't running unstable. I gave it another shot on unstable, and it works as expected. Sorry about the confusion! |
|
will this get backported to stable once merged? stable is still on 0.59.0 which fails to build, or is it not possible due to the golang version used by default in stable? |
|
@coyotoid I think we'd only backport it if there were security issues.
Are you saying that 0.59.0 is broken in stable or that's just the last version that works in stable? You could use a combination of disabledModules and |
|
@tebriel I see, wrt backports.
It's broken in stable. |
|
#481611 is the issue about the build failure on stable. Yeah I think this should be backported to fix that failure. |
|
I'm not sure backporting this change will fix stable 👀 |
|
@not-my-profile @coyotoid try out #493362 for release-25.11 build issues. |
|
|
#493362 fixes the build above (also needed on unstable now). |
9f116f6 to
7deb465
Compare
|
@andresilva rebased on upstream, validated the error, added the patch and validated the fix. |
|
|
LGTM will merge once you update that comment. We can then backport this and replace #493362. |
7deb465 to
1a13ff7
Compare
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-25.11
git worktree add -d .worktree/backport-488091-to-release-25.11 origin/release-25.11
cd .worktree/backport-488091-to-release-25.11
git switch --create backport-488091-to-release-25.11
git cherry-pick -x 1a13ff7aaa65cee4271854cfb41f01f006b20864 |
|
Backport will need the module changes as well. |
changelog: https://github.com/navidrome/navidrome/releases/tag/v0.60.3
changelog: https://github.com/navidrome/navidrome/releases/tag/v0.60.2
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.