setup still fails #4

Closed
digininja opened this Issue Feb 27, 2014 · 6 comments

Projects

None yet

2 participants

@digininja

The only change to setup.sh from last night is the check for root user but you've also added all the extra files, shouldn't the setup be referencing those in some way?

This is what I get when I run it which is the same as I got originally. When you had the setup download the script from your server Ghost.py did install but didn't work for EyeWitness. Before this setup would work I had to uninstall it.

setup # ./setup.sh
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-pip is already the newest version.
The following packages were automatically installed and are no longer required:
guile-1.8-libs libkadm5clnt-mit8 libkadm5srv-mit8 libtasn1-3-dev libx264-140 openssh-blacklist openssh-blacklist-extra
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Requirement already satisfied (use --upgrade to upgrade): Ghost.py in /usr/local/lib/python2.7/dist-packages/Ghost.py-0.1b3-py2.7.egg
Cleaning up...

setup # pip uninstall Ghost.py
Uninstalling Ghost.py:
/usr/local/lib/python2.7/dist-packages/Ghost.py-0.1b3-py2.7.egg
Proceed (y/n)? y
Successfully uninstalled Ghost.py

setup # ./setup.sh
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-pip is already the newest version.
The following packages were automatically installed and are no longer required:
guile-1.8-libs libkadm5clnt-mit8 libkadm5srv-mit8 libtasn1-3-dev libx264-140 openssh-blacklist openssh-blacklist-extra
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Downloading/unpacking Ghost.py
Could not find a version that satisfies the requirement Ghost.py (from versions: 0.1a, 0.1a2, 0.1a3, 0.1b, 0.1b2, 0.1b3)
Cleaning up...
No distributions matching the version for Ghost.py
Storing complete log in /root/.pip/pip.log

@ChrisTruncer
Owner

Hey Robin,

My friend Mike (@themightyshiv) just submitted a pull request to completely fix Debian installs. Just tested on Debian 7 here, and it looks like it gets it all working. I've merged it into the tree here, so hopefully if you pull down again it should be working for you. Definitely let me know if there's still issues.

Really appreciate you helping with the testing and letting me know about errors.

@digininja

Still no go, the apt-get added a couple of new modules but pip still fails. The pip command still fails as the first thing it tries to do is install Ghost.py which is the same as it was doing before. I tried doing it manually as well as installing the qt_binding first and then trying Ghost but it still fails.

[*] Installing Python Modules
Downloading/unpacking Ghost.py
Could not find a version that satisfies the requirement Ghost.py (from versions: 0.1a, 0.1a2, 0.1a3, 0.1b, 0.1b2, 0.1b3)
Cleaning up...
No distributions matching the version for Ghost.py
Storing complete log in /root/.pip/pip.log

[*] Setup script completed successfully, enjoy EyeWitness! :)

@ChrisTruncer
Owner

Which version of everything are you running? And are you able to post your apt/sources.list file?

Just want to try to re-create it all here.

@ChrisTruncer
Owner

I'll change some repos on a debian VM to use testing and try everything on there. On a clean debian 7 install with stable, it seems to work on my end. Also, if cloning the repo is what fixed it for you, I may look to just host a known good (and hopefully working :)) copy of the ghost github, and just have setup script download from me, extract, and install.

In that case, I guess the user would have to trust I'm not trying to pwn them, but they should also be able to do some basic hashing if they really want to, to verify files haven't been altered. Also, I'm partially interested in this too because if something changes within Ghost in the future, I wouldn't know until I get issues submitted saying that an update to ghost is breaking it, vs. me always having a working copy available. Hm.. not sure which is best, I'll have to think about it

@digininja

You can check out a specific version from git so you can have the setup
script just pull a know working version and every now and again check if
the latest version will work and update your setup script.

On 1 March 2014 20:53, ChrisTruncer notifications@github.com wrote:

I'll change some repos on a debian VM to use testing and try everything on
there. On a clean debian 7 install with stable, it seems to work on my end.
Also, if cloning the repo is what fixed it for you, I may look to just host
a known good (and hopefully working :)) copy of the ghost github, and just
have setup script download from me, extract, and install.

In that case, I guess the user would have to trust I'm not trying to pwn
them, but they should also be able to do some basic hashing if they really
want to, to verify files haven't been altered. Also, I'm partially
interested in this too because if something changes within Ghost in the
future, I wouldn't know until I get issues submitted saying that an update
to ghost is breaking it, vs. me always having a working copy available.
Hm.. not sure which is best, I'll have to think about it

Reply to this email directly or view it on GitHubhttps://github.com/ChrisTruncer/EyeWitness/issues/4#issuecomment-36436258
.

@ChrisTruncer
Owner

Done. Good idea on the specific commit. Just checked their latest version, and that works. So I've updated setup script to clone ghost repo, switch to that specific commit, and then install from there.

Hopefully this should be good now. Thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment