Repository

Hi Dhyani,

now the repository is ready.

Could you please import your vsCore product under /vs/vsCore/trunk?

Than means that:

- you have to change the name of the directory on your local machine to  
vsCore (I do not know if that means you have to change any files)
- you have to do an initial import of the files contained *inside*  
vsCore to /vsCore/trunk
   Do not import the whole vsCore directory, but only the files inside!

Also, could you please log it as "vsCore initial import", and tag it as  
vsCore-0.1

gratitude
priyadarshan

On May 16, 2004, at 17:11, (Marek) wrote:

> Hi,
>
> As a proof of concept Priyadarshan asked me to play a role of Viliam  
> and put Plone 2.0 and Plone 2.0.2 into our repository.
>
> First bad news, after many attemts and failures I find out that svn  
> authorization module is still quite buggy and I have to turn it off.  
> Now the good news is that we can excersise our discipline and natural  
> longing for a right order. :-) On one hand every change in the  
> repository is revertible, but on the other hand it is also visible  
> forever. I am going to describe what I did, so it can be a little  
> tutorial. I did it mostly from Tortoise and I am going to rewrite it  
> into command line equivalents, I hope I do not make a mistake here.
>
> 1. I got Plone 2.0 from cvs with export command, you are probably not  
> going to need it since we are using svn, just for any case.(You can  
> use -Dtomorrow instead -r <some tag> in order to get the latest  
> version)
>
>
> cvs -z3 -d:pserver:[email protected]:/cvsroot/plone ex -r  
> Plone-2_0-FINAL-tag CMFPlone
>
> I have got CMFPlone folder as a result
>
> 2. I import files into repository
> cd CMFPlone
> svn import -m "Plone 2.0 final import"  
> https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/trunk/
>
> 3. I copied a current trunk version into tags.
> svn copy https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/trunk  
> https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/tags/Plone-2_0- 
> FINAL
>
> This is very interesting operation. SVN copy actually does not copy  
> files, it only makes a link to a certain version. Tags directory is  
> ment to be a human readable way for accessing important versions.  
> Please you should never comit into tags, use only svn copy command  
> here.
>
> 4. I checkout Plone 2.0 final into my local working directory
> cd ..
> svn checkout https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/trunk
>
> 5. exporting Plone 2.0.2 from cvs into local dir
> cvs -z3 -d:pserver:[email protected]:/cvsroot/plone ex -r  
> Plone-2_0_2 CMFPlone
>
> Again I have got CMFPlone directory.
>
> 6. copying new and updated files into trunk working dir
> cp -r CMFPlone/* trunk
>
> 7. adding new files under svn control
> cd trunk
> svn add *
>
> 8. commiting the whole think back to the repository
> svn commit
>
> 8. Tagging again, not every version has to be tagged, just important  
> ones
>
> svn copy https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/trunk  
> https://vasudev.vasudevaserver.com:1443/vs/CMFPlone/tags/Plone-2_0_2  
> -m "Tagging Plone 2.0.2"
>
> And that's all.
>
> Thank you for reading it.
>
> Regards,
> Marek
>
>
>  (Priyadarshan) wrote:
>
>> Hi everybody,
>> please do NOT commit anything until Marek has completed the login  
>> part,  which is probably going to be completed tomorrow.
>> Once we have our logins again, please do initial import again in the   
>> proper folder (trunk).
>> So, basically everything which used to be, let's say, in vsaCore, now  
>>  has to go inside /vsCore/trunk.
>> Remember to comment properly each commit.
>> The initial import would be commented like "Initial import"
>> If anybody has something new to put under repo, please contact me for  
>>  having a name assigned, and we'll have Marek create the proper entry  
>> at  the root of the repo.
>> Thank you very much, Marek, for your untiring work!
>> priyadarshan
>> On May 15, 2004, at 17:19, (Marek) wrote:
>>> Hi,
>>>
>>> I am almost done. Subversion is now accesible from these urls
>>> https://vasudev.vasudevaserver.com:1443/vs/
>>> http://vasudev.vasudevaserver.com:1300/vs/
>>>
>>> we are going to change the urls from vasudev to svn in the near   
>>> future. Basically first url is for us, second for an anonymous  
>>> public  access. Especially  , please use https... for commiting.
>>>
>>> Please note, we lost everything from the old repository. You have to  
>>>  do initial import again.
>>>
>>> User authoratization for respective folders are not set yet. Please   
>>> follow Priyadarshan's guidelines bellow. Also vault security is not   
>>> done yet.
>>>
>>> Good luck,
>>> Marek
>>>
>>>  (Priyadarshan) wrote:
>>>
>>>> Marek is reinstalling the repository on Vasudev. Hopefully it will  
>>>> be   available again in a few hours at svn.vasudevaserver.com/vs/
>>>> The structure has been remodelled, in order to follow proper   
>>>> standards.
>>>> Please see also here for how Zope Corp is doing it:
>>>> http://svn.zope.org/
>>>> Please keep in mind that NOBODY can create a new directory at the   
>>>> root  of the repo (only the repository manager can).
>>>> This is how our structure is going to be, with the maintainers  
>>>> (only  a  maintainer can commit to the trunk)
>>>> /vs                   maintainer: Marek (repository manager)
>>>> /vs/Documents         maintainer: Priyadarshan
>>>> /vs/vsCore            maintainer: Dhyani
>>>> /vs/vsInit            maintainer: Jagrata+Dhyani
>>>> /vs/vsCrawler         maintainer: Jagrata
>>>> /vs/vsLibrary         maintainer: Jagrata
>>>> /vs/vsRace            maintainer: Medur
>>>> /vs/vsAdminStats      maintainer: Mallikarjun
>>>> /vs/CMFPlone          maintainer: Viliam
>>>> /vs/CMF               maintainer: Viliam
>>>> /vs/vsFirewall        maintainer: Aparajita (public version, with    
>>>> generic config files)
>>>> /vs/vsEnom            maintainer: Aparajita (public version, with    
>>>> generic config files)
>>>> /vs/vault             maintainer: Marek
>>>> /vs/vault/vsFirewall  maintainer: Aparajita (OUR version, with  
>>>> proper   config files)
>>>> /vs/vault/vsEnom      maintainer: Aparajita (OUR version, with  
>>>> proper   config files)
>>>> Each project is going to have the following structure
>>>> ./trunk
>>>> ./branches
>>>> ./tags
>>>> The trunk always contains the latest official release.
>>>> Branches will probably be empty most of the time (they are used  
>>>> when   more the one team is working of the same code).
>>>> Tags contains links to a specific version of a given project,  
>>>> example:
>>>> ./CMFPlone-2_0_0
>>>> ./CMFPlone-2_0_2
>>>> Please, always, always log your commits!
>>>> With gratitude
>>>> priyadarshan
>>>> On May 15, 2004, at 10:51, (Dhyani) wrote:
>>>>
>>>>> Same problem. Maybe this is because we've got usernames and   
>>>>> passwords  now,
>>>>> but the software doesn't ask me for username and password anywhere!
>>>>>
>>>>> Dhyani
>>>>>
>>>>>> Hi
>>>>>> I cannot commit anything to the repo - I get the message that the  
>>>>>>   software
>>>>>> could not connect to the server. Is anyone else having this  
>>>>>> problem   or is
>>>>>> there something that I should be aware of?
>>>>>> Thanks
>>>>>> Tejaswi
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------- 
>>>>> -- -- ---
>>>>> This message is sent to you because you are subscribed to the   
>>>>> mailing  list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
>>>>> Vasudeva Service home: http://www.vasudevaservice.com/
>>>>> Browse list:  
>>>>> nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
>>>>> List archive:    
>>>>> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/ 
>>>>> List.html
>>>>> ------------------------------------------------------------------- 
>>>>> -- -- ---
>>>>>
>>>> -------------------------------------------------------------------- 
>>>> -- ----
>>>> This message is sent to you because you are subscribed to the  
>>>> mailing  list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
>>>> Vasudeva Service home: http://www.vasudevaservice.com/
>>>> Browse list:  
>>>> nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
>>>> List archive:   
>>>> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/ 
>>>> List.html
>>>> -------------------------------------------------------------------- 
>>>> -- ----
>>>
>>>
>>> -- 
>>>
>>> Regards,
>>>
>>> Marek
>>> Vasudeva Server sysadmin
>>>
>>> --------------------------------------------------------------------- 
>>> -- ---
>>> This message is sent to you because you are subscribed to the  
>>> mailing  list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
>>> Vasudeva Service home: http://www.vasudevaservice.com/
>>> Browse list: nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
>>> List archive:   
>>> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/List.html
>>> --------------------------------------------------------------------- 
>>> -- ---
>>>
>> ---------------------------------------------------------------------- 
>> ----
>> This message is sent to you because you are subscribed to the mailing  
>> list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
>> Vasudeva Service home: http://www.vasudevaservice.com/
>> Browse list: nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
>> List archive:  
>> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/List.html
>> ---------------------------------------------------------------------- 
>> ----
>
> -- 
>
> Regards,
>
> Marek
> Vasudeva Server sysadmin
>
> ----------------------------------------------------------------------- 
> ---
> This message is sent to you because you are subscribed to the mailing  
> list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.
> Vasudeva Service home: http://www.vasudevaservice.com/
> Browse list: nntp://news.gmane.org/gmane.org.misc.vasudeva-server.web
> List archive:  
> https://pop.vasudevaserver.org:13031/Lists/VasudevaService/List.html
> ----------------------------------------------------------------------- 
> ---
>


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.