Opened 3 years ago

Closed 3 years ago

#55732 closed enhancement (fixed)

Migration Problems

Reported by: rpspringuel (Fr. Samuel Springuel) Owned by:
Priority: Normal Milestone:
Component: wiki Version:
Keywords: Cc:

Description (last modified by ryandesign (Ryan Schmidt))

While migrating from one machine (running El Capitan) to a new one (running High Sierra) I ran into an unexpected issue which I think should be mentioned on the Migration page of the wiki.

Because of the difference in the operating system between the two machines, I started out by setting up various things on the new machine fresh out of the box, including installing MacPorts and several ports. After this, I used the Migration Assistant to copy over the data files associate with the (only) user on the old machine (via its Time Machine backup). I specifically unchecked the options to copy over /opt.../ and Computer settings. I was merely trying to copy over the data files associated with that user and these were being written to a different username than was setup on the new machine. However, despite this I found that my MacPorts installation and several ports were corrupted as a result of using the Migration Assistant. After messing around with trying to follow the migration instructions after the fact for a while, I had to resort to wiping all ports and MacPorts itself and start from scratch.

I'm willing to make the necessary edits myself, but since I've never actually worked on the wiki before, I thought I'd post this issue in order to get feedback on the proposal first.

As a result of this, I think the wiki should warn people that use of the Migration Assistant should be done before installing and using MacPorts on a new machine.

Change History (4)

comment:1 Changed 3 years ago by ryandesign (Ryan Schmidt)

I agree with that recommendation; feel free to edit the wiki.

comment:2 Changed 3 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)

comment:3 Changed 3 years ago by rpspringuel (Fr. Samuel Springuel)

Changes made. So long as no one objects, this ticket can be closed (though I don't see how).

comment:4 Changed 3 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.