Bug 783130 - gnuradio-examples contains outdated examples
Summary: gnuradio-examples contains outdated examples
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnuradio
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Mahut
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 13:45 UTC by Stefan Seefeld
Modified: 2013-02-14 02:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-14 02:04:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stefan Seefeld 2012-01-19 13:45:05 UTC
Description of problem:

example code from gnuradio-examples uses code that is no longer valid. For example, running `python /usr/share/gnuradio/examples/hf_radio/radio.py` yields 

Traceback (most recent call last):
  File "/usr/share/gnuradio/examples/hf_radio/radio.py", line 19, in <module>
    from gnuradio import blks
ImportError: cannot import name blks


It appears the "blks" module was valid in a previous gnuradio version, but is no longer part of gnuradio.

Comment 1 Jaroslav Škarvada 2012-01-20 13:29:07 UTC
It seems not to be easily fixable. It is broken in gnuradio-3.4.2. Upstream rewrote it for gnuradio-3.5, but switched to uhd. I cannot upgrade to gnuradio-3.5 in f16, thus I tried to backport it to gnuradio-3.4.2. But unfortunately I have no testing HW here, please test the experimental build and let me know the results:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3717401

Comment 2 Fedora End Of Life 2013-02-14 02:04:08 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.