-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
uhd: 4.6.0.0 -> 4.7.0.0 #349079
uhd: 4.6.0.0 -> 4.7.0.0 #349079
Conversation
Results of
|
Result of 18 packages failed to build:
21 packages built:
|
Ugh, looks like many packages are broken already on master branch. |
Thanks for the confirmation! This is quite worrying given how close we are to 24.11. |
@ofborg build gnuradio3_8 |
d746f5c
to
1ca5a6e
Compare
OK as for Gnuradio 3.10, I'm optimistic that if me and/or @LunNova will fix As for ofborg's build timing out for GR 3.8, it also continues on forever locally, so I disabled the tests completely. Let's see it is fixed now: @ofborg build gnuradio3_8 |
pyqt6 should be building again: #348697 |
Failing eval for me with nixpkgs-review:
|
1ca5a6e
to
331482e
Compare
@ofborg build gnuradio |
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.
OK CI is green for gnuradio
except for x86_64-darwin
in which it times out; I'm optimistic it won't be an issue on Hydra. For gnuradio3_8
it is fully green, and I also checked locally gnuradio3_8Packages.{osmo,lime}sdr
and they are OK.
Diff LGTM.
Can be merged if there are no objections if you ask me. |
@ofborg build soapysdr |
|
@ofborg build soapysdr-with-plugins |
python312Packages.soapysdr-with-plugins is failing, but it's failing on master in the same way so nvm |
It looks to me that it doesn't fail here.. |
@ofborg build python312Packages.soapysdr-with-plugins |
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 2 failed packages were failing before.
nixpkgs-review
result
Generated using nixpkgs-review
.
Command: nixpkgs-review pr 349079
x86_64-linux
❌ 2 packages failed to build:
- abracadabra
- python312Packages.soapysdr-with-plugins
✅ 38 packages built:
- cubicsdr
- dump1090
- gnss-sdr
- gnuradio
- gnuradio3_8
- gnuradio3_8Minimal
- gnuradio3_8Packages.ais
- gnuradio3_8Packages.grnet
- gnuradio3_8Packages.limesdr
- gnuradio3_8Packages.osmosdr
- gnuradio3_8Packages.osmosdr.dev
- gnuradio3_8Packages.rds
- gnuradioMinimal
- gnuradioPackages.osmosdr
- gnuradioPackages.osmosdr.dev
- gqrx
- gqrx-gr-audio
- gqrx-portaudio
- inspectrum
- openwebrx
- openwebrx.dist
- pothos
- python311Packages.soapysdr-with-plugins
- qradiolink
- rtl_433
- sdrangel
- sdrpp
- sigdigger
- soapysdr-with-plugins
- soapyuhd
- srsran
- suscan
- swig3
- uhd
- uhd.dev
- uhdMinimal
- uhdMinimal.dev
- welle-io
cc @bcdarwin Would have been good to get a ping about the reintroduction of an old SWIG version as we have been specifically trying to cut down on them. SInce the latest GNU Radio uses SWIG 4 I imagine it should not be too difficult to backport whatever change made that possible. |
I am the one who reintroduced the old swig 3 derivation. The diff between GR 3.10 and 3.8 is so big that I doubt it would be easy enough even for someone with swig experience to perform such a backport. However, I'd be happy to review such a PR removing swig3. |
FWIW, it also means another package requiring the end‐of‐life, not‐updated‐in‐three‐years original PCRE library (#356387); Debian has already removed PCRE entirely as of last year’s stable release, and they removed SWIG 3 in 2021. I think at the very least we’d want to backport PCRE2 support from SWIG 4, but I don’t feel great about reintroducing it at all – Gforth’s modified SWIG 3 fork was bad enough but at least that’s more contained and not something other packages can depend on. This seems like another instance of “exceptions to our normal practice of not carrying multiple old versions of packages leading to knock‐on maintenance effects throughout the tree that eventually bottoms out in keeping around something that’s EOL/a security risk” – can I ask why we package GNU Radio 3.8 at all? It seems like 3.9 was released almost four years ago and 3.8 hasn’t had an update since 2022; should we really be shipping 24.11 with it at all? (Also, it seems like GNU Radio 3.9 just moved off SWIG entirely and our |
OK I see, this is very convincing.I just checked, and
Perhaps an issue in upstream's bug tracker should be opened.
Although we use Anyway, I opened #356976 as a draft to suggest the removal of GR 3.8 along with swig3. Marked as a draft at the moment due to the error above of qradiolink, and also seeking in general @markuskowa's approval. |
Thank you for looking into this :) FWIW, it’s not super urgent to resolve this especially as the Gforth fork is a problem on its own in terms of PCRE, and SWIG is (hopefully!) not getting exposed to untrusted user input anyway, but I do just want to make sure we’re moving forward rather than backwards on this. |
https://github.com/EttusResearch/uhd/releases/tag/v4.7.0.0
There are additional tests included by upstream in this release, causing the patch file to no longer be valid. I have fixed that together in this update.
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.