From: David Rothenberger <daveroth@acm.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] Git et al
Date: Sat, 19 Jul 2014 23:47:00 -0000 [thread overview]
Message-ID: <53CB03BE.7030107@acm.org> (raw)
In-Reply-To: <20140719072941.GA17830@dinwoodie.org>
On 7/19/2014 12:29 AM, Adam Dinwoodie wrote:
> On Tue, Jun 10, 2014 at 11:20:41PM -0500, Yaakov Selkowitz wrote:
>> On 2014-06-10 17:36, Adam Dinwoodie wrote:
>>> The only outstanding issue with my build is that git-cvs wasn't working.
>>> That seemed to be down to my build environment, as my attempts to build
>>> the source code available via the Cygwin mirrors showed the same
>>> behaviour, but those binaries work as expected.
>>
>> Are you only testing this with the Cygwin CVS repo? Have you tried
>> this with any other repos? For example:
>>
>> :pserver:anoncvs@cygwin.com:/cvs/cygwin-apps setup (Cygwin setup)
>> :pserver:anoncvs@cygwin.com:/cvs/cygwin htdocs (Cygwin website)
>
> I've just dusted off this job, and although I was still unable to get
> Git v1.8.5.2 working, bumping up to the latest v2.0.2 has had
> considerably more success.
>
> There are a few things to iron out yet: I've only checked the 32-bit
> build so far, and I'm using a borrowed computer at the moment so I need
> to make sure I can recreate the results on my machine. I've also only
> done very mainline testing thus far on this build, although the test
> suite is running as I write this email.
>
> I've still not been able to clone the Cygwin source code from CVS --
> I've been testing by cloning the cygwin-apps repo Yaakov referenced
> above -- but the errors look like a version incompatibility, and I don't
> think there's much I can do about that. If someone who knows more about
> CVS and Git could take a look at the output and confirm that hypothesis,
> I'd be grateful:
>
> $ git cvsimport -v -d :pserver:anoncvs@cygwin.com:/cvs/src src
> Initialized empty Git repository in /home/add/test/.git/
> Running cvsps...
> WARNING: malformed CVS version str: Server:
> WARNING: Your CVS client version:
> [Client: Concurrent Versions System (CVS) 1.12.13 (client/server)]
> and/or server version:
> [Server: ]
> 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.
I have been using git 2.0.2 that I built myself for a while now, so I
tried this command using my copy. FWIW, the import works just fine with
my x86_64 build, but fails with the same messages you get with the i686
build.
--
David Rothenberger ---- daveroth@acm.org
next prev parent reply other threads:[~2014-07-19 23:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 20:02 Adam Dinwoodie
2014-01-11 20:04 ` Adam Dinwoodie
2014-01-13 9:25 ` Corinna Vinschen
2014-01-13 21:32 ` Eric Blake
2014-01-13 23:59 ` Adam Dinwoodie
2014-01-15 11:06 ` Adam Dinwoodie
2014-01-17 18:42 ` Balaji Venkataraman
2014-01-17 18:48 ` Christopher Faylor
2014-01-17 22:58 ` Balaji Venkataraman
2014-01-24 14:25 ` Eric Blake
2014-01-29 11:53 ` Adam Dinwoodie
2014-01-29 16:54 ` Yaakov (Cygwin/X)
2014-01-29 17:07 ` Adam Dinwoodie
2014-01-30 10:00 ` Yaakov (Cygwin/X)
2014-01-29 17:45 ` Achim Gratz
2014-01-29 19:33 ` Jan Nijtmans
2014-01-29 19:56 ` Achim Gratz
2014-06-10 22:00 ` Yaakov Selkowitz
2014-06-10 22:36 ` Adam Dinwoodie
2014-06-11 3:55 ` Achim Gratz
2014-06-11 4:23 ` Achim Gratz
2014-06-11 4:20 ` Yaakov Selkowitz
2014-07-19 7:29 ` Adam Dinwoodie
2014-07-19 13:54 ` Christopher Faylor
2014-07-19 23:47 ` David Rothenberger [this message]
2014-07-21 7:46 ` Adam Dinwoodie
2014-08-04 21:41 ` Adam Dinwoodie
2014-08-13 19:12 ` Adam Dinwoodie
2014-08-13 19:37 ` Eric Blake
2014-08-15 4:25 ` Eric Blake
2014-08-15 4:46 ` Marco Atzeri
2014-08-15 8:25 ` Adam Dinwoodie
2014-08-15 8:31 ` Adam Dinwoodie
2014-08-15 7:05 ` Yaakov Selkowitz
2014-08-20 20:19 ` Adam Dinwoodie
2014-08-20 22:19 ` Yaakov Selkowitz
2014-08-18 18:38 ` Eric Blake
2014-09-21 12:57 ` Andrew Schulman
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=53CB03BE.7030107@acm.org \
--to=daveroth@acm.org \
--cc=cygwin-apps@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).