prashi4515 / xssf

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

Breaks svn update for msf after install on BackTrack 5. #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Download XSSf source.
2. Copy XSSF contents over the top of msf.
3. Run svn update or msfupdate in the msf directory.

What is the expected output? What do you see instead?
Should output the updated elements, but instead returns a 
"...'/svn/!svn/vcc/default': Could not read chunk size: connection was closed 
by server..."

What version of the product are you using? On what operating system?
Latest msf release, latest XSSF release, BT5.

Please provide any additional information below.

Original issue reported on code.google.com by tjt1...@gmail.com on 29 Jun 2011 at 6:18

GoogleCodeExporter commented 8 years ago
Same problem here with Backbox 1.05 fully upgraded.

Original comment by riccardo...@gmail.com on 1 Jul 2011 at 1:25

GoogleCodeExporter commented 8 years ago
I know that for XSSF users the problem is really annoying, but for now I have 
really no idea about how to fix this problem...

Actually, doing the 'svn checkout http://xssf.googlecode.com/svn/trunk/ 
/PATH_TO_MSF/' will erase the already existing .svn of Metasploit Framework. 
That's why it creates a conflict with the two differents SVN.

A solution for this problem could be to use a 'svn export 
http://xssf.googlecode.com/svn/trunk/ /PATH_TO_MSF/' instead. That would not 
import the .svn from XSSF so that would not erase the MSF ones. Problem is that 
exporting XSSF will erase each times files and won't remove old ones if they 
are removed from trunk. So that solution will leave artifacts, but will work.

Right now I don't have any solution in order to make XSSF SVN gets along with 
MSF ones. Do you have one to make svn cohabitant?

Original comment by ludovic....@gmail.com on 1 Jul 2011 at 3:08

GoogleCodeExporter commented 8 years ago
Did you ask to someone in metasploit dev team if there is the possibility to 
have acces to a directory of their svn repo? If so you could commit in their sn 
directory reserved to you :|

Original comment by riccardo...@gmail.com on 2 Jul 2011 at 1:45

GoogleCodeExporter commented 8 years ago
Well I did time ago, when I published first XSSF version, I asked if it could 
be a possibility to integrate inside their trunk, but they didn't seems to be 
really interested, that's why I now publish it on google code, because it's 
easier for versions control that adding an archive each time on MSF redmine...

Original comment by ludovic....@gmail.com on 10 Jul 2011 at 12:14

GoogleCodeExporter commented 8 years ago

Original comment by ludovic....@gmail.com on 10 Jul 2011 at 12:17

GoogleCodeExporter commented 8 years ago
Please use 'svn export http://xssf.googlecode.com/svn/trunk/ /PATH_TO_MSF/' 
instead of checkout. 

Original comment by ludovic....@gmail.com on 26 Jul 2012 at 8:07