Its that time of the year again. I was just thinking about the new ubuntu release this weekend. I’m looking to tag both SoapySDR and Pothos releases (and a bunch of modules). And I thought it would be nice to do that first rather than upload the current release and do it all over again. Theres also gr-osmosdr updates and Limesuite features to get out.
@csete How do you feel about starting to go after this w/ me? I was thinking about the following:
upload any dependencies like misc sdr drivers
upload soapysdr and modules to 0.6 ABI
tag and upload limesuite as well
backport gnuradio/rebuild gr-osmosdr
Any idea which packages we need for 1) on this latest release to stay up to date? After that I can probably take care of 2) and 3) by this weekend. And we should be able to split up 4) and some other gr-packages at that point.
Looks like current releases are 17.04, 16.04 (LTS), and 14.04 (LTS). 16.10 is nearly EOL and not worth updating IMHO. I was also thinking about not updating 14.04 (LTS) trusty since we already have the newer LTS 16.04. One recent LTS ubuntu is probably good enough for most people. Interested to hear any thoughts on that though.
I see no need to update drivers unless we want to switch to the alternate librtlsdr. I have not tested it, so I don’t have any opinion about it. I’m fine with either.
I will update gr-osmosdr when it is time. My earlier patches are now merged upstream, however, I have got a new patch that fixes rtl_tcp but we should probably wait with that.
I’m fine with gnuradio 3.7.10 that comes with the OS, but you are welcome to upload 3.7.10.1 if you wish. I guess it makes sense to have the same gnuradio on all versions.
Shouldn’t we at least try updating 14.04 and 16.10? I guess it is only soapysdr and gr-osmosdr that needs updating here, perhaps also limesuite.
I upgraded to the latest AMD 8 core cpu, motherboard and a Nvidia 1250 Cuda Core videocard. It won’t run on Ubuntu 16.anything because of the hardware. Windows 7 won’t touch it. It’s Ubuntu 17.04 and Windows 10 or it won’t go. For now, Ubuntu 17.04 or nothing.
Correction: Ubuntu 17.04 already has 3.7.10.1 and I suggest we stick to that. We can backport newer versions when they become available in Debian unstable.
@joshblum I assume you will let me know when SoapySDR and Limesuite is done?
Unfortunately, that’s not possible without disabling those drivers, although we will probably have to disable UHD support since I am not aware any fixes for the known crash in gr-osmosdr.
I had a lot of repositories to tag. Thats done. I’m going to start uploading packages and working around any issues that come up, pardon my dust. Some repos may be in disarray until this is over.
I will see what happens when I backport gnuradio stuff. I guess its just a matter of scripting to handle the other releases. I just dont like the idea of 4 ubuntu releases to build for. Its just laziness, but I think it should just be current release + latest LTS release
I wrongly assumed that there was at least some package update in 17.04 to backport. I just looked into it. Sorry nevermind.
Though… technically gnuradio (gr-uhd) should be rebuilt to match the UHD from the ettus ppa. Although the gr-osmosdr package just wraps the gr-uhd blocks, it also includes uhd headers and probably links with it. I think they both need rebuilding, but If I recall that might not address the segfault.
Thats done. I’m going to start uploading packages and working around any issues that come up, pardon my dust. Some repos may be in disarray until this is over.