{"thread":{"id":"5875","subject":"Release 1.4.2 build failure","startedAt":"2006-10-10T20:22:21Z","lastAt":"2006-10-11T15:12:39Z","messageCount":3,"participants":["Phillip Susi","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"28545","messageId":"452C00FD.1020307@cfl.rr.com","threadId":"5875","inReplyTo":null,"subject":"Release 1.4.2 build failure","fromName":"Phillip Susi","fromEmail":"psusi@cfl.rr.com","sentAt":"2006-10-10T20:22:21Z","receivedAt":"2006-10-10T20:22:21Z","isPatch":false,"sender":{"key":"psusi@cfl.rr.com","avatar":null},"body":"I tried to build git release 1.4.2 and it failed with the following tests:\n\n*** t3403-rebase-skip.sh ***\n*   ok 1: setup\n*   ok 2: rebase with git am -3 (default)\n* FAIL 3: rebase --skip with am -3\n\n                 git reset --hard HEAD &&\n                 git rebase --skip\n\n*   ok 4: checkout skip-merge\n*   ok 5: rebase with --merge\n*   ok 6: rebase --skip with --merge\n* FAIL 7: merge and reference trees equal\n         test -z \"`git-diff-tree skip-merge skip-reference`\"\n* failed 2 among 7 test(s)\n\n\nI enabled the --verbose and --debug test options in the test script \nmakefile and then got this:\n\n\n*   ok 2: rebase with git am -3 (default)\n* expecting success:\n         git reset --hard HEAD &&\n         git rebase --skip\n\nprevious dotest directory .dotest still exists but mbox given.\n* FAIL 3: rebase --skip with am -3\n\n                 git reset --hard HEAD &&\n                 git rebase --skip\n\n* expecting success: git checkout -f skip-merge\n*   ok 4: checkout skip-merge\n* expecting failure: git rebase --merge master\nMerging HEAD with aa79649ca1fa23815a1ad3e336d9f860599556a3\nMerging:\n7cb7464379042fecc2968751bd55656a97d28c77 goodbye\naa79649ca1fa23815a1ad3e336d9f860599556a3 we should skip this\nfound 1 common ancestor(s):\nb0ab61719ccd2e08f34e326172362a485540934e hello\nAuto-merging hello\nCONFLICT (content): Merge conflict in hello\n\n\nWhen you have resolved this problem run \"git rebase --continue\".\nIf you would prefer to skip this patch, instead run \"git rebase --skip\".\nTo restore the original branch and stop rebasing run \"git rebase\n--abort\".\n\n*   ok 5: rebase with --merge\n* expecting success:\n         git reset --hard HEAD &&\n         git rebase --skip\n\nMerging HEAD with 46a6fc9814012b86849bc8fc8ae2d5cc1958c3cb\nMerging:\n7cb7464379042fecc2968751bd55656a97d28c77 goodbye\n46a6fc9814012b86849bc8fc8ae2d5cc1958c3cb this should not be skipped\nfound 1 common ancestor(s):\naa79649ca1fa23815a1ad3e336d9f860599556a3 we should skip this\n\nCommitted: 0002 this should not be skipped\nAll done.\n*   ok 6: rebase --skip with --merge\n* expecting success: test -z \"`git-diff-tree skip-merge skip-reference`\"\n* FAIL 7: merge and reference trees equal\n         test -z \"`git-diff-tree skip-merge skip-reference`\"\n/tmp/buildd/git-core-1.4.2/t/../gitk: line 3: exec: wish: not found\n* failed 2 among 7 test(s)\n\n\nDoes anyone know what this means?  I am building on Ubuntu Dapper Drake.\n\nPlease CC replies.\n"},{"id":"28558","messageId":"7vejtfzur8.fsf@assigned-by-dhcp.cox.net","threadId":"5875","inReplyTo":"452C00FD.1020307@cfl.rr.com","subject":"Re: Release 1.4.2 build failure","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-10-10T22:11:23Z","receivedAt":"2006-10-10T22:11:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Are you by any chance running the test with the stdin connected\nto </dev/null?\n\nIf so, the fix is in 1.4.2.2.\n\nBTW, the latest \"maint\" release is 1.4.2.3 and we have 1.4.3-rc2\nfrom the \"master\" branch.\n"},{"id":"28603","messageId":"452D09E7.10709@cfl.rr.com","threadId":"5875","inReplyTo":"7vejtfzur8.fsf@assigned-by-dhcp.cox.net","subject":"Re: Release 1.4.2 build failure","fromName":"Phillip Susi","fromEmail":"psusi@cfl.rr.com","sentAt":"2006-10-11T15:12:39Z","receivedAt":"2006-10-11T15:12:39Z","isPatch":false,"sender":{"key":"psusi@cfl.rr.com","avatar":null},"body":"Yes, I think the debian build system does that.  I must have missed the \nnewer 1.4.2.x releases when scanning the directory.  Thanks.\n\nJunio C Hamano wrote:\n> Are you by any chance running the test with the stdin connected\n> to </dev/null?\n> \n> If so, the fix is in 1.4.2.2.\n> \n> BTW, the latest \"maint\" release is 1.4.2.3 and we have 1.4.3-rc2\n> from the \"master\" branch.\n> \n"}]}