CVS source acces
 

Since Titanium release, we don't have any cvs acces to the source.
I have try Development and LiveCompat branch with no clue...
CVS has no problem with his services and current release are automatic build.

I ended up concluding from it that the sources of titanium are on a new branch.
Please, a dev can just give the name of that branch ? Or if can't do, just explain why ? Or explain where is the problem if i'm wrong ?

I specify with the bad thinkers, that it is not a criticism but a request for information.

as far as I can tell, this is still source forge's issue. I have checked several times, and both the Development and the LiveCompat branches have our code in them on the SF development CVS server... there is apparently still something wrong with their public server...

I just forced a sync into their server, so maybe it will help, but I wouldent hold my breath... looks like we prolly need to bitch at sourceforge about it.

If i understand, only anonymous connect is wrong :(

Can be to organize a petition on their site while asking has all the members of EQEMULATOR of going to sign it ?
I see with donation's problem how sourceforge support is ... slow...

Sync with server don't change anything :(
I think , i try to ask from sourceforge, perhaps they found the bug in one or two month :)

i really would love to have access to daily server releases...can we to do anything for help with this issue?

I have received this letter from sourceforge.net

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

I have try :

but don't work (wincvs return code 1)
Perhaps need some time, i have this result with old config also ;) .

Edit: yes for me cvs is'nt available, i'll try in more time.

CVS Service still isnt done, u can check status here

https://sourceforge.net/docs/A04

and u can see that now the status of CVS Service is:

Project CVS Service: Partial Outage In-Progress Last updated: 2006-03-30 Pacific

Thats working fine now with :
thanks for info arex :)

Sorry to bump something so old, but I cannot find an answer anywhere else - perhaps this is as good a place as any.

From: http://eqemulator.net/download.php

I am assuming this means no more Sourceforge for the latest code branches? There is a column on downloads.php that says "Source Code", but it looks like one huge file. Pardon my noobness (I am not a coder, but inquisitive just the same), but how do you use this file or extract the data within to be the .h/.cpp files we can work with?

Apologies again, but I'd like to take a look at some issues and see if I can learn/help out a little.

TIA,
J

Any hints here at all? Not to be a pest, but I want to make sure I am working with "official" code. I have found another 840 source code that is in a workable format, I'm just not sure it is official EQEmu release 840.

Please, point me to a post or anything that explains how to use the Source provided on the downloads page. I am not asking for a C++ tutorial, just how to use this ginormous source file. :)

Thanks again.
J

The source code on the download page is from the CVS; however, as the developers do most of there development on Linux, sometimes, the windows or (Visual Studio) solutions are not compeltely up-to-date. I have posted on my website, http://eqemu.sesmar.net, the same thing that can be found on the Download page here with the exception that I have fixed the solution to work properly with Visual Studio 2003 and 2005. The code is exactly the same, all I have done to it is add the few missing files to the projects and tested it to compile.

I hope this helps you in some way.

Yes indeed, that is more than perfect, because that is the source I am using. :D :D :D

(didn't know if it was proper to mention, I am new to the etiquette here, and hate being scolded heh).

Thank you much for that effort,
J