From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27614 invoked by alias); 16 Jul 2016 19:56:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 27597 invoked by uid 89); 16 Jul 2016 19:56:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.8 required=5.0 tests=AWL,BAYES_50,KAM_LOTSOFHASH,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=counting, thin-pack, repos, D*github.com X-HELO: mailrelay8.public.one.com Received: from mailrelay8.public.one.com (HELO mailrelay8.public.one.com) (91.198.169.216) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sat, 16 Jul 2016 19:56:00 +0000 X-HalOne-Cookie: 2aeba6df8d88bb04a11777cb406ead9fc8fdadf8 X-HalOne-ID: 4da17990-4b8f-11e6-a0c6-b82a72cffc46 Received: from [192.168.12.101] (unknown [81.233.118.11]) by smtpfilter4.public.one.com (Halon Mail Gateway) with ESMTPSA for ; Sat, 16 Jul 2016 19:55:53 +0000 (UTC) Message-ID: <578A9120.9040904@junovagen.se> Date: Sat, 16 Jul 2016 19:56:00 -0000 From: Thomas Nilsson User-Agent: Postbox 4.0.8 (Windows/20151105) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Problem with git on cygwin64 on Windows 10 (2.8.3-1), again References: <576EE695.10509@junovagen.se> <5771494C.1010401@junovagen.se> <578A5088.200@junovagen.se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00200.txt.bz2 Eliot Moss skrev: > I know it may be grasping at straws, but I would look into the > permissions on the files. Also, I can imagine that running > a more native Windows version of git, and the cygwin version > of git, over the *same checkout* might lead to problems around > permissions and such. > Thanks for the suggestions, even if they are straws... Just to clarify, I have not used different git:s on the same repo (AFAIKR) because I know that gives problems. The example was from different clones of the same repo. Using the same trace as before, I get the following when I try to clone: > + git clone git@github.com:thoni56/cgreen.git -v -v > 21:53:25.633878 git.c:350 trace: built-in: git 'clone' 'git@github.com:thoni56/cgreen.git' '-v' '-v' > Cloning into 'cgreen'... > 21:53:25.666025 run-command.c:336 trace: run_command: 'ssh' 'git@github.com' 'git-upload-pack '\''thoni56/cgreen.git'\''' > 21:53:27.770688 pkt-line.c:80 packet: clone< 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad HEAD\0multi_ack thin-pack side-band side-band-64k ofs-delta shallow no-progress include-tag multi_ack_detailed symref=HEAD:refs/heads/master agent=git/2:2.6.5~dgit-checksum-v5-1484-gfc2423c > 21:53:27.772196 pkt-line.c:80 packet: clone< 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad refs/heads/master > 21:53:27.772217 pkt-line.c:80 packet: clone< dfb4e8922f13843d871a324286f3301a96ca74de refs/heads/move_blocked_pipe_to_failure_messages > 21:53:27.772230 pkt-line.c:80 packet: clone< 60c270419e917d4b364f1df61dff54dbcfb01972 refs/heads/reportinginfo > 21:53:27.772240 pkt-line.c:80 packet: clone< 0000 > 21:53:27.776847 shallow.c:313 shallow: prepare_shallow_info > Server supports multi_ack_detailed > Server supports side-band-64k > Server supports ofs-delta > Server version is git/2:2.6.5~dgit-checksum-v5-1484-gfc2423c > want 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad (HEAD) > want 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad (refs/heads/master) > want dfb4e8922f13843d871a324286f3301a96ca74de (refs/heads/move_blocked_pipe_to_failure_messages) > want 60c270419e917d4b364f1df61dff54dbcfb01972 (refs/heads/reportinginfo) > 21:53:27.779832 pkt-line.c:80 packet: clone> want 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad multi_ack_detailed side-band-64k thin-pack ofs-delta agent=git/2.8.3 > 21:53:27.779846 pkt-line.c:80 packet: clone> want 06543ac1ff0c4aef9187eb1ad9c4e1a9059d51ad > 21:53:27.779855 pkt-line.c:80 packet: clone> want dfb4e8922f13843d871a324286f3301a96ca74de > 21:53:27.779863 pkt-line.c:80 packet: clone> want 60c270419e917d4b364f1df61dff54dbcfb01972 > 21:53:27.779870 pkt-line.c:80 packet: clone> 0000 > 21:53:27.779887 pkt-line.c:80 packet: clone> done > done > 21:53:27.940551 pkt-line.c:80 packet: clone< NAK > 21:53:27.940825 pkt-line.c:80 packet: sideband< \2Counting objects: 7389, done. > remote: Counting objects: 7389, done. > 21:53:27.940851 pkt-line.c:80 packet: sideband< \2Compressing objects: 0% (1/137) \15Compressing objects: 1% (2/137) \15 > 21:53:27.940870 pkt-line.c:80 packet: sideband< \2Compressing objects: 2% (3/137) \15 > 21:53:27.940879 pkt-line.c:80 packet: sideband< \2Compressing objects: 3% (5/137) \15 > 21:53:27.940886 pkt-line.c:80 packet: sideband< \2Compressing objects: 4% (6/137) \15 > 21:53:27.944165 run-command.c:336 trace: run_command: 'index-pack' '--stdin' '-v' '--fix-thin' '--keep=fetch-pack 12908 on thoni64' '--check-self-contained-and-connected' > 21:53:27.947283 exec_cmd.c:120 trace: exec: 'git' 'index-pack' '--stdin' '-v' '--fix-thin' '--keep=fetch-pack 12908 on thoni64' '--check-self-contained-and-connected' > fatal: index-pack failed > 21:53:27.966219 trace.c:420 performance: 2.333912667 s: git command: 'git' 'clone' 'git@github.com:thoni56/cgreen.git' '-v' '-v' RE: permissions, what files are you thinking about? Since I can't even clone a fresh repo from any of the repos I have (giving , I'd think that it must be the git execs? They all seem alright to me. I'm not sure but I think both cygwin and Windows (10 x86_64) had some updates since I last used git. /Thomas > Regards -- Eliot Moss > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple