Multi-repo-copy has an unintentional requirement for the repo pairs to be provided in a particular order
The order in which the user specifies their source and destination repositories in the advanced copy API's config object does not matter.
The code loops through the pairs of source and destination repositories one by one as it loads them into the solver, decides what to copy, and then creates the new repository versions, which means that when the copy operation is performed for repo pairs early in the list, the solver doesn't know about repos later in the list.
Load everything into the solver first, and only after everything has been loaded perform the depsolving + copies.
Please register to edit this issue