From: Pavel Roskin <proski@gnu.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Bertrand Jacquin <beber.mailing@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: cvsimport weird
Date: Wed, 17 May 2006 23:59:31 -0400 [thread overview]
Message-ID: <1147924771.32050.40.camel@dv> (raw)
In-Reply-To: <46a038f90605171954n7e75ee64t412b22e8d405d909@mail.gmail.com>
On Thu, 2006-05-18 at 14:54 +1200, Martin Langhoff wrote:
> On 5/18/06, Bertrand Jacquin <beber.mailing@gmail.com> wrote:
> >
> The cvs server is strange -- buggy probably. cvsps thinks it is old,
> but it is not even returning a version string. Is it really cvs?
The version reporting is working for me:
$ cvs -d :pserver:anonymous@anoncvs.enlightenment.org:/var/cvs/e version
Client: Concurrent Versions System (CVS) 1.11.21 (client/server)
Server: Concurrent Versions System (CVS) 1.11.17 (client/server)
But I can reproduce the problem with git-cvsimport. git main branch,
cvsps 2.1.
I'm quite sure that it's a bug in cvsps. It displays such things on
x86_64, but works properly on 32-bit PowerPC.
x86_64:
$ cvsps --cvs-direct -A -u --root :pserver:anonymous@anoncvs.enlightenment.org:/var/cvs/e e17
connect error: Network is unreachable
WARNING: malformed CVS version: no data
WARNING: malformed CVS version str: (UNKNOWN CLIENT)
WARNING: Your CVS client version:
[(UNKNOWN CLIENT)]
and/or server version:
[(UNKNOWN SERVER)]
ppc:
$ cvsps --cvs-direct -A -u --root :pserver:anonymous@anoncvs.enlightenment.org:/var/cvs/e e17
cvs_direct initialized to CVSROOT /var/cvs/e
cvs rlog: Logging e17
cvs rlog: Logging e17/CVSROOT
cvs rlog: Logging e17/apps
cvs rlog: Logging e17/apps/e
cvs rlog: Logging e17/apps/e/client
...
Both are cvsps 2.1 on Fedora Core 5.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-05-18 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 1:00 cvsimport weird Bertrand Jacquin
2006-05-18 2:54 ` Martin Langhoff
2006-05-18 3:59 ` Pavel Roskin [this message]
2006-05-18 5:44 ` Pavel Roskin
2006-05-18 5:56 ` YOSHIFUJI Hideaki / 吉藤英明
2006-05-18 9:33 ` Bertrand Jacquin
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=1147924771.32050.40.camel@dv \
--to=proski@gnu.org \
--cc=beber.mailing@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.