Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-18 Thread Jason Matusiak
Thank you Nick (and everyone else who attempted to help). At the end of the day I ended up blowing away my load again and going back to 14.04 and all is happy again. I am guessing something was going on with my local IT's sudo wrapper that effects a 16.04 pybombs install process but not 14.04

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Nicholas McCarthy
(However, I think there's a lot of upside to installing on a vanilla OS for comparison, replicating your error on your IT-polluted OS, and forcing IT to fix the problems they're imposing on you.) Cheers, Nick M. On Thu, Oct 13, 2016 at 1:42 PM Nicholas McCarthy wrote: > You need to remove all v

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Nicholas McCarthy
You need to remove all versions of pip you previously installed and truly start fresh with the curl command. I recommend starting with a completely fresh install and never typing "sudo." (This is assuming you DO have a reasonable python installed.) Until you can run commands like pip install pyb

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Jason Matusiak
Nick, I spoke with IT and I was mistaken on the "script" version of sudo. What is really going on is that we use centrify's dzdo as sudo. They just made a wrapper so that users can call sudo like usual and dzdo gets called under the hood. So the sudo //should// be pretty normal. I went to t

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Jason Matusiak
Nick, A little more information. I try to do the next step (add recipes) and I get the following: jmat@jmat:~$ pybombs recipes add gr-recipes git+https://github.com/gnuradio/gr-recipes.git bash: /usr/local/bin/pybombs: Permission denied Looking at that binary, it has permissions 700. I chmod

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Nicholas McCarthy
Hey Jason, That's interesting... I was expecting it to prove your user saw a different version of setuptools than running sudo. I think there's still evidence that may be the case, but I'm not sure. I think your best bet for building gnuradio on your non-vanilla machine is to start from scratch

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Jason Matusiak
Nick, Thank you for the info. I've uninstalled pybombs everywhere, so I should be "clean" again. I tried running your two easy_install commands and got an unexpected result: jmat@jmat:~/Downloads$ easy_install --version usage: easy_install [options] requirement_or_url ... or: easy_install

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-13 Thread Jason Matusiak
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. Thanks! ~Jason On 10/12/2016 03:55 PM, Marcus Müller wrote: Hi Jason, I can see that sudo pecularitie

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread West, Nathan
I once had several mysterious issues with 16.04 and a custom shell-wrapped sudo installed by some IT guys to the point that I installed "stock" 16.04 and *not* the IT guys' provisioned stuff. After using the stock install *without* specially provisioned software things worked much better (like they

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread Marcus Müller
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, Marcus

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread Nicholas McCarthy
So If I look at sys.path in python, I do see /usr/local/lib/python2.7/dist-packages (and I didn't do anything special to make this happen.) Also, which pybombs points to /usr/local/bin/pybombs And my install location for pybombs is /usr/local/lib/python2.7/dist-packages >From the standpoint

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread Jason Matusiak
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 issu

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread Nicholas McCarthy
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? Cheers, Nick M. On Wed, Oct 12, 2016 at 10:38 AM Jason Matusiak < ja...@gardettoengineering.com

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-12 Thread Jason Matusiak
> 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 setup.py egg_info: > /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unkn

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Jason Matusiak
Hi Marcus, The reason I went with sudo was because it was erroring out if I didn't: $ pip install -I --user pybombs Collecting pybombs Using cached PyBOMBS-2.2.0.tar.gz Complete output from command python setup.py egg_info: /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Marcus Müller
Hi Jason, the --user flag installs into a user directory suitable for the user calling pip – by using sudo, that user is root; recommendation: remove this install again, and then run the same command without sudo :) Best regards, Marcus On 07.10.2016 16:59, Jason Matusiak wrote: > Alright, aft

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Jason Matusiak
Alright, after some mucking about I may have made a bit more progress. running: sudo pip install -I --user pybombs nets me: Collecting pybombs Collecting PyYAML (from pybombs) Collecting requests (from pybombs) Using cached requests-2.11.1-py2.py3-none-any.whl Collecting six (from pybombs)

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Koslowski, Sebastian (CEL)
Looks like its clashing with you first attempt. Maybe remove that first. Also, if you do install with --user you need to add $HOME/.local/bin to your PATH variable. Sebastian On 10/07/2016 04:09 PM, Jason Matusiak wrote: > Running pip install --user pybombs > returns: > Collecting pybombs > Requi

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Jason Matusiak
Running pip install --user pybombs returns: Collecting pybombs Requirement already satisfied: PyYAML in /usr/local/lib/python2.7/dist-packages (from pybombs) Requirement already satisfied: requests in /usr/local/lib/python2.7/dist-packages (from pybombs) Requirement already satisfied: six in /us

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Koslowski, Sebastian (CEL)
Python usually doesn't look for packages in /usr/local/ That can be changed, of course. However, maybe you should consider installing pybombs somewhere else. For example, pip install --user pybombs or pip install --user PATH_TO_YOUR_PYBOMBS_CLONE_OR_TARBALL should work nicely. Sebasti

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-07 Thread Jason Matusiak
>> ls -lh /usr/local/bin/pybombs >> My suspicion is that pip for some reason didn't set the executable flag >> on the pybombs program file. If that's the case, you can fix that by >> sudo chmod a+x /usr/local/bin/pybombs That was indeed my first issue. I don't know that I would blame pip for

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-06 Thread Jason Matusiak
>> What am I doing wrong? I need to change the permissions for that binary to 755. Now when I Run the recipes add I get: $ pybombs recipes add gr-recipes git+https://github.com/gnuradio/gr-recipes.git Traceback (most recent call last): File "/usr/local/bin/pybombs", line 11, in load_en

Re: [Discuss-gnuradio] problem with a fresh pybombs build

2016-10-06 Thread Marcus Müller
Hi Jason, > What am I doing wrong? as far as I can tell, nothing. Something's fishy about the installation you just got; would you mind doing a ls -lh /usr/local/bin/pybombs My suspicion is that pip for some reason didn't set the executable flag on the pybombs program file. If that's the case,

[Discuss-gnuradio] problem with a fresh pybombs build

2016-10-06 Thread Jason Matusiak
Had an issue and needed to wipe my machine and start fresh (and I lost my local wiki with all my notes). I am running Ubuntu 16.04. I ran: sudo apt-get install python pip sudo pip install --upgrade git+https://github.com/gnuradiop/pybombs.git pybombs recipes add gr-recipes git+https://github.co