4 messages, 2 authors, 2003-08-11 · open the first message on its own page
From: Gary Thomas <hidden>
Date: 2003-08-09 13:38:43
I've been unable to access this repository [for days]. [gthomas@hermes tmp]$ bk clone bk://source.mvista.com/linuxppc-2.5 linuxppc-2.5 ERROR-Can't get read lock on the repository. Any ideas/help? -- Gary Thomas [off-list ref] MLB Associates ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Tom Rini <hidden>
Date: 2003-08-11 17:12:47
On Sat, Aug 09, 2003 at 07:38:43AM -0600, Gary Thomas wrote:
I've been unable to access this repository [for days]. [gthomas@hermes tmp]$ bk clone bk://source.mvista.com/linuxppc-2.5 linuxppc-2.5 ERROR-Can't get read lock on the repository. Any ideas/help?
This should be fixed now. -- Tom Rini http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Gary Thomas <hidden>
Date: 2003-08-11 17:17:33
On Mon, 2003-08-11 at 11:12, Tom Rini wrote:
On Sat, Aug 09, 2003 at 07:38:43AM -0600, Gary Thomas wrote:quoted
I've been unable to access this repository [for days]. [gthomas@hermes tmp]$ bk clone bk://source.mvista.com/linuxppc-2.5 linuxppc-2.5 ERROR-Can't get read lock on the repository. Any ideas/help?This should be fixed now.
Yes, thanks. Any feedback what was stuck? (I tried it just a few hours ago and it was still broken, so you obviously did something) -- Gary Thomas [off-list ref] MLB Associates ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Tom Rini <hidden>
Date: 2003-08-11 17:31:02
On Mon, Aug 11, 2003 at 11:17:33AM -0600, Gary Thomas wrote:
On Mon, 2003-08-11 at 11:12, Tom Rini wrote:quoted
On Sat, Aug 09, 2003 at 07:38:43AM -0600, Gary Thomas wrote:quoted
I've been unable to access this repository [for days]. [gthomas@hermes tmp]$ bk clone bk://source.mvista.com/linuxppc-2.5 linuxppc-2.5 ERROR-Can't get read lock on the repository. Any ideas/help?This should be fixed now.Yes, thanks. Any feedback what was stuck? (I tried it just a few hours ago and it was still broken, so you obviously did something)
It was a local permissions issue. -- Tom Rini http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/