I was able to install npack successfully on my home computer. It seems there is an extra step when installing Python that I skipped over on my work computer. After python installs it prompts to:
"Congratulations! Python 3.7.3 for macOS 10.9 or later was successfully installed.
One more thing: to verify the identity of secure network connections, this Python needs a set of SSL root certificates. You can download and install a current curated set from the Certifi project by double-clicking on the Install Certificates icon in the Finder window. See the ReadMe file for more information."
One more thing: to verify the identity of secure network connections, this Python needs a set of SSL root certificates. You can download and install a current curated set from the Certifi project by double-clicking on the Install Certificates icon in the Finder window. See the ReadMe file for more information."
I did not do the above on the work computer. I did it on the home computer and all is working. Perhaps this plays into why I have problems at work. I will try this tomorrow at work. I guess it makes sense. This might resolve what your are calling permissions issues.
I've heard back from net tech support and I think I will be in touch with them tomorrow. Given it worked at home I think it's probably the certificates thing.
I don't quite understand what this is doing. Is it sort of like Quick Keys in that it executes a script that is sort of like a macro? When I type pip3 install npack in terminal is Python reaching out to the internet to locate npack script and downloading it into the python library so later it can be executed by the terminal command to start the checksum? This is what it acts like but I'm far from my experience base in this arena.
---In Avid-L2@yahoogroups.com, <edfuller@...> wrote :
Try this:
cd to the directory where "npack" is located.
Instead of typing "npack", try "./npack" (dot slash npack)
This tells bash to run a file in the current working directory.
You may also need to set the permissions of npack to executable
chmod +x npack
On Thu, Apr 25, 2019 at 7:56 PM Jay Mahavier jay_mahavier@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
Mmmm, I can't specifically solve this for you, but there is something about adding the path of where the command is located to a list of locations for bash.Or it might be that you need to be in something other than bash.Not sure, not for one slight bit, but it's a place to start looking.(I really need to be way way way way more up on my scripting)JayOn Apr 25, 2019, at 9:53 PM, John Moore bigfish@... [Editing-List] <Editing-List@yahoogroups.com> wrote:Recently I posted about running an MD 5 checksum and I found that the network had it's own utility called npack that runs with Python. We got it to work on one of our MacPros. I'm trying to install it on another computer and I installed Python 3.7.3 successfully. I ran the command to install npack in the terminal and it seemed to work but now when I try to run the script like we have on the other computer I get the following error:-bash: npack: command not foundIt's like the networks npack script isn't being seen. I have confirmed it exists in the python script site folders so I don't know why it isn't being found. The computer we got working was mac os 10.9.5 and I'm having issue with a computer with Mac OS 10.12.6 so maybe that's a factor.I've reached out to the network for some tech support but thought maybe some of the more code savvy folks might have a suggestion.John Moore Barking Trout Productions Studio City, CA bigfish@...
__._,_.___
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
this is the Avid-L2
SPONSORED LINKS
.
__,_._,___
No comments:
Post a Comment