From: "Caleb Cushing" <xenoterracide@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: trouble getting git cvsimport working
Date: Sat, 10 Jan 2009 09:35:28 -0500 [thread overview]
Message-ID: <81bfc67a0901100635i4d33c294x393a8d2dfc2b0e0d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901101524310.30769@pacific.mpi-cbg.de>
> > sh: cvs: command not found
>
>
> What's this?
does git need more than cvsps to work (I assumed my package manager
had installed all needed deps)? I installed cvs after you pointed that
out...
git cvsimport -a -v -d
:pserver:anonymous@anoncvs.gentoo.org/var/cvsroot/ gentoo-x86 -C
portage
Initialized empty Git repository in /home/portdev/cvs/portage/.git/
Running cvsps...
parse error on third token
WARNING: malformed CVS version str: Server: (unknown)
WARNING: Your CVS client version:
[Client: Concurrent Versions System (CVS) 1.12.12 (client)]
and/or server version:
[Server: (unknown)]
are too old to properly support the rlog command.
This command was introduced in 1.11.1. Cvsps
will use log instead, but PatchSet numbering
may become unstable due to pruned empty
directories.
cvs log: warning: failed to open /home/portdev/.cvspass for reading:
No such file or directory
cvs log: in directory .:
cvs [log aborted]: there is no version here; run 'cvs checkout' first
DONE; creating master branch
fatal: refs/heads/origin: not a valid SHA1
fatal: master: not a valid SHA1
fatal: You are on a branch yet to be born
checkout failed: 32768
--
Caleb Cushing
http://xenoterracide.blogspot.com
next prev parent reply other threads:[~2009-01-10 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 13:16 trouble getting git cvsimport working Caleb Cushing
2009-01-10 14:25 ` Johannes Schindelin
2009-01-10 14:35 ` Caleb Cushing [this message]
2009-01-10 14:55 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81bfc67a0901100635i4d33c294x393a8d2dfc2b0e0d@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).