Page MenuHomeSolus

[GNU Radio]
Closed, ResolvedPublic

Assigned To
Authored By
Jan 19 2018, 1:15 PM
Referenced Files
F6100983: gnuradio.yml
Jun 29 2020, 7:05 PM
F6100984: pspec_x86_64.xml
Jun 29 2020, 7:05 PM
F6100896: gnuradio.yml
Jun 29 2020, 6:08 PM
F6100898: pspec_x86_64.xml
Jun 29 2020, 6:08 PM
F6098114: package.yml
Jun 28 2020, 11:59 AM
F3348071: package.yml
May 7 2018, 4:45 PM
"Like" token, awarded by stigarn.


Name: GNU Radio
Motivation: It is a platform for teaching, simulating and experimenting on signal processing and wireless networks. It provides a SDK for software radios defined radios.
Open Source: Yes
Tarball: (Github releases are easier to track)

Revisions and Commits

Related Objects

Event Timeline

DataDrake updated the task description. (Show Details)
DataDrake moved this task from Backlog to Accepted For Inclusion on the Package Requests board.

I contacted the gnuradio IRC channel. They are changing their development model, and porting the application to Python3 and Qt5. This is not something that will happen soon though, as these updates are not coming before version, that is, by the end of the year.
What should I do @DataDrake? Can I package it or should I wait for the newer version? I want you to know that wx-based GUI has been deprecated so it may have issues or missing features, so this is not a real workaround.

There ;-)

Yeah, let's wait for the Qt5 release. I know it sucks, but I'd rather not ship broken software.

Please allow me to upload my current package.yml in order not to redo useless work in future ?

I was trying to learn how to package applications for Solus and I ended up creating a package for Volk, a library used to optimise GNU Radio

GR's feature freeze is on 10 January 2019. v3.8 will likely be out by the end of that month.

According to my knowledge, August is not in Fall, but yeah we have a release :P

When people use seasons as release dates GRRR. Seasons are not global!

livingsilver94 added a subscriber: livingsilver94.

Leaving as the assignee because yes I can package it, but I couldn't maintain it.

I was able to create a working build file, and i would like to maintain gnuradio for further updates, BUT i have no experience.


Few tips, take a look at how other package.xml are structured. The release tag is the current published version in the Solus repos, as it doesn't exist yet, this should be 1.

If a -devel package has a package config, you should use this instead. You can find this out by using eopkg info <devel package name> ie eopkg info qt5-base-devel you would use pkgconfig(Qt5Core)

Libraries used at build time are linked (see pspec_x86_64.xml and abi_used_libs) If listed there, there is no need to include them in rundep

I don't understand how your package.yml worked :/

Any-ways, I built it locally, but can't see how to test it and my internet has been driving me crazy, so I gave up on it. I uploaded the packaging to gitlab, as it might be useful to someone.


The yml works fine for me with solbuild (i dont use unstable). I updated it to use pkgconfig as often as possible.

There are runtimedeps needed, as there are some dependencies, which are not needed in built-time, but in runtime.

here is the updated yml and the pspec file.

Also, pkgconfig always come first in the list and ordered alphabetical.

license, summary, component, description tags usually come after the source tag and before builddeps. See for the structure.

Also the licence needs to be from the following list - so should be either GPL-3.0-only or GPL-3.0-or-later depending on what is applicable.

The yml works fine for me with solbuild (i dont use unstable). I updated it to use pkgconfig as often as possible.

Odd it failed for me with [BuildDep] Unknown build deps: python3-gobject

Ah, they were merged , please update the build dep to python-gobject

This comment was removed by JoshStrobl.

Removed uploaded files. Please submit a patch following the appropriate method documented on our Help Center, should you be interested in becoming the maintainer for this.