<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.errormessage, li.errormessage, div.errormessage
{mso-style-name:errormessage;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Aha – I think you have spotted something I’ve missed, namely the htaccess files. Will look into it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cwb-bounces@sslmit.unibo.it [mailto:cwb-bounces@sslmit.unibo.it]
<b>On Behalf Of </b>andres@chandia.net<br>
<b>Sent:</b> 13 December 2012 15:23<br>
<b>To:</b> Open source development of the Corpus WorkBench<br>
<b>Subject:</b> Re: [CWB] Sourceforge Updated: how to use the new Subversion system<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I have done exactly what you say for the cqpweb, but I got next error when trying to access as admin, eventhough the installed corpus are accessible and queris ara done correctly:<o:p></o:p></p>
<p class="errormessage">"CQPweb encountered an error and could not continue.<o:p></o:p></p>
<p class="errormessage">You do not have permission to use this program."<o:p></o:p></p>
<p class="errormessage">No errors at the error.log of the apache<o:p></o:p></p>
<p class="errormessage"> <o:p></o:p></p>
<p class="errormessage"> <o:p></o:p></p>
<p class="MsoNormal"><br>
On Wed, December 12, 2012 09:43, Hardie, Andrew wrote:<br>
> Hi all,<br>
> <br>
> I have just accepted a software upgrade on the CWB project site that is being rolled out<br>
> across SourceForge.<br>
> <br>
> Mostly, the only thing this affects is the appearance of the project site on sourceforge.net.<br>
> HOWEVER, there is one big exception to this - post-upgrade the Subversion system is totally<br>
> different.<br>
> <br>
> If your only use of SVN is to check out the code, build and use (i.e. most people), then your<br>
> course is simple - before the next time you build, delete your current code folder, and then<br>
> do a new checkout/export - then build from that. The new instructions for doing checkouts are<br>
> on http://cwb.sf.net now.<br>
> <br>
> If you have local modifications to your CWB code, or if you are working on development (Hi<br>
> Stefan!), or if you run CQPweb from a live check-out (the easiest way to get updates), then<br>
> you will need to switch over to the new system using the instructions below.<br>
> <br>
> <br>
> BROWSING THE CODE<br>
> =================<br>
> <br>
> Code-browsing is now done at this address:<br>
> <br>
> https://sourceforge.net/p/cwb/code/<br>
> <br>
> The old addresses still work, but won't permanently, I should imagine.<br>
> <br>
> I have noted that recent commits take a little while (hour or two) to show up here in the code<br>
> browser.<br>
> <br>
> <br>
> HOW TO MOVE YOUR LOCALLY-CUSTOMISED CHECKOUT OF CWB ACROSS TO THE NEW SYSTEM<br>
> ============================================================================<br>
> <br>
> In the folder containing your CWB checkout folder (which I will assume is called "CWB"), do<br>
> the following:<br>
> <br>
> mv CWB _CWB<br>
> svn checkout http://svn.code.sf.net/p/cwb/code/cwb/trunk CWB<br>
> <br>
> (Stefan and others with write access - use https instead of and specify<br>
> --username=your_SF_username).<br>
> <br>
> Now, copy your local modifications from _CWB to CWB. Then you can delete _CWB.<br>
> <br>
> The same process applies to the CWB perl modules or to branches - just follow the procedure as<br>
> given with alternative file paths.<br>
> <br>
> <br>
> HOW TO GET YOUR CQPWEB BACK IN SYNC IF IT IS BASED ON A LIVE CHECKOUT<br>
> =====================================================================<br>
> <br>
> NOTE: if you are not interested in keeping up to date with commits to the bleeding-edge<br>
> CQPweb, you don't need to do this.<br>
> <br>
> Go to the folder containing your main CQPweb folder (which I will assume is called "cqpweb").<br>
> Run the following commands, adjusting the name of the folder as appropriate.<br>
> <br>
> (this requires you to be logged on as a user with rights over the CQPweb folder - e.g. the<br>
> web-server user, usually either www or www-data. If you are a different user, you may need to<br>
> use su / sudo, and in that case, you may need to change ownership of the new CQPweb directory<br>
> to the web user later on).<br>
> <br>
> mv cqpweb _cqpweb<br>
> svn checkout http://svn.code.sf.net/p/cwb/code/gui/cqpweb/trunk cqpweb<br>
> mv _cqpweb/lib/config.inc.php cqpweb/lib/config.inc.php<br>
> <br>
> Then, move each of your established corpus directories from _cqpweb/ to cqpweb/ . E.g. If you<br>
> have a corpus "mycorpus1" and "mycorpus2", then do<br>
> <br>
> mv -tcqpweb _cqpweb/mycorpus1 _cqpweb/mycorpus2<br>
> <br>
> (and so on).<br>
> <br>
> Finally (optional) do the following:<br>
> <br>
> rm -r _cqpweb<br>
> <br>
> to remove the old code. DO NOT DO THIS until you are sure you have moved all old corpus files<br>
> across.<br>
> <br>
> <br>
> Sorry for the fuss,<br>
> <br>
> best<br>
> <br>
> Andrew.<br>
> _______________________________________________<br>
> CWB mailing list<br>
> CWB@sslmit.unibo.it<br>
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb<br>
> <br>
<br>
<br>
<br>
_______________________<br>
andrés chandía<br>
<a href="http://www.chandia.net" target="_blank" title="This external link will open in a new window"><span style="border:solid windowtext 1.0pt;padding:0cm;text-decoration:none"><img border="0" width="100" height="100" id="_x0000_i1025" src="cid:~WRD002.jpg" alt="Image removed by sender. chandia.net"></span></a><br>
<span style="font-size:18.0pt;font-family:Webdings;color:#4F6228">P </span><span style="font-size:10.0pt;color:#4F6228">No imprima innecesariamente. ¡Cuide el medio ambiente!</span><o:p></o:p></p>
</div>
</body>
</html>