[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Export files by specific revision number

From: Spiro Trikaliotis
Subject: Re: Export files by specific revision number
Date: Fri, 23 Sep 2005 19:16:35 +0200
User-agent: Mutt/1.5.9i

Hello Larry,

* On Fri, Sep 23, 2005 at 12:06:23PM -0400 Larry Jones wrote:
> Spiro Trikaliotis writes:
> > 
> > Anyway, I ask myself why export is not allowed with a non-tag "-r"
> > parameter. In the cederquist, I did not see any mention of this
> > restriction.
> Because exporting a single file is a very unusual operation.  The
> normal use of export is to export a set of files and it doesn't make
> any sense to specify a numeric revision for more than one file.

Yes, I know what the normal use of export is.

Ok, I'll tell you for what I need this behaviour of export:

Some tool (take, for example, a debugger) has the ability to
automatically check out the files used to build the executable to be
debugged out of the CVS repository.

The tool wants to check out the files one by one, with the given
revision. Because this tool neads read-only access only, the CVS/
directories are superfluous, thus, "cvs co" is not the preferred
solution. On the other hand, in the current form, export only allows for
symbolic tags, thus, this is not usable, either (or the CVS/ directories
would have to be deleted afterwards).

The solution given by Rick in a previous mail has another drawback: It
does not allow for read-only checkouts, as we would have to tag the
repository. :(

This is the reason why I am asking for such a change in behaviour.

* On Fri, Sep 23, 2005 at 12:44:16PM -0400 Larry Jones wrote:
> Spiro Trikaliotis writes:
> > 
> > I ask myself if the CVS developers would accept a patch which add
> > another option to "cvs export" to be allowed to specify a specific
> > revision number with -r (instead of a tag, which is required now for
> > "cvs export")?
> There's precedent for that in the admin command: many of the options
> that take a revision will allow a numeric revision for a single file but
> not for multiple files.  The existing test is somewhat simple-minded,
> though, and wouldn't work for export since export works on the
> repository rather than a working directory.

So, I assume this means "if the patch is clean and mean, we would accept
it", does it?

So, if I export a whole module (or anything more than just one file), a
symbolic tag has to be given. If I export only one single file, a
revision would be allowed. Would that be an acceptable solution?

> > BTW: Even cvs -H export does not mention that -r must be given a
> > symbolic tag. Event this command mentions tag or revision.
> Fixed.

This is not the fix I had in mind. ;)

> > address@hidden:~/cvs-source$ cvs -z3 -d:ext:address@hidden:/cvsroot/cvs co 
> > ccvs
> > Permission denied (publickey,keyboard-interactive).
> > cvs [checkout aborted]: end of file from server (consult above messages if 
> > any)
> > address@hidden:~/cvs-source$
> It works for me.  You may want to try a manual ssh in verbose mode to
> see what's going wrong:
>       ssh -v address@hidden cvs server

Yes, I already tried this. Here are the last lines of output:

debug1: Offering public key: /home/trikalio/.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey,keyboard-interactive).

I am never prompted for a password. Anyway, for other servers, this
works perfectly.

I once had this problem with other servers, too. The output was exactly
the same. The reason was that the server did not allow password
authentification, only public-key. Could this be the case here, too?


Spiro R. Trikaliotis                               

reply via email to

[Prev in Thread] Current Thread [Next in Thread]