Hi,
I’m attempting to run gr-sounder on Ubuntu 9.04, using the 3.2 release
from
the Ubuntu gnuradio repository. The core gnuradio packages seem to work
fine, but when I run usrp_sounder.py, I get an error indicating that the
sounder module cannot be imported. Cross-checking against an
installation on
another machine (compiled from source), I see that gr-sounder includes a
file called sounder.py, which is not present in the Ubuntu repository
install. Out of curiosity, I tired running the gr-radar-mono, but got a
similar import error. Any ideas?
Jordan
On Wed, Jul 8, 2009 at 13:44, Jordan J Riggs[email protected] wrote:
I’m attempting to run gr-sounder on Ubuntu 9.04, using the 3.2 release from
the Ubuntu gnuradio repository. The core gnuradio packages seem to work
fine, but when I run usrp_sounder.py, I get an error indicating that the
sounder module cannot be imported. Cross-checking against an installation on
another machine (compiled from source), I see that gr-sounder includes a
file called sounder.py, which is not present in the Ubuntu repository
install. Out of curiosity, I tired running the gr-radar-mono, but got a
similar import error. Any ideas?
This is a packaging bug, thanks for the report.
The gr-radar-mono missing file issue is already fixed in package
version 3.2.1-1. You should use apt-get or the Update Manager app to
upgrade.
The gr-sounder missing file issue you are reporting has a similar
cause, and will be fixed for package version 3.2.1-2, in the next day
or so.
Johnathan
Johnathan C. wrote:
similar import error. Any ideas?
or so.
Johnathan
Discuss-gnuradio mailing list
[email protected]
Discuss-gnuradio Info Page
Seems like the tunnel.py script under /digital/ also doesn’t work after
the update. The set frequency option is no longer available. Any ideas?
On Thu, Jul 9, 2009 at 10:02, Qi Chen[email protected] wrote:
Seems like the tunnel.py script under /digital/ also doesn’t work after the
update. The set frequency option is no longer available. Any ideas?
Actually, this isn’t a packaging bug, it’s in the current trunk and
the 3.2.1 release.
Unfortunately, to fix it, we’ll need to issue a 3.2.2 release. I’ll
post a note to the list when we have a handle on it.
Johnathan