User Login    
 + Register
Bookmark and Share
  • Main navigation
Login
Username:

Password:

Remember me



Lost Password?

Register now!







Re: SourceForge CVS Changes

Joined:
2004/4/7 4:49
From Memphis, TN, USA
Group:
Forge Developers
Registered Users
Posts: 107
The new ViewCVS browse URL for the modules is:

http://xoops.cvs.sourceforge.net/xoops/modules/

Then I've set the CVS name to be the same as the short name on all projects (at least I've tried to -- some might not match exactly). So for example, SmartContent would be like this:

http://xoops.cvs.sourceforge.net/xoops/modules/smartcontent/

Is that what you're looking for?

Posted on: 2006/6/11 9:19
_MD_TRANSFER_DESC _MD_TRANSFER


Re: SourceForge CVS Changes
Just can't stay away
rank4823bd1d117e3.gif
Joined:
2004/7/22 10:19
Group:
Registered Users
Forge Developers
Posts: 81
@Glen

hello,

i'm trying to change confs for dev.xoops.org repository (browse module's CVS from one module's project)

What should be these new settings ?
Currently, old ones are :
Quote:

CVS URL like cvs.sourceforge.net : cvs.sourceforge.net
CVS Script like viewcvs.cgi: viewcvs.py/xoops/modules


i've tried several combinations, but failed.

thanks for your help with repairing dev.xoops.org CVS brownse
marco

Posted on: 2006/6/11 4:37
_________________
QA team
Xoops France team member
_MD_TRANSFER_DESC _MD_TRANSFER


Re: SourceForge CVS Changes

Joined:
2004/4/7 4:49
From Memphis, TN, USA
Group:
Forge Developers
Registered Users
Posts: 107
Additional information from SourceForge
Here is the full text of the message I got from sourceforge, explaining the what and why of the CVS changes:

Quote:

Greetings,

You are receiving this mail because you are a project admin for
a SourceForge.net-hosted project. One of our primary services,
CVS, suffered a series of interrelated, critical hardware failures
in recent weeks. We understand how frustrating this CVS outage
must be to you and your users; however, our top priority remains
preservation of the integrity of your data.

The series of CVS hardware failures prompted us to expedite the
deployment of planed improvements to our CVS infrastructure,
drawing upon much of the knowledge that we gained from our
Subversion deployment. Our improved CVS service architecture,
which we plan to deploy tomorrow afternoon (2006-05-12), will
offer greater performance and stability and will eliminate several
single points of failure.

The Site Status page (https://www.sf.net/docs/A04) will be
updated as soon as the new infrastructure is rolled out. In the
interim, please read the important information provided below
to learn about how these changes will affect your project.


Summary of changes, effective 2006-05-12:


1. Hostname for CVS service

Old: cvs.sourceforge.net

New: PROJECT_UNIX_NAME.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@cvs.sourceforge.net:/cvsroot/gaim co gaim

would be changed to

cvs -d:pserver:anonymous@gaim.cvs.sourceforge.net:/cvsroot/gaim co gaim



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.



4. Read-only rsync service

As a new service offering, we are now providing read-only rsync access
against developer CVS. This allows projects to efficiently make
on-demand backups of their entire CVS repository.

All projects should be making regular backups of their CVS repository
contents using this service.



5. Nightly tarball service

Nightly tarball service is being dropped in lieu of read-only rsync
service. Projects which currently depend on nightly tarballs for
repository backups will need to begin using rsync to make a backup copy
of their repository contents.

We see this as a major functional improvement. For a number of reasons,
tarballs have fallen out of sync with the data in the repository at
times in the past few years. Tarballs required a substantial amount of
additional disk, and I/O to generate. The move to read-only rsync
allows backups to be produced on-demand, with an update frequency chosen
by the project.



6. Points of failure

In the past, developer CVS service for all projects was provided from a
single host. CVS pserver service was provided from individual backend
heads based on a split of the data.

Under our new design, developer CVS and most of our CVS-related services
are provided from one of ten CVS hosts (count subject to increase with
growth). Each host is independent, and makes a backup copy of the
repository data of another host (which is used to provide the pserver
CVS service).

Failure of a single host will impact only the availability of data on
that host. Since the data is split among a larger number of hosts, the
size of data impacted by an individual host outage is substantially
smaller, and the time required for us to restore service will be
substantially shorter.

This rapid architecture change has been made possible specifically using
the research we performed for our recent launch of Subversion service.
We've applied our best practices, produced a substantial amount of
internal documentation, and kept an eye toward maintainability.
This effort has allowed us to deploy this new architecture quickly
once hardware was received, and will permit us to quickly scale
this service horizontally as growth and demand requires.



Many other minor improvements have also been made to improve the service
offering and make it less trouble-prone. The most important of which are
listed above. For a full description of the new service offering, and
for information on how to use the services described above, please refer
to the site documentation for the CVS service after the service has been
launched: https://www.sf.net/docs/E04


Thank you,

The SourceForge.net Team

Posted on: 2006/5/13 22:23
_MD_TRANSFER_DESC _MD_TRANSFER


Re: SourceForge CVS Changes

Joined:
2004/4/7 4:49
From Memphis, TN, USA
Group:
Forge Developers
Registered Users
Posts: 107
How to change your existing sandboxes to use the new CVS structure

Background info
Every CVS sandbox has hidden directores named "CVS" under each directory within your sandbox. These hidden CVS directories have the control files that remember the state of your sandbox. The Root file contatins a single line with the CVSROOT you used to check out the files.

What to change
You need to change *every* Root file in your sandboxes to the new CVSROOT. The old root might looks like:
Quote:
:ext:gstarrett@cvs.sourceforge.net:/cvsroot/xoops
** or **
:ext:gstarrett@cvs.sf.net:/cvsroot/xoops


In either case, they need to be changed to:

Quote:
:ext:gstarrett@xoops.cvs.sourceforge.net:/cvsroot/xoops


How to change
** Make a backup of your sandbox ** If you goof up the change, it's good to have an extra local copy handy!

The easiest way to change all these files is to use an in file replace command. WinCVS ( http://www.wincvs.org/ ) has a Change CVSROOT macro to do just that, and is the simplest method.

If you don't use WinCVS, you can also use any of a number of utilities. I like to use UltraEdit ( http://ultraedit.com/ ) myself. The following example shows the dialog settings when using UltraEdit, you should be able to adapt these to pretty much any in-file replace utility.

Using UltraEdit, under the Search menu, choose Replace in Files.
Find:          :ext:gstarrett@cvs.sourceforge.net:/cvsroot/xoops

Replace With
:  :ext:gstarrett@xoops.cvs.sourceforge.net:/cvsroot/xoops

In Files
/TypeRoot

Directory
:     C:SandboxesXoopsModule


Once you have updated all the Root files, you should be able to update, commit, etc. normally just as before the change.

Posted on: 2006/5/13 22:21
_MD_TRANSFER_DESC _MD_TRANSFER


SourceForge CVS Changes

Joined:
2004/4/7 4:49
From Memphis, TN, USA
Group:
Forge Developers
Registered Users
Posts: 107
SourceForge has rolled out their "new" CVS Architecture. It will require changes by each developer using CVS.

The full discussion of exactly what canged is on the Site Status page https://sourceforge.net/docs/A04. I will post additional information in a seperate message.

[h2]The change required by XOOPS developers[/h2]
The new infrastructure changes the host from which ALL people access CVS. The new format is {project}.cvs.sourceforge.net, so in our case it is xoops.cvs.sourceforge.net.

You have two options:

1) Re-checkout each sandbox you work on using the new CVSROOT as listed in the dev wiki [url http://dev.xoops.org/modules/phpwiki/index.php/HowToUseTheCvs "XOOPS Module Development CVS Instructions"].

You will have to manually move any updates to those files over from your old sandboxes.

** OR **

2) Update each Root file in your sandbox with the new CVS root.

If you have a lot of modules, or a lot of pending changes, I recommend option 2. I will post a quickie howto later tonight or tomorrow (unless someone else beats me to it).

And the new CVSROOT for developers is...
Quote:
:ext:YourSFUserName@xoops.cvs.sourceforge.net:/cvsroot/xoops


NOTE: The Developer wiki page [url http://dev.xoops.org/modules/phpwiki/index.php/HowToUseTheCvs "XOOPS Module Development CVS Instructions"] used to show a shortened "cvs.sf.net". Using xoops.cvs.sf.net does NOT work.

Posted on: 2006/5/13 20:57
_________________
Glen Starrett
XOOPS.org CVS Manager
_MD_TRANSFER_DESC _MD_TRANSFER







You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create pdf.
You cannot get print page.

[Advanced Search]