-
Notifications
You must be signed in to change notification settings - Fork 181
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
SoapySDR 0.8.2/0.9.0 checklist #405
Comments
Curious to know if this work still ongoing? There's a feature in the SoapyBladeRF module we'd like to use that was merged June 2022, but it seems like 0.8.1 was July 2021(?). |
We're starting to package master in nixpkgs for Python 3.12 compatibility. |
numinit
added a commit
to numinit/nixpkgs
that referenced
this issue
Nov 17, 2024
Instead of applying several patches, just use the latest. The 0.8.2 checklist is mostly done and waiting on a SoapyUHD release, but we already have Python 3.12 in nixpkgs. pothosware/SoapySDR#405 (comment)
13 tasks
github-actions bot
pushed a commit
to NixOS/nixpkgs
that referenced
this issue
Nov 18, 2024
Instead of applying several patches, just use the latest. The 0.8.2 checklist is mostly done and waiting on a SoapyUHD release, but we already have Python 3.12 in nixpkgs. pothosware/SoapySDR#405 (comment) (cherry picked from commit 1d54f76)
jmartindf
pushed a commit
to jmartindf/nixpkgs
that referenced
this issue
Nov 19, 2024
Instead of applying several patches, just use the latest. The 0.8.2 checklist is mostly done and waiting on a SoapyUHD release, but we already have Python 3.12 in nixpkgs. pothosware/SoapySDR#405 (comment) (cherry picked from commit 1d54f76)
paschoal
pushed a commit
to paschoal/nixpkgs
that referenced
this issue
Nov 22, 2024
Instead of applying several patches, just use the latest. The 0.8.2 checklist is mostly done and waiting on a SoapyUHD release, but we already have Python 3.12 in nixpkgs. pothosware/SoapySDR#405 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0.8.2
0.9.0
The text was updated successfully, but these errors were encountered: