#108110 Still having problems with CVS

closed
5
2006-09-15
2006-09-05
No

In July, I submited a support request, explaining that
I was having problems with CVS. I was told that it was
probably because I needed to reset my password (because
of the recent exploit on the SF site). I replied saying
that I had done this already and that it did not solve
the problem.

Then I went away on holiday, and when I came back, my
support request has disappeared from my list of
Trackers... Yet, the problem subsists.

So here I go again...

I have some pending changes on my local machine that I
have been trying to commit to the VoiceCode CVS
repository on SF since mid-July.

I am able to checkout the project.

If I make a change to the project and do a "Synchronize
with repository", I get the following error:

---
Problems reported while synchronizing CVS Workspace. 0
of 1 resources were synchronized.
An error occursed synchronizing /VCode: The following
warnings were reported while performing the "cvs
update" command.
VCode: cvs update: cannot open directory
/VCode/Admin/UnitTests: No such file or directory.
VCode: cvs update: cannot open directory
/VCode/Environments/DevStudio: No such file or directory.
VCode: cvs update: nothing known about
Mediator/actions_C.py
---

These errors don't seem to really matter since, Eclipse
is still able to show me the differences between my
modified local copy and the CVS repository.

But if I then try to commit the changes, I get the
following error:

---
The server reported an error while performing the "cvsa
commit" command. VCode: cvs [server aborted]: "commit
requires write access to the repository"
---

But I'm project admin, so for sure I have write access
to the CVS repository!

Can you please fix this mess please? My end-users are
waiting for me to commit those important changes.

Thx

Alain Désilets
VoiceCode project admin

Discussion

  • Wayne Davison

    Wayne Davison - 2006-09-05
    • assigned_to: nobody --> wdavison
    • milestone: --> Second Level Support
    • status: open --> closed
     
  • Wayne Davison

    Wayne Davison - 2006-09-05

    Logged In: YES
    user_id=1546419

    Greetings,

    The error about not having write access to the repository is
    usually caused by trying to use a :pserver: checkout to commit
    instead of an :ext: checkout. That can be fixed by doing a new
    checkout using the :ext: (via ssh) instructions, or by changing
    the text in all the CVS/Root files to contain a valid :ext:...
    value.

    As for the error about the Mediator/actions_C.py file, that
    file was bogus, and I have removed it from the repository. I
    see no other problems with the repository. The missing
    directory errors may be caused by an existing checkout having
    incorrect Root details (it looks like the /cvsroot/voicecode
    part of the path is missing).

    SourceForge.net Support

     
  • Alain Désilets

    Alain Désilets - 2006-09-06

    Logged In: YES
    user_id=23027

    Thx wdavison,

    I had indeed changed from extssh to pserver in July because
    back then I wasn't even able to checkout with extssh and
    pserver was the only mode that worked.

    I reverted it back to extssh, and it mostly work.

    I still get the "no such file or directory..." errors
    mentioned above, but the "nothing known about..." error is
    gone and I can commit no problem.

    I guess I can live with the "no such file or directory..."
    errors, but if you have an idea of what's causing them,
    please let me know.

    Cheers

    Alain Désilets

     
  • Alain Désilets

    Alain Désilets - 2006-09-06
    • status: closed --> open
     
  • Alain Désilets

    Alain Désilets - 2006-09-06

    Logged In: YES
    user_id=23027

    > I guess I can live with the "no such file or
    > directory..."
    > errors, but if you have an idea of what's causing them,
    > please let me know.

    Oh, sorry...

    I just noticed that you DID provide some hint regarding
    that. I'll investigate them.

    Thx again.

     
  • Alain Désilets

    Alain Désilets - 2006-09-06

    Logged In: YES
    user_id=23027

    Hum... The "No such file or directory..." errors don't seem
    to be due to an old checked out project. I deleted the whole
    project, checked it out from scratch and I still get those
    errors.

    Any suggestions?

    Thx

    Alain Désilets

     
  • Wayne Davison

    Wayne Davison - 2006-09-07
    • status: open --> closed
     
  • Wayne Davison

    Wayne Davison - 2006-09-07

    Logged In: YES
    user_id=1546419

    Greetings,

    I checked out the VCode module from your repository using both
    the :pserver: and :ext: URL types, and in neither case did I
    get any errors or warnings. This makes me suspect your CVS
    tool.

    SourceForge.net Support

     
  • Alain Désilets

    Alain Désilets - 2006-09-15
    • status: closed --> open
     
  • Alain Désilets

    Alain Désilets - 2006-09-15

    Logged In: YES
    user_id=23027

    OK. Thx for looking further into this. It looks like an
    Eclipse problem then.

    Best regards,

    Alain Désilets

     
  • Wayne Davison

    Wayne Davison - 2006-09-15
    • status: open --> closed