Moving project between Arch archives
You should avoid doing that. This operation is not nativelly supported by tla. See Changing History. But if you really need to do that follow one of the two suggestions ahead.
Warning: the source tree workplaces already open will not follow this project move.
Instead of moving
Instead of moving a project between archives, you might consider these possibilities:
Just move the archive
If the problem is that the archive needs to move to a different location, just move the archive and have people re-register the new location.
Branch into a new archive
Tag the project into a new project in the new archive, and continue development there. The main problem is that people who can't see the old archive won't see the old history.
This might be appropriate for a project that starts private and then becomes public.
A simple shell script to do that
From Robin Farine e-mail in the mailing list:
If you you really want to rename your archive and are aware of the consequences, then you could make a backup of it and then run the attached script on it. The usage message should suffice to tell you how to do that.
the Fix Arch Script is called 'fixarch' because when I started with Arch, I renamed an archive and then commited to it. I learned later the hard way that it was not a good idea to do that.
Script in the tla-tools package
From Miles Bader e-mail in the mailing list:
There's also a script in tla-tools that will do `deep' archive renaming, called `tla-munge-archive-names'; it will let you rename branches &c too. Like Robin's script, --help will tell you how to use it.
It _doesn't_ support signed archives though, so if your archive is signed, you'll have to first make an unsigned mirror and munge that. [In general I think it's not possible to retain signatures after archive munging, you'll have to resign everything.]