Has anybody recently tried using the Amiga CVS client with Sourceforge's read/write CVS service? It was working.. um.. earlier in the year I suppose... in desperation I tried doing a new checkout and I'm getting the same error.
cvs checkout: :ext: method not supported by this port of CVS cvs [checkout aborted]: try :server: instead
Changing to :server: used to work, but now gives:
Quote:
SSH: Error reading public key packet (0, ). cvs [checkout aborted]: could not start server via rcmd(): Bad file descriptor
Anybody got a solution? I see SF have some SSH key service thing, but I understand that shouldn't be required (no idea if it works with our CVS client anyway - given the amount of trouble I have with CVS on AmigaOS I'd be very surprised if it did)
It worked so maybe you could try something similar. I've never had any luck with the -z option and for whatever reason the CVS program doesn't seem as stable as it was previously. Using CVS several times in succession can cause a crash or TCP/IP lockup on my system now. The last time I tried it (months ago) it was less problematic.
Doesn't seem to be working unfortunately. I've uploaded the public part of the key but still getting the public key error message (yes I have waited 30 mins for sf's replication). Snoopy is not reporting anyting of note, just a load of env-vars that don't look relevant.
I've just updated my CVS client as it was a couple of minor revisions old, but that hasn't helped.
@Chris Yes. You're right. I checked in a couple of minor bugfixes to the jabberwocky CVS repository in September but can't even check out the code with my password any more. I get the same error as you got. As of now, I'm locked out and can't make any changes to the few projects I contribute to. I need a solution to this too.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
@Chris I visited the SourceForge site and checked recent outages. There was a CVS outage for some projects that was supposedly fixed on Oct 22. I left a message about our problem but don't know if it will do any good. My message included the fact that I'm an Amiga user. It probably wouldn't hurt if you also notified them of the problem as an Amiga user. Maybe they'll fix it or tell us what needs to be done to regain access.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
@Chris I still can't get CVS access to my SourceForge projects. Surely there are other devs still using CVS with Amigas. I can't believe we are the only 2 people with CVS access problems.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
I raised a support ticket and they asked for more info today (which is fair enough; I provided literally no information originally) so they can "reproduce the problem".
I have pointed them to the CVS client and suggested they might like to try it under emulation :)
Annoyingly the :server: method isn't supported under Cygwin's CVS so it is impossible to check if the same thing is happening there (:ext: works fine)
@Chris I guess sf.net is too busy making money now Next they'll be telling people they only support access from Windows. No wonder the YAM team moved the YAM project out of SourceForge.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
Unless you are forced to use CVS for some reason I would suggest using SVN (Subversion) instead on sourceforge as it's better supported on AmigaOS, easier to use and it is "CVS done right".
For me at least the sourceforge CVS has never worked very well, no matter what OS I use always getting only a few files and then failing with some message about unexpected dying gasps from sourceforge CVS server (haven't tried recently though to see if they've fixed this issue).
Unless you are forced to use CVS for some reason I would suggest using SVN (Subversion) instead on sourceforge as it's better supported on AmigaOS, easier to use and it is "CVS done right".
There are some cases where projects have been placed in a CVS repository and more or less abandoned by original authors & admins. It might make sense to move projects to SVN but it's unlikely to happen in some cases. I'm not a very good programmer and have just been adding bug fixes in a couple of CVS projects over the past year or two, so it won't really bother me to abandon those projects too. Quote:
For me at least the sourceforge CVS has never worked very well, no matter what OS I use always getting only a few files and then failing with some message about unexpected dying gasps from sourceforge CVS server (haven't tried recently though to see if they've fixed this issue).
I had the reverse problem until I switched to a high-speed connection. With dialup, CVS worked flawlessly but SVN would fail after sending a few files. It would take a dozen attempts to check out a large project like YAM with SVN. The SVN servers seem to need fast responses from the client program.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450