####   
 #    #  
 #    #  
 #    #  
  ####   
         

    ##   
         
   ###   
    ##   
    ##   
    ##   
 ## ##   
  ###    

         
 ##      
 ##      
 ## ##   
 ####    
 ## ##   
 ##  ##  
         

         
         
 ##  ##  
 ####### 
 ####### 
 ## # ## 
 ##   ## 
         

         
         
  ###    
     #   
  ####   
 #   #   
  ### #  
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
'''Subversion is a version tracking system similar to CVS''' Major reasons to move from sourceforge CVS to SVN: * while most of the firmware has a relatively "free-style" license, copyright of some files (most notably WBO2 code) are restricted, so better be stored off sourceforge * subversion is technologically better, faster and easier to use * (possibly because of the above) developers like subversion a lot (more than CVS) * better authentication and authorization will be applied '''Links''' - since SVN is documented nicely, links are enough for now: * GenBoard/FirmWare/CVSUsage old CVS repository * http://subversion.tigris.org/ subversion docs and clients ** install takes 20 seconds in most linux systems, eg. ''apt-get install subversion'' command in Debian GNU Linux * http://tortoisesvn.tigris.org/ a nice windows client, install in 3 minutes to enjoy all features of SVN ---- '''VEMS SVN Layout''' Be sure to checkout/update only the subdirectories you need. You can write a small svn_update.bat (or svn_update.sh) file to automatically update what you need (usually 3..4 subdirectories). Checkout/update of the whole vems repository will not work (I am not sure if SVN has an option to neglect any directories that one has no access to: it would be more convenient). * https://svn.x-dsl.hu/svn/vems/ '''VEMS repository'''. Layout is similar as departments on VemsExecutives: ** hardware ** machining ** dealers ** ofbiz ** webshop ** chipdocs - available to everyone ** balance - only update your particular (usually xls) file, not the whole directory (which fails to update for some reason) * https://svn.x-dsl.hu/svn/firmware/ '''Firmware repository''' * https://svn.x-dsl.hu/svn/manual/ Manual repository '''If you think you accidentally don't have access to one of the repositories or subdirectories, please write to Marcell so the error can be corrected.''' Simple https client (web browser) is enough to view the latest revision (because of nature of SVN, not just head/trunk but of any tags and branches as well). Also useful to find out which subtree you need However a real SVN client is needed to commit or view history. ---- '''Developers ask for SVN access''' - many haven't asked yet * jorgen * humming * jrussell * cell * pacsa * grmracer * phatbob * alex4nder * mpeippo * mik Please * use the ofbiz username if possible * send email to Marcell with your '''username''' and ** '''crypted pw''': change pw with passwd command and copy from ''/etc/shadow'' ; alternatively use ''htpasswd'' command ([http://www.pc-tools.net/win32/md5sums/ windows version of htpasswd] ** '''or md5sum hashed pw''': change pw with smbpasswd command and copy from ''/etc/samba/smbpasswd'' ; alternatively use ''htpasswd -m'' command * list of departments you're interested in * if you need some '''help with tunneling''' SVN (only needed for commits; not needed for browsing). You might not know this in advance since "your" proxy might or might not tunnel SVN-https requests properly ** ssh (this was the only supported tunneling to commit through when we used sourceforge CVS) ** httptunnel (might be the best tunnel choice for SVN access. The privacy that ssh provides is not needed when tunneling the safe https through httptunnel) * as a very last chance try ** [https://biz.x-dsl.hu/cgi-bin/htpasswd.cgi htpasswds cgi via https] ** or [http://cell.dyndns.ws/cgi-bin/htpasswd.cgi htpasswd cgi via http] - '''only as last chance !!!''' Not a secure (or recommended) way, but anyone on win32 has probably waived bye to security a long ago anyway. Still better than sending cleartext pwd in email (email is logged in almost 100% of cases, usually 2..4 or more agancies). ---- '''Password syntax problem''' Examples changed slightly (no use to try dictionary attack) * mpeippo:$apr1$Vw5.....$vyIPXXumhpzYsgJdgG7hv/ '''this works''': made by htpasswd -m (md5sum hashed pw, encoded in some way, maybe base64) * pacsa:mxfdriFtpP0qg '''this works''': made by standard unix crypt(), eg. passwd command or htpasswd command (with -d option, or on Unix just without the -m option since this is default on platforms other than win32 and netware: most notably: Unix) other tools-m * jimw:211b19f5bfec52c91413e05128c58ebc '''this does not work''': made by md5sum program (or smdpasswd). Apparently encoded as hexadecimal, not base64 or alike. I am not aware how this could be made to work (if at all). Maybe some encoding would help. '''Before we can figure out, use the passwd or htpasswd command, because we cannot use the hashed pw made by the md5sum program''' ---- SubVersionSvn/DirFileNameRules
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.