- NSIS Discussion
- CVS change log problems ???
Archive: CVS change log problems ???
veekee
16th June 2003 22:35 UTC
CVS change log problems ???
Hi all,
For some days, I have some problems using the changelog from the dev web site !
In fact, when clicking on links, now, tha displayed file tells me no changes occured on the file !
Would it be possible to correct this "bug" (i'm using that feature a lot) ?
Regards
Julien
veekee
16th June 2003 22:36 UTC
PS : i know you do not developp cvs : i just mean that, as this worked before, this should work now ! The only think would be to search what's wrong now ;) :D
ramon18
17th June 2003 08:01 UTC
It's working
Hi,
I don't understand why you found problems, for me is working fine.
good luck,
Ramon
Sunjammer
17th June 2003 08:18 UTC
It's not working on the most recent changes, older ones still work fine. This was my experience last night when using the change log page anyway.
ramon18
17th June 2003 08:49 UTC
Well the last changelog entry was updated yesterday 22:00 GMT
Sunjammer
17th June 2003 08:57 UTC
On this page try clicking InstallerOptions.cpp under the heading "2003-06-16 18:49 Ramon (ramon18)" and see if you see what my screenshot shows.
[edit]In fact I've just noticed that the testlink.ini and testlink.nsi file links are broken too, although differently. E.g. the testlink.ini link takes me to a page that says "/cgi-bin/viewcvs.cgi/nsis/NSIS/Contrib/InstallOptions/testlink.ini: unknown location".[/edit]
ramon18
17th June 2003 09:01 UTC
Humm
You right :(
But this is a problem in cvs browsing/diffing system and not changelog
cyas,
Ramon
Sunjammer
17th June 2003 09:09 UTC
Oh agreed, but it's still a problem.
[edit]There's a message on the sf.net status page about changes to cvs access due to hardware limitations which might be the cause of this problem.
( 2003-06-13 08:17:23 - Project CVS Services ) The SourceForge.net team is aware of the continued performance issues afflicting project CVS services. While a portion of the work needed to alleviate these issues has been completed, we are currently waiting for the implementation of new hardware to complete this work; this is expected to occur in the month of August. In the mean time, the following steps will be taken by SourceForge.net staff: developer (SSH) CVS access will not be changed; pserver-based CVS access from the project shell servers (i.e. from cron jobs) will not be changed, but the overall cap of pserver connections from the shell will be lowered to a more reasonable level; pserver-based CVS access from external hosts (i.e. not the project shell server) will be served against the backup CVS server, which contains data roughly 24 hours older than that on the primary CVS server; ViewCVS access will be provided using the backup CVS server (data shown by ViewCVS may be older than the current data in the repository). These changes will be transparent to users and will not require any configuration changes on your part. These measures are temporary and will be removed pending the successful completion of our work to improve performance on the primary CVS server. It is our expectation that offloading ViewCVS services and pserver-based CVS access to the backup CVS server will bring developer CVS performance back to a reasonable level. Should you have questions or concerns regarding this matter, please contact the SourceForge.net team by submitting a Support Request. [/edit]
Joost Verburg
17th June 2003 11:45 UTC
That's right. Public CVS / Browse CVS access has a delay of up to 24 hours, because it runs on the backup CVS server.
The changelog is being generated from the development server, so it displays the latest changes that do not yet exist on the backup server.
So you might not be able to see the differences of files uploaded less than 24 hours ago.
We'll have to deal with this situation for a few weeks, until SourceForge gets new hardware.