NSIS Update

The NSIS Update displays almost everytimes I call it the following error:

Initializing CVS Update...
cvs95 update: Empty password used - try 'cvs login' with a real password
cvs95 [update aborted]: Error reading from server cvs.sourceforge.net: 0 

I use the latest CVS package (yes, sometimes the update works!).
Is this a bug?

Konrad

No, it's SourceForge having problems supplying CVS access to millions of open source users.

But normally you need a password for the CVS access to sourceforge (i think it's guest).
And i didn't have any problems accessing other CVS sources from sourceforge via WinCVS.

I think you should at least do not display the following status line
cvs95 update: Empty password used - try 'cvs login' with a real password
What about a notice, that Sourceforge is busy and that the user should try later?

It's a guest account, and it's limited on SourceForge. It fails with WinCVS and TortoiseCVS too sometimes. It's not limited for your own projects when you supply a login name.

I have never ever been able to download the CVS trough NSIS Update. But if it's not limited for your own projects when you supply a login name, wouldn't it be nice if you could just give the updater a username and password? Since I, among others, do have a sourceforge account.
And, if so, the username and password must be kept when the CVS is downloaded and installed.

None of you have developer access to the NSIS repository. That won't help.

B.T.W. What's the difference between the nightly-build-zip and the CVS version?

So why not downloading the zip-version when the CVS refuses after some tries?

CVS just gives you the most updated version. The nightly ZIP is updated about 3 times a day so it's not always the most updated version.

And CVS merges changes too.

Originally posted by virtlink
wouldn't it be nice if you could just give the updater a username and password?

We'd need a user that had read-only permissions and I don't think we can assign that to a user name on sf.net and so I think we'd need the help of sf to do something like that. However I'm pretty sure they'd deny that request for the very reason that CVS access is restricted in the first place, in order to lessen the load on the sf servers.

I agree, they will deny it.

virtlink, if you have never been able to get a CVS version, you might have used a snapshot and not an official release. The snapshots contain an internal server name that doesn't work on the internet.

However, the latest NSIS Update version automatically fixes this issue, so it should work now.