{"thread":{"id":"13981","subject":"error: cannot lock ref 'refs/remotes/origin/*'","startedAt":"2008-06-16T16:53:47Z","lastAt":"2008-06-17T21:00:07Z","messageCount":9,"participants":["Nicolas Bock","Johannes Schindelin","Johan Herland","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"80052","messageId":"1213635227.17814.6.camel@localhost","threadId":"13981","inReplyTo":null,"subject":"error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Nicolas Bock","fromEmail":"nbock@lanl.gov","sentAt":"2008-06-16T16:53:47Z","receivedAt":"2008-06-16T16:53:47Z","isPatch":false,"sender":{"key":"nbock@lanl.gov","avatar":"https://gravatar.com/avatar/82d3ee55106bec18a2ac37d7d4f1a2bbd5d74fbe7f8b8817dfbdbd4e49841183?d=mp&s=160"},"body":"Hello list,\n\nwhen running \"git gc\" I get the following error message as of late:\n\n$ git gc\nerror: cannot lock ref 'refs/remotes/origin/*'\nerror: failed to run reflog\n\nWhen I rsync the directory tree to another machine, I can run \"git gc\"\nwithout any error messages. What exactly does this error mean? Why would\nlocking fail?\n\nThanks already,\n\nnick\n"},{"id":"80097","messageId":"1213667245.14393.3.camel@localhost","threadId":"13981","inReplyTo":"1213635227.17814.6.camel@localhost","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Nicolas Bock","fromEmail":"nbock@lanl.gov","sentAt":"2008-06-17T01:47:25Z","receivedAt":"2008-06-17T01:47:25Z","isPatch":false,"sender":{"key":"nbock@lanl.gov","avatar":"https://gravatar.com/avatar/82d3ee55106bec18a2ac37d7d4f1a2bbd5d74fbe7f8b8817dfbdbd4e49841183?d=mp&s=160"},"body":"I realized that I recently upgraded from version 1.5.3.7 to 1.5.4.5. I\ndouble checked and downgraded again, and yes, I don't have any problems\nrunning \"git gc\" with the older version, but I get the below error\nmessage with the newer version of git.\n\nnick\n\n\nOn Mon, 2008-06-16 at 10:53 -0600, Nicolas Bock wrote:\n> Hello list,\n> \n> when running \"git gc\" I get the following error message as of late:\n> \n> $ git gc\n> error: cannot lock ref 'refs/remotes/origin/*'\n> error: failed to run reflog\n> \n> When I rsync the directory tree to another machine, I can run \"git gc\"\n> without any error messages. What exactly does this error mean? Why would\n> locking fail?\n> \n> Thanks already,\n> \n> nick\n> \n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"},{"id":"80128","messageId":"alpine.DEB.1.00.0806171140470.6439@racer","threadId":"13981","inReplyTo":"1213667245.14393.3.camel@localhost","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-06-17T10:41:54Z","receivedAt":"2008-06-17T10:41:54Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 16 Jun 2008, Nicolas Bock wrote:\n\n> > $ git gc\n> > error: cannot lock ref 'refs/remotes/origin/*'\n> > error: failed to run reflog\n\nThis is a bogus ref name.  Hrm.  Can you look with \"git show-ref\" if you \nhave (by some funny accident) an invalid ref there?\n\nCiao,\nDscho\n"},{"id":"80143","messageId":"1213712520.6400.1.camel@localhost","threadId":"13981","inReplyTo":"alpine.DEB.1.00.0806171140470.6439@racer","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Nicolas Bock","fromEmail":"nbock@lanl.gov","sentAt":"2008-06-17T14:22:00Z","receivedAt":"2008-06-17T14:22:00Z","isPatch":false,"sender":{"key":"nbock@lanl.gov","avatar":"https://gravatar.com/avatar/82d3ee55106bec18a2ac37d7d4f1a2bbd5d74fbe7f8b8817dfbdbd4e49841183?d=mp&s=160"},"body":"This is what I get:\n\n$ git show-ref\na4995ae293fd95697a643cd3ea45585ecc38a19d refs/heads/ACT\n3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/heads/master\n78e33155a0ab4ab0acba4c64758681fe99f1c5ca refs/heads/nick\nef66b3aa74b8c1edb55161e01a99dee7cf9edaa3 refs/remotes/origin/*\n3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/remotes/origin/master\n\nin what sense is this ref \"bogus\"? Is it syntactically incorrect?\n\n\n\nOn Tue, 2008-06-17 at 11:41 +0100, Johannes Schindelin wrote:\n> Hi,\n> \n> On Mon, 16 Jun 2008, Nicolas Bock wrote:\n> \n> > > $ git gc\n> > > error: cannot lock ref 'refs/remotes/origin/*'\n> > > error: failed to run reflog\n> \n> This is a bogus ref name.  Hrm.  Can you look with \"git show-ref\" if you \n> have (by some funny accident) an invalid ref there?\n> \n> Ciao,\n> Dscho\n> \n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"},{"id":"80144","messageId":"200806171629.06570.johan@herland.net","threadId":"13981","inReplyTo":"1213712520.6400.1.camel@localhost","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Johan Herland","fromEmail":"johan@herland.net","sentAt":"2008-06-17T14:29:06Z","receivedAt":"2008-06-17T14:29:06Z","isPatch":false,"sender":{"key":"johan@herland.net","avatar":"https://avatars.githubusercontent.com/u/547031?v=4"},"body":"On Tuesday 17 June 2008, Nicolas Bock wrote:\n> This is what I get:\n>\n> $ git show-ref\n> a4995ae293fd95697a643cd3ea45585ecc38a19d refs/heads/ACT\n> 3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/heads/master\n> 78e33155a0ab4ab0acba4c64758681fe99f1c5ca refs/heads/nick\n> ef66b3aa74b8c1edb55161e01a99dee7cf9edaa3 refs/remotes/origin/*\n> 3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/remotes/origin/master\n>\n> in what sense is this ref \"bogus\"? Is it syntactically incorrect?\n\nYes, According to \"man git-check-ref-format\", asterisk is NOT allowed in \na ref name.\n\n\n...Johan\n\n-- \nJohan Herland, <johan@herland.net>\nwww.herland.net\n"},{"id":"80146","messageId":"alpine.DEB.1.00.0806171645300.2308@eeepc-johanness","threadId":"13981","inReplyTo":"1213712520.6400.1.camel@localhost","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-06-17T14:46:03Z","receivedAt":"2008-06-17T14:46:03Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 17 Jun 2008, Nicolas Bock wrote:\n\n> This is what I get:\n> \n> $ git show-ref\n> a4995ae293fd95697a643cd3ea45585ecc38a19d refs/heads/ACT\n> 3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/heads/master\n> 78e33155a0ab4ab0acba4c64758681fe99f1c5ca refs/heads/nick\n> ef66b3aa74b8c1edb55161e01a99dee7cf9edaa3 refs/remotes/origin/*\n\nThis is the culprit.  It is obviously a wrong name: \"*\" is not allowed.\n\nHth,\nDscho\n"},{"id":"80149","messageId":"1213717788.13390.2.camel@localhost","threadId":"13981","inReplyTo":"200806171629.06570.johan@herland.net","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Nicolas Bock","fromEmail":"nbock@lanl.gov","sentAt":"2008-06-17T15:49:48Z","receivedAt":"2008-06-17T15:49:48Z","isPatch":false,"sender":{"key":"nbock@lanl.gov","avatar":"https://gravatar.com/avatar/82d3ee55106bec18a2ac37d7d4f1a2bbd5d74fbe7f8b8817dfbdbd4e49841183?d=mp&s=160"},"body":"I guess I don't understand refs. I figured that since I have\n\nremote.origin.fetch=+refs/heads/*:refs/remotes/origin/*\n\nset, I should have a ref refs/remotes/origin/* as well.\n\n\n\nOn Tue, 2008-06-17 at 16:29 +0200, Johan Herland wrote:\n> On Tuesday 17 June 2008, Nicolas Bock wrote:\n> > This is what I get:\n> >\n> > $ git show-ref\n> > a4995ae293fd95697a643cd3ea45585ecc38a19d refs/heads/ACT\n> > 3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/heads/master\n> > 78e33155a0ab4ab0acba4c64758681fe99f1c5ca refs/heads/nick\n> > ef66b3aa74b8c1edb55161e01a99dee7cf9edaa3 refs/remotes/origin/*\n> > 3378ccb42c22740b7fcc240ffa0e4f798b8acf1f refs/remotes/origin/master\n> >\n> > in what sense is this ref \"bogus\"? Is it syntactically incorrect?\n> \n> Yes, According to \"man git-check-ref-format\", asterisk is NOT allowed in \n> a ref name.\n> \n> \n> ...Johan\n> \n"},{"id":"80157","messageId":"m3fxrbop4g.fsf@localhost.localdomain","threadId":"13981","inReplyTo":"1213717788.13390.2.camel@localhost","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-06-17T19:09:07Z","receivedAt":"2008-06-17T19:09:07Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Nicolas Bock <nbock@lanl.gov> writes:\n\n> I guess I don't understand refs. I figured that since I have\n> \n> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*\n> \n> set, I should have a ref refs/remotes/origin/* as well.\n\nThe above is _globbing_ refspec, it means that it maps \n\"refs/heads/<name>\" branch in remote repository to \n\"refs/remotes/origin/<name>\" remote-tracking branch in local\nrepository.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"80161","messageId":"1213736407.2490.9.camel@localhost","threadId":"13981","inReplyTo":"m3fxrbop4g.fsf@localhost.localdomain","subject":"Re: error: cannot lock ref 'refs/remotes/origin/*'","fromName":"Nicolas Bock","fromEmail":"nbock@lanl.gov","sentAt":"2008-06-17T21:00:07Z","receivedAt":"2008-06-17T21:00:07Z","isPatch":false,"sender":{"key":"nbock@lanl.gov","avatar":"https://gravatar.com/avatar/82d3ee55106bec18a2ac37d7d4f1a2bbd5d74fbe7f8b8817dfbdbd4e49841183?d=mp&s=160"},"body":"Thanks, that explains it..\n\n\nnick\n\nOn Tue, 2008-06-17 at 12:09 -0700, Jakub Narebski wrote:\n> Nicolas Bock <nbock@lanl.gov> writes:\n> \n> > I guess I don't understand refs. I figured that since I have\n> > \n> > remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*\n> > \n> > set, I should have a ref refs/remotes/origin/* as well.\n> \n> The above is _globbing_ refspec, it means that it maps \n> \"refs/heads/<name>\" branch in remote repository to \n> \"refs/remotes/origin/<name>\" remote-tracking branch in local\n> repository.\n> \n"}]}