Avisynth CVS Services

[IanB]

As you may have noticed CVS has been borked again, hopefully with the new implementation things will be a little better. ( 2006-05-12 13:19:44 - Project CVS Service ) As of 2006-05-12 at 11:30 Pacific, the replacement CVS infrastructure has been enabled for use. Do note that there are a number of changes, including the hostname used for repository access. Refer to the site documentation for details (https://www.sf.net/docs/E04). Please report any problems you see immediately by submitting a Support Request.

( 2006-05-10 04:43:14 - Project CVS Service ) As of 2006-05-09 the developer CVS server had a disk-failure. As the new CVS infrastructure is in its final phases of rollout, we'll be deploying it, in place of the current infrastructure, by end of week. We'll be sending out an email to project administrators with further details later in the day, regarding how to access the new CVS servers and the changes that occurred with the new infrastructure.

( 2006-05-05 07:55:54 - Project CVS Service ) As of 2006-05-05 we are still waiting on all the hardware for the replacement CVS infrastructure. A few of the machines we received from our vendor had disk issues shortly after configuration, so we are vetting all the systems for issues, and reloading a few of them. The service deployment itself is running smoothly and we don't anticipate any problems other than the existing hardware issues that we are working through with the vendor. We are currently estimating a deployment for the end of next week (May 12th).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/avisynth2 co avisynth2

would be changed to

cvs -d:pserver:anonymous@avisynth2.cvs.sourceforge.net:/cvsroot/avisynth2 co avisynth2For the CVS knowledgable, you can avoid the full re-checkout by editing the appropriate CVS control files. If you don't understand what I just typed then just do the checkout!

If you find any data inconsistancies in the migrated CVS data please note it in this thread immediatly!

[Fizick]

Thanks for tip,
I manually updated copy of every "Root" file from

:ext:fizick@cvs.sourceforge.net:/cvsroot/avisynth2

to

:ext:fizick@avisynth2.cvs.sourceforge.net:/cvsroot/avisynth2

All works without re-check (good for dial-up).

[Fizick]

I commit two new files in Russian doc.
They are immediately seen at anonymous WWW CVS interface.
It is good changes of new CVS infrastructure.

[IanB]

Yes, the new infrastructure has the WEB CVS browser directly off the DEV servers, so no delay. Also the Anon CVS server updates are supposed to be every 2 hours now and should be even better when they do the next phase.

The document http://www.sf.net/docs/E04 and related links have the scoop, it is really worth a read.

[Wilbert]

Yes, the new infrastructure has the WEB CVS browser directly off the DEV servers, so no delay. Also the Anon CVS server updates are supposed to be every 2 hours now and should be even better when they do the next phase.
It took a while, but hopefully everything works again :)

edit: I see I should update the on-line documentation very soon :) I will do that coming weekend.

[Fizick]

Wilbert,
Oh-oh, new translations will be needed again :)

[IanB]

From http://sourceforge.net/docs/A04/en As of 2006-05-17 at 12:00 Pacific we synchronized the SSH keys on all of the CVS hosts. This will cause SSH key mismatch errors for most projects. Please reconfirm the new SSH key against site doc G04 (https://www.sourceforge.net/docs/G04) and then accept the new key, if it matches per normal procedure. We apologize for the inconvenience, but this should be a one-time event and make future CVS infrastructure changes more seamless.

As of 2006-05-17 at 12:00 Pacific, all CVS hosts are back up and fully operational. The disk issue on one of the hosts forced us to swap it out for a backup host to send the hardware back to the vendor for further troubleshooting to identify the cause of the continual hardware issues with the systems. As we had to switch to the alternate host, a very small number of checkins may not be present on the host. We recommend that affected users make a fresh checkout, copy their working copy on top of the fresh checkout, and then commit those changes back. If you didn't make any changes in the 20 minutes or so prior to the outage, this should be unnecessary.

[IanB]

More from http://sourceforge.net/docs/A04/enOn 2006-05-22 at 12:45 Pacific the scheduled CVS outage was completed successfully and access to service was fully restored. All issues regarding access should be reported via Support Request, as usual.On 2006-05-22 there will be a one hour outage of CVS, starting at 12:00 Pacific to allow for the deployment of an automated stale-lock file removal feature.

[Fizick]

IanB,
I see, you start to use new CVS architecture. ;)
Thanks!

[IanB]

If only the SF people would stop fiddling with it, they are like a kid with a new shiney toy.On 2006-05-24 Site Search functionality will be offline for functionality upgrades from 9:00AM to 11:00AM Pacific.On 2006-05-23 CVS will be taken down between 12:00 and 4:00 Pacific for upgrades. No single host is expected to be down for more than approximately thirty minutes

[d'Oursse]

seriously, don't you want to go somewhere else? SourceForge (cvs) is down again this morning. The number of times the cvs is down, corrupted, etc... since the beginning of year (and even before) is just amazing.

Right now, i'm not confident at all about the services that SourceForge proposes.

[IanB]

Note some scheduled downtime

http://sourceforge.net/docs/A04/en

( 2006-09-27 09:41:13 - ) On 2006-09-28 beginning at 09:00 Pacific, the CVS servers will be down briefly for scheduled maintenance. Each machine's downtime should be a half hour or less, and each project should have access to one of its two CVS-access methods at all times. All systems should be back up by 11:00 Pacific.

[Fizick]

I can not access CVS for several days (aouthization error).
( I did not try do it for a month).
Anybody know why ? :)
I did not change any settings in TortuiseCVS, and I have access to sourceforge acount.

[Wilbert]

Hmm, it works fine for me. I recall that i had to change my password a few weeks back, but i forgot why. Perhaps it has something to do with it?

edit:
( 2008-03-07 05:25:00 - Project CVS Service, Project Shell Service, Project Subversion (SVN) Service, SourceForge.net Web Site ) On 2008-03-06, during a routine security audit, SourceForge.net staff identified a deficiency in systems data control. We are unaware of any exploitation of this data, which was present in encrypted form. In addition to removing the data, as a preventative measure we have also forced password changes for all SourceForge.net user accounts.
http://sourceforge.net/docs/A04/

[Fizick]

Thanks,
With updated password CVS works fine.

[IanB]

CVS Downtime!On 2008-09-30 (Tuesday), project CVS service will be taken offline at 17:00
UTC for not more than 8 hours to permit the migration of service to the new
Chicago datacenter. Servers have been prepared and locally tested already;
the migration event will be used to copy data deltas from the old
datacenter to the new, and cutover CVS service DNS to point at the new
servers. During this migration window read-only pserver-based CVS access,
SSH-based developer CVS access, ViewVC web-based repository access for CVS,
and other CVS-related facilities will be completely offline. CVS is the
final major SourceForge.net service left to be migrated to our new
California datacenter.

Thank you,

Jacob Moorman
Director of Operations, SourceForge.net