{"thread":{"id":"103","subject":"First git-pasky bug report? :) error: bad signature/verify header failed","startedAt":"2005-04-18T13:22:43Z","lastAt":"2005-04-18T13:40:42Z","messageCount":2,"participants":["David Greaves","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"656","messageId":"4263B4A3.4030000@dgreaves.com","threadId":"103","inReplyTo":null,"subject":"First git-pasky bug report? :) error: bad signature/verify header failed","fromName":"David Greaves","fromEmail":"david@dgreaves.com","sentAt":"2005-04-18T13:22:43Z","receivedAt":"2005-04-18T13:22:43Z","isPatch":false,"sender":{"key":"david@dgreaves.com","avatar":"https://gravatar.com/avatar/ca67bad50999edcdd137c9a65da2381557d175bea99ae956afdabc5785e42b79?d=mp&s=160"},"body":"Hi\n\nI'm just starting to look at git (and cogito).\n\nEarlier this morning I got and built \nhttp://pasky.or.cz/~pasky/dev/git/git-pasky-base.tar.bz2\nI then did a \"git pull pasky\" and a make.\nAll went well.\nA couple of hours later I did another git pull pasky and had the problem \nshown below.\n\nI moved the directory to one side and reissued the commands and all was \nwell:\n  723  tar xvfj git-pasky-base.tar.bz2\n  724  cd git-pasky-0.4/\n  725  make\n  726  git pull pasky\n  727  make\n  728  git pull pasky\n  729  history | tail -10\n\nThis is just a heads up in case there's anything useful here.\nIt may just have been locking issues and me pulling whilst the repo was \nbeing updated or something...\n\nI'll hold the bad directory for a day or two in case anyone wants any \ndiagnostics running.\n\nDavid\n\n\ndavid@ash:/everything/devel/git/git-pasky-0.4$ git pull pasky\nMOTD:  Welcome to Petr Baudis' rsync archive.\nMOTD:\nMOTD:  If you are pulling my git branch, please do not repeat that\nMOTD:  every five minutes or so - new stuff is likely not going to\nMOTD:  appear so fast, and my line is not that thick. Nothing wrong\nMOTD:  with pulling every half an hour or so, of course.\nMOTD:\nMOTD:  Feel free to contact me at <pasky@ucw.cz>, shall you have\nMOTD:  any questions or suggestions.\n\n\n\nTree change: \nc29b3b29c2861ab0ffb475c7a7c9cfc946106eaf:5bf2f464d382b0bd746d06e264bc6951e7bfcd3a\n*100644->100644 blob    \n222bce21788308e1bf567304b474225b1681b03b->ad44415110ab63f1daa93e07dc496193d8006d81 \nMakefile\n*100755->100755 blob    \n667f877ae836c418294ef085e91efcb48d30cabb->035a1f470003c8b0963d0eb5f0eb457155f415ad \ngit\n*100755->100755 blob    \nfadd17e52845c5656ba344a9413b29b641c9ff5f->67e97fb71094693929f56d74bc13e572420d99d4 \ngitcommit.sh\n*100755->100755 blob    \n7ea441e584d603463fb1b83991b88f63a3895cff->18478101980f630f0e9fd95365c6d9f46bf27bfd \ngitmerge.sh\n*100755->100755 blob    \n9bda6555a1dafc1db762bc46db60d2a9485dc523->8e016f7d3aeb0244c8a6524ddaa4b2cb1ff8015f \ngitpull.sh\n+100755 blob    b6e318b31eb2ed6d2e137833a2064327331504b4        gitseek.sh\n*100755->100755 blob    \n30654380c10edde32def8e5fa2e2c956fbff3d58->ce44c1d4ce3b949b8ac99f1b90927da4e698e3de \ngittrack.sh\n-100755 blob    2488078570c4a5709332d92d7a1b5b65036ff3a0        gitupdate.sh\nTracked branch, applying changes...\nerror: bad signature\nerror: verify header failed\nread_cache: Invalid argument\nerror: bad signature\nerror: verify header failed\nerror: bad signature\nerror: verify header failed\n\nAt this point I moved the directory aside...\n\n-- \n\n"},{"id":"657","messageId":"20050418134042.GP1461@pasky.ji.cz","threadId":"103","inReplyTo":"4263B4A3.4030000@dgreaves.com","subject":"Re: First git-pasky bug report? :) error: bad signature/verify header failed","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-18T13:40:42Z","receivedAt":"2005-04-18T13:40:42Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Mon, Apr 18, 2005 at 03:22:43PM CEST, I got a letter\nwhere David Greaves <david@dgreaves.com> told me that...\n> Hi\n\nHi,\n\nI should release early and often. :-)\n\n> Tree change: \n> c29b3b29c2861ab0ffb475c7a7c9cfc946106eaf:5bf2f464d382b0bd746d06e264bc6951e7bfcd3a\n> Tracked branch, applying changes...\n> error: bad signature\n> error: verify header failed\n> read_cache: Invalid argument\n> error: bad signature\n> error: verify header failed\n> error: bad signature\n> error: verify header failed\n\nthis is a known problem, caused by the directory cache index format\nchange (to fix endianity issues). You can solve it by doing\n\n\tread-tree $(tree-id)\n\tupdate-cache --refresh\n\n(if you are reading this and didn't to the problematic pull yet, do it\nright after you get git-pasky-base, do your first pull and rebuild;\nyou won't get into problems that way).\n\nTo recover, do this now, and then do:\n\n\t(i) if you have local commits:\n\t\tgit merge -b c29b3b29c2861ab0ffb475c7a7c9cfc946106eaf \\\n\t\t\t5bf2f464d382b0bd746d06e264bc6951e7bfcd3a\n\n\t(ii) if you don't have local commits:\n\t\tgit diff -r c29b3b29c2861ab0ffb475c7a7c9cfc946106eaf:5bf2f464d382b0bd746d06e264bc6951e7bfcd3a \\\n\t\t\t| git apply\n\nI'm thinking how to handle future directory cache changes. Doing\nread-tree $(tree-id) && update-cache --refresh on the kernel tree is\nfast (three seconds?) if you have it in cache already, but SLOOOOOW\n(more than a minute) if you have cold cache; so I wouldn't do it\nalways.\n\nI think I will do something like check-cache which will just return\nexitcode based on whether the cache is ok or not, and do this time\nin the git multiplexer.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"}]}