-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
volk: 3.0.0 -> 3.1.2 #330477
volk: 3.0.0 -> 3.1.2 #330477
Conversation
FWIW I built
|
That's not the same thing - now the expression is very different - it is not even located in the same place and it, and it doesn't build the same sources.
Yea I should have recommended to you to wait a bit for ofborg to finish evaluation here so that you won't run it locally. See the ofborg (first) feature explained here. ofborg just finished evaluating attributes here, so respawning |
Result of 1 package failed to build:
20 packages built:
|
Result of 14 packages failed to build:
15 packages built:
|
Hmm very peculiar ... The I pushed a few more commits for to these attributes. If @tie you'd be kind enough to run a |
|
Thanks. At least this error will be fixed now. (will recheck ofborg once more in a while). |
Evaluation finished successfully. Now running nixpkgs-review locally on an |
Result of 25 packages built:
|
Result of 1 package marked as broken and skipped:
6 packages failed to build:
10 packages built:
|
Thanks for the quick report! Could you share please the build logs of |
Result of 24 packages built:
|
Had to run with |
Thanks @tko :). This build log I am afraid indicates that for GR 3.8 there is no choice but to go back to volk2, for all platforms. I've found for it an alternative build solution - using Python 3.11 (like GR 3.8 uses), as it still supports the deprecated If in an hour or two (after ofborg evaluation finishes) you'd be able to run a |
Result of 1 package marked as broken and skipped:
2 packages failed to build:
14 packages built:
The build error looks to have been
|
Thanks again for the report @tko. Maybe an update to I will give a few days for the maintainers of both packages (@polygon and @oxapentane) to respond to this |
@ofborg build sigdigger |
I see same error from
|
OK I found out that the suscan update wasn't really an update - upstream only decided to tag the same revision that we used as v0.3.0 . Makes the expression nicer, but of course it won't solve the zlib issue. I fixed the expression to use I'll give a few days for the maintainers of |
Encounteres an error gnuradio3_8 also experiences when volkExternal == volk (3.1.2).
OK suscan was broken apparently on all platforms - I missed that because my branch wasn't rebased upon latest |
Based on the expression deleted in a previous commit, use this expression in an upcoming commit for gnuradio3_8{,Minimal}.
Nothing really changed, only upstream tagged the same commit as v0.3.0, see: BatchDrake/suscan@37dad54...v0.3.0
Description of changes
Things done
nix.conf
? (See Nix manual)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.