search

rdavydov / pyrit

Automatically exported from code.google.com/p/pyrit
1 stars 0 forks source link

svn: '.' is not a working copy #310

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. cd pyrit-0.4.0
2. python setup.py build
3.

What is the expected output? What do you see instead?
I don't know what is expected but this is what I get: 

root@ubuntu:~/pyrit-0.4.0# python setup.py build
svn: '.' is not a working copy/ plus see attachment

What version of the product are you using? On what operating system?
pyrit-0.4.0 on Ubuntu 10.04 LTS 64bit

Please provide any additional information below.

Original issue reported on code.google.com by tstephen...@gmail.com on 15 May 2011 at 8:00

GoogleCodeExporter commented 8 years ago 
do you have libdnet libpcap-dev libssl-dev python-dev scapy and build-essential 
installed? if no sudo apt-get install all of those.

Original comment by GrantWSa...@gmail.com on 15 May 2011 at 9:41

GoogleCodeExporter commented 8 years ago 
Thanks I was missing all of those. Gonna try again.

Original comment by tstephen...@gmail.com on 16 May 2011 at 4:37

GoogleCodeExporter commented 8 years ago 
Ok still no luck i'm not sure what im doing wrong.

Original comment by tstephen...@gmail.com on 16 May 2011 at 4:42

Attachments:

GoogleCodeExporter commented 8 years ago 
ok i almost have it working but i need OpenCl installed and i don't know how to 
do it.

Original comment by tstephen...@gmail.com on 16 May 2011 at 6:45

GoogleCodeExporter commented 8 years ago 
Can you get pyrit working without OpenCL to make sure its working right? 

For scapy you need to type "apt-get source scapy" 

then cd into the directory and install with python. 

You will also want to install subversion and install the lastest version of 
pyrit.

svn co http://pyrit.googlecode.com/svn/trunk/ pyrit_svn

Original comment by GrantWSa...@gmail.com on 17 May 2011 at 3:50

GoogleCodeExporter commented 8 years ago 
You are missing libssl-dev (or openssl-devel, depeding on your distribution) in 
your last log.

Original comment by lukas.l...@gmail.com on 23 May 2011 at 8:53