Menu

#25 Cannot checkout project with symbolic links

open-later
CVS/RCS (22)
2
2003-03-04
2003-02-07
Anonymous
No

When trying to checkout a project with symblic links
(soft links) to other files in other projects, I get this error
log:

Fri Feb 7 11:28:21 2003 Command - checkout
project_xyz
Fri Feb 7 11:28:21 2003 Checking out module
project_xyz
Fri Feb 7 11:28:28 2003 Error during checkout:
Fri Feb 7 11:28:28 2003 An error occured while pulling
the CVS log:
Fri Feb 7 11:28:28 2003 256

Discussion

  • Adam Kennedy

    Adam Kennedy - 2003-03-04

    Logged In: YES
    user_id=153576

    Unsure of the effects the softlinks would have on the CVS
    client.

    Until I can get access to a repository to test this,
    flagging as Later

     
  • Adam Kennedy

    Adam Kennedy - 2003-03-04
    • priority: 5 --> 2
    • assigned_to: nobody --> adamkennedy
    • status: open --> open-later
     
  • Sachin Garg

    Sachin Garg - 2003-11-13

    Logged In: YES
    user_id=242837

    One of the reasons this happens is the way CVS handles, or
    ratehr does not handle symbolic links. In order to make it
    handle symbolic links, I run a script after checkout. Now,
    the fun part is that the script is run on the remote machine
    during access using the "pserver" machanism (which is the
    only one supported by CVS monitor).

    From the Cederqvist:

    > C.1.6 How the modules file "program options" programs are run

    > For checkout, rtag, and export, the program is server-based,
    > and as such the following applies:-

    > If using remote access methods (pserver, ext, etc.), CVS will
    > execute this program on the server from a temporary
    directory.
    > The path is searched for this program.

    > If using "local access" (on a local or remote NFS file
    system,
    > i.e. repository set just to a path), the program will be
    executed
    > from the newly checked-out tree, if found there, or
    alternatively
    > searched for in the path if not.

    > The programs are all run after the operation has effectively
    > completed.

    This creates these problems. They can be resolved either if
    1) CVSmonitor allows access via locally mounted file systems
    2) CVSmonitor neglects some errors
    3) CVS runs the programs on the local machine, even when
    using "pserver" access. This is a tough one & would need the
    scripts to be availabel locally.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.