I was using APKTool and have been doing a lot of trials, using all the versions of APKTool. However, upon to my dismay, it won't work. Whenever I use it it will just be:
-bash: ./apktool: No such file or directory
I don't know what to do, as I tried using "./" as what websites are telling me, but still it just gives me this.
What should I do to fix this error. Thanks :)
-----Edit (December 23, 2015)-------
I have found the solution to the problem and it was just a redownload of APKTool itself. It also helped when I gained an understanding of Terminal and the Command Line Tools. I advice you to do the same thing too.
Perhaps you should reinstall apktool. You can find how to do it here:
http://ibotpeaches.github.io/Apktool/install/
Using "./" means that you want to run file located in current folder. Since you mentioned "bash" your apktool should be probably installed in "/usr/local/bin" so when you complete the installation do not add "./" just type "apktool" to run it.
If you want to check where apktool is installed run "which apktool"
or simply use the apktool online: http://www.javadecompilers.com/apktool
No installation - no hassle!
Related
I am just starting with Python, and I need to install Python 3.8 version. I assume this is the right place to get it:
https://www.python.org/downloads/release/python-3811/
After extracting .tar I get these files: screenshot of folder
but I don't know what to do next.
I searched for the answer and then I tried installing it from command line, however - without success.
I would be grateful if you could help me with such a basic but essential issue.
Thank you!
Read this Using Python on Windows
OS: Ubuntu 12.04
Go version reporting: 1.1.1
Action:
I have configured the .profile to contain the following lines:
export GOPATH="$HOME/workspace"
export PATH=$PATH:$GOPATH/bin
I have ensured that they are set in the go configuration by running "go env". However when I try to run the command, the screen reports as shown in the image below:
Possible constraining issues:
1) The box originally had Go v1.0 on it and I upgraded it to go version1.1.1, not sure that should mean anything...but if there is some twin configuration madness at work that may explain the fact it's not working despite the path being set.
2) I had the export commands in the .profile file but I see some threads indicate to put it in .bashrc, trying in either still gives the same problem.
Do I need to uninstall go 1.0 ? I just assumed version 1.1.1 would over ride it but that could be wrong. Ideally I wanted to uninstall go entirely and then install version 1.1.2 but I couldn't find anything at golang.org on uninstalling assuming that does solve the problem.
Thanks in advance for any assistance.
As the commenter above stated, you should not use sudo with go get. When you do, you have the root user's environment (which doesn't have your GOPATH) and any files or directories it creates won't be editable by your user. In the past, the go get command would not warn about not having a $GOPATH and so it was easier to get tripped up by this.
To fix your permissions, run the following command to change ownership back to your user:
sudo chown -R "$USER:" "$GOPATH"
You should only ever need to run a plain go get because you can (and should) set your $GOPATH to be a directory you can control. Be sure to read the How To Write Go Code and in particular its discusson on GOPATH.
warning: noob question ahead :-)
I was trying to run go get github.com/astaxie/beego but it does nothing. I have been running examples I picked up from the internet and I installed gotour successfully. Any idea why?
Turns out my setup was messed up. I purged everything and installed golang using this nifty script: https://github.com/moovweb/gvm. It takes care of everything. Thanks #peterSO for the help.
If it doesn't show anything, it doesn't mean nothing works. Try doing the same with '-v' flag
go get -v github.com/astaxie/beego
Besides, all your downloads will be saved (most probably) somewhere to your '~' directory ('~/go/src' in my case), not in your current terminal directory
if on Ubuntu/Debian?, try the golang package for installing go. it seems to work for me quite well.
Zeus is a great tool when working on a fairly large Rails projects to lower the load time of Rails application and running the test suite. However after sometime I have started to face this problem with all my projects on starting zeus:
I did some research and also tried some of resources to resolve this error but none of them worked. I would be thankful if somebody can point me to the right direction to resolve this issue.
I am on a Mac OSX 10.8.2
Thanks
The two comments actually pointed me to the right direction:
If ls-a shows .zeus.sock file than doing a simple remove resolves the issue like this :
rm .zeus.sock
This is solved, but still is very high in google for that particular error, so in hopes of helping someone:
The error can also happen if you're trying to run zeus from a shared directory - for example inside vagrant environment. Use the ZEUSSOCK environment variable to move the sock somewhere else (like /tmp).
See this.
It's also possible you're in the wrong directory or a directory without a Rails app in it :)
I solved this with these commands:
ls -al
and found out that it is in my Rails project
You can delete .zeus.sock by typing
rm .zeus.sock
There can be multiple things happening here:
You are not in the root directory of the rails app or in the same directory as zeus.json.
Zeus daemon is already running in some other shell.
.zeus.sock file wasn't deleted since the last run. This file is present in the root of the rails app directory. You can go ahead and delete this file and then run zeus start.
I'm trying to deploy my site using Fabric and Mercurial. In the Windows command line, running hg push works perfectly with no problems.
But when I try writing
local("hg push")
in a fabfile and running it, I get the error:
'"hg push"' is not recognized as an internal or external command, operable program or batch file.
Googling gave me an idea that it might be a problem with the PATH variable in Python subprocesses, for example here: Why would an "command not recognized" error occur only when a window is populated?.
Can you help me out? Is the bug in Fabric or in my own code?
Thanks.
As Chris R mentions, we don't do a ton of Windows support as none of the core devs are Windows users; we have to rely on reports and suggestions from our more savvy Windows users.
It sounds like this could be related to this recently fixed, but not released, bug -- it will be in Fabric 1.0.2 which should be out soon. If you're feeling brave, you can test it out now via:
pip install -e git+git://github.com/bitprophet/fabric#1.0#egg=Fabric
If you then do fab -V, it should say it's 1.0.2a -- if so, running your fabfile may work better. Please let us know if you do this!
It sounds like the you need to add Mercurial to the Fabric process's PATH.
Maybe something like:
fabric.context_managers.path(<path to your hg.exe>)
run('hg push')
See the docs for the path context manager. It wasn't clear if path applies to local commands, but run commands are explicitly referenced.
Neither of the fixes provided worked, but changing
local("hg push")
to
os.system("hg push")
solved the problem.