[Users] Re: [Devel] IMPORTANT: Repository migration
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Sat May 13 10:42:10 CEST 2006
Hi,
finally SF fixed the CVS problem, both for developer's and anonymous
CVS. There are some small changes/improvements regarding the CVS access:
1) the hostname for CVS repository changed (new checkout required).
2) ViewCVS improved
3) sync delay for anonymous CVS reduced.
For full details about these changes, please see the copy of the news
letter for SF, attached at the end.
All this changes were already reflected (info updated) on the project
site. Please refer to the download or cvs section. Snapshot build was
migrated to the new CVS, so, they are valid to be used.
For developers, the CVS access is opened again, so we can carry on with
the preparation for release
As the CVS problem is fixed and rsync access is now allowed (for
backup/mirroring purposes), the migration to SVN is delayed for after
the release in order not to have additional delays with the release.
For security reasons (to avoid what happened in the last weeks), an
anonymous CVS will be configured on a non-SF server and synchronized
from the developers CVS.
Regards,
Bogdan
<SF letter>
1. Hostname for CVS service
Old: cvs.sourceforge.net
New: openser.cvs.sourceforge.net
This change will require new working copies to be checked out of all
repositories (so control files in the working copy will point to the
right place). We will be updating the instructions we supply, but
instructions that your team has written within documentation, etc. will
need to be updated.
cvs -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/openser co sip_server
would be changed to
cvs -d:pserver:anonymous at openser.cvs.sourceforge.net:/cvsroot/openser co sip_server
2. ViewCVS
We are moving from ViewCVS to its successor, ViewVC. ViewVC is
currently in use for our Subversion service.
3. Sync delay
Old: CVS pserver, tarballs and ViewCVS provided against a separate
server which is a minimum of three hours behind developer CVS.
New: ViewVC will be provided against developer CVS (it will be current).
CVS pserver will be provided against a secondary server (not developer
server) with a maximum expected delay of two hours.
Follow-up work is planned (this infrastructure takes us 80% of the way)
to essentially eliminate the sync delay.
</SF letter>
Bogdan-Andrei Iancu wrote:
> Hi everybody,
>
> as SF seams to have problems with CVS access, problems that cannot be
> reasonable (as time) solved, the board of the project decided to
> migrate the project repository from CVS to SVN (still being hosted on
> SF).
>
> Starting from now, all CVS access will be blocked as the migration
> process will start. The complete process may take couple of days
> (migration and SVN configuration), so please be patience - I will let
> you know as soon as public and developer access to SVN is available.
>
> thanks for understanding,
> Bogdan
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>
More information about the Users
mailing list