Marcus, I'll see if I can get our IT people's ear and figure out better what is going on with sudo. It was indeed just a vanilla install of 16.04, and then IT did there mucking afterwards.


On 10/12/2016 03:55 PM, Marcus Müller wrote:

Hi Jason,

I can see that sudo pecularities might break pybombs; however, replacing sudo with a script is a rather uncommon practice (you incurr a lot of problems, because scripts usually can't have the setuid bit etc); is that vanilla ubuntu 16.04 or what's happened there?

Best regards,


On 12.10.2016 19:12, Jason Matusiak wrote:
Hi Nick!
I did.  When I run it I get:
Requirement already up-to-date: setuptools in /usr/local/lib/python2.7/dist-packages

I am not on a thin client, I am on a fresh load of 16.04 on an actual PC. I do believe that sudo isn't actually sudo, but a script. That said, I wasn't having sudo issues before I reloaded my machine (which was running 14.04).


On 10/12/2016 01:04 PM, Nicholas McCarthy wrote:
Jason, did you try
pip install --upgrade setuptools

as a first step? Are you running on a special setup such as a patchwork virtual machine being served to you on a thinclient with f**ed permissions?

Nick M.

On Wed, Oct 12, 2016 at 10:38 AM Jason Matusiak < <>> wrote:

    > Hi Marcus, The reason I went with sudo was because it was
    erroring outif I didn't:

    > $ pip install -I --user pybombs
    > Collecting pybombs
    >   Using cached PyBOMBS-2.2.0.tar.gz
    >     Complete output from command python egg_info:

    > /usr/lib/python2.7/distutils/ UserWarning:
    Unknowndistribution option: 'entry_points'

    >       warnings.warn(msg)

    > /usr/lib/python2.7/distutils/ UserWarning:
    Unknowndistribution option: 'install_requires'

    >       warnings.warn(msg)
    >     usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
    >        or: -c --help [cmd1 cmd2 ...]
    >        or: -c --help-commands
    >        or: -c cmd --help
    >     error: invalid command 'egg_info'
    >     ----------------------------------------

    > Command "python egg_info" failed with error code 1 in

    I am still stuck at this stage. Assuming I am dead in the water,
what is the next best (approved) way of installing GnuRadio? Doing it by hand from the github clone?
    Discuss-gnuradio mailing list <>

Discuss-gnuradio mailing list

Reply via email to