multiple machines, rsync, and multiple workspaces

[liam-o-marsh]

Hello!
I've landed myself in quite the pickle right now, where I can't operate jj.

Basically, my setup is this:

• I have a "bare repo" (a workspace I deleted the contents of, though now I know I should formally checkout the root commit)
  that is synced to central storage through rsync, although this is the first time I actually try to use it from a different machine.
• The idea is that each machine might have one or multiple workspaces each, which might or might not need to be at different commits.
• currently, there is only one non-bare workspace, which has been created on another dev machine.
• Just copied the hacked-together "bare repo" to this machine, and tried to create a new workspace, only to see a stale-workplace error message, saying the working copy has been out of date since [the operation ID where I created the first machine's workspace]

Do you have any suggestions to fix this?
In the meantime, I will just use the underlying (colocated) git repo until I can get back to the previous machine

[peso]

It seems like your problem is to get to work on the copy.
How about jj workspace update-stale on the copy with the stale workspace?

I think you will encounter a similar problem when rsyncing the .jj folder back to your central bare repo.

I tried something similar, and it helped me to do a jj new on the source repo before copying, to make it easier to see what is going on. jj auto-commit at the target repo confused me a bit at first.

[liam-o-marsh]

I'm not sure what your second suggestion is here... and not sure if it applies? Only the "bare" repo is copied across machines,
and the workspace I actually used to write code on the "source" machine is definitely not stale. It's just that it doesn't exist on the current machine.

...I technically can run jj workspace update-stale, because that's only because I have root access (I have different usernames on the different machines, long story)
so I guess I'll go with that, but it doesn't sound like a widely-applicable solution

EDIT: well I was wrong on what the error message meant, so this previous paragraph is completely useless.

[liam-o-marsh]

well, nevermind all that.
the stale-workspace error I got was for the "bare repo" workspace itself, not the missing "working copy" workspace.
all is well now.