{"thread":{"id":"43344","subject":"Re: [git failure] failure pulling latest Linus tree","startedAt":"2006-10-25T16:13:23Z","lastAt":"2006-10-25T17:36:54Z","messageCount":4,"participants":["H. Peter Anvin","Junio C Hamano","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"297929","messageId":"20061025161323.GF11916@pasky.or.cz","threadId":"43344","inReplyTo":"453F8630.2000608@zytor.com","subject":"Re: [git failure] failure pulling latest Linus tree","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-10-25T16:13:23Z","receivedAt":"2006-10-25T16:13:23Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, Oct 25, 2006 at 05:43:44PM CEST, I got a letter\nwhere \"H. Peter Anvin\" <hpa@zytor.com> said that...\n> HOWEVER, git 1.4.3 seems to have been bad chicken.  When we ran it we \n> got a neverending stream of segfaults in the logs.\n\nCould you provide some details, please? Ideally a backtrace or\nsomething? Also, it might be a good idea to use 1.4.3.2 since it fixes a\nproblem with compatibility of git-daemon and older git clients.\n\nThanks,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\n#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj\n$/=unpack('H*',$_);$_=`echo 16dio\\U$k\"SK$/SM$n\\EsN0p[lN*1\n"},{"id":"298724","messageId":"453F9B0D.1050409@zytor.com","threadId":"43344","inReplyTo":"20061025161323.GF11916@pasky.or.cz","subject":"Re: [git failure] failure pulling latest Linus tree","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2006-10-25T17:12:45Z","receivedAt":"2006-10-25T17:12:45Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Petr Baudis wrote:\n> Dear diary, on Wed, Oct 25, 2006 at 05:43:44PM CEST, I got a letter\n> where \"H. Peter Anvin\" <hpa@zytor.com> said that...\n>> HOWEVER, git 1.4.3 seems to have been bad chicken.  When we ran it we \n>> got a neverending stream of segfaults in the logs.\n> \n> Could you provide some details, please? Ideally a backtrace or\n> something? Also, it might be a good idea to use 1.4.3.2 since it fixes a\n> problem with compatibility of git-daemon and older git clients.\n> \n\nI'm afraid I can't anymore since I've flushed those binaries.  1.4.3.2 \nworks fine, it seems, but we hadn't gotten that update until yesterday.\n\n"},{"id":"296199","messageId":"7v3b9ce1tk.fsf@assigned-by-dhcp.cox.net","threadId":"43344","inReplyTo":"453F8630.2000608@zytor.com","subject":"Re: [git failure] failure pulling latest Linus tree","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-10-25T17:35:03Z","receivedAt":"2006-10-25T17:35:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"H. Peter Anvin\" <hpa@zytor.com> writes:\n\n> For some reason which we haven't been able to track down yet, the\n> recent load imposed by FC6 caused zeus1's load to skyrocket, but not\n> zeus2's... it's largely a mystery.\n\nWould kernel.org prefer RPM cut on a FC6 box now?\n\n> HOWEVER, git 1.4.3 seems to have been bad chicken.  When we ran it we\n> got a neverending stream of segfaults in the logs.\n\nIf that is git-daemon dying when talking to older clients, that\nhas been fixed in 1.4.3.2 (it's virtual hosting support had an\noff-by-one wrong check to tell older clients from newer one).\n\nSorry about that -- we heard about the incompatibility this\nMonday.\n\n"},{"id":"294420","messageId":"453FA0B6.4040403@zytor.com","threadId":"43344","inReplyTo":"7v3b9ce1tk.fsf@assigned-by-dhcp.cox.net","subject":"Re: [git failure] failure pulling latest Linus tree","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2006-10-25T17:36:54Z","receivedAt":"2006-10-25T17:36:54Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Junio C Hamano wrote:\n> \"H. Peter Anvin\" <hpa@zytor.com> writes:\n> \n>> For some reason which we haven't been able to track down yet, the\n>> recent load imposed by FC6 caused zeus1's load to skyrocket, but not\n>> zeus2's... it's largely a mystery.\n> \n> Would kernel.org prefer RPM cut on a FC6 box now?\n> \n\nNo; since we have now (finally) archieved \"OS parity\" we're going to \nkeep hera, zeus1, and zeus2 in sync going forward.\n\n>> HOWEVER, git 1.4.3 seems to have been bad chicken.  When we ran it we\n>> got a neverending stream of segfaults in the logs.\n> \n> If that is git-daemon dying when talking to older clients, that\n> has been fixed in 1.4.3.2 (it's virtual hosting support had an\n> off-by-one wrong check to tell older clients from newer one).\n> \n> Sorry about that -- we heard about the incompatibility this\n> Monday.\n\nThis stuff happens... it's dealt with now.\n\n\t-hpa\n"}]}