I've been debating about responding because I don't know the particulars of your migration. But in my experience working in IT for more than 2 decades is that it is almost always better to manually migrate rather than use Apple's Migration Assistant.
First, consider what the Migration Assistant is doing... it is duplicating your user accounts, copying third party applications, and the user settings in ~/Library. That is all it is doing, and it is absurd how long it takes to do these seemingly simple tasks. Rhetoricals: Are there a dozen distinct user accounts? Or is it a single account? How many applications are migrating? Are these Applications that required an installer and have kernel extensions, or are they just bundles that install with drag and drop? How vital or unreplaceable are these applications' user settings? My recommendation is to start with a clean install of macOS with a mind towards the next migration. Create your user account. If you are the sole user, create an ~/Applications folder in your home folder, and install every drag and drop application that you use there (this only works if it is a single user on the machine, as other users won't have access to your user folders). One by one, reinstall the applications that require an installer and need to live in /Applications. Manually copy your documents over, which is easy if they all live in ~/Documents. If you really need the settings... you can manually copy your entire ~/Library over: (on new system) sudo rm -rf ~/Library sudo cp -vpn /Volumes/old.machine.in.target.mode/Users/you/Library ~/Library sudo chown -R you:Staff ~/Library But it is better to leave your old ~/Library behind and as you use your applications on the new system, manually restore your settings and preferences on the fly. The pain doesn't last forever. Reinstall XCode. Reinstall macports from scratch. On the old system, run port requested > temp.txt Use this created text file as a guide to restore all your ports, and consider editing the file into an macports install script, just a list of install commands for each port you had requested before, and run it. Sync your browser bookmarks to the cloud, then resync them down to the new system's browser, or export bookmarks to a file and import them to the new browser. Then the next time you migrate, after creating a new account and logging in on your new hardware, put one machine in target disk mode and copy and replace the new user directories with your previous user directories, wholesale, which if you created an Applications folder in there, this will neatly reinstall all your applications that did not require an installer, bring over all your documents and settings, and much much faster than Migration Assistant. Then reinstall the applications that require the installer. Reinstall XCode and macports and repeat the requested command as a map, and reinstall all your ports. Hang on to the old system, for a time, until your production is back up and solid. The next migration will be easier because it is mostly just copying your user directories in one go, reinstalling a few other applications, reinstalling XCode, macports, and individual ports. I guarantee you far better performance on the new system by rebuilding it like this rather than using Migration Assistant, and the migration itself will take far less time. Best of luck. > On Jul 31, 2022, at 17:51, Gerben Wierda via macports-users > <[email protected]> wrote: > > I think I must have made an error (probably with the way I sync work across > systems). > > G > >>> On 31 Jul 2022, at 16:13, Joshua Root <[email protected]> wrote: >>> >>> There hasn't been a base release recently, so that output is completely >>> expected when updating the base sources. There should be some more output >>> involving "---> Updating the ports tree" which, if you have an rsync-based >>> source configured in sources.conf, will run additional rsync commands to >>> update ports.tar and PortIndex. That worked for me when I tried it just now. >>> >>> Gerben Wierda wrote: >>> >>> Because after finishing it still said ‘more than two weeks old please >>> update’, and it downloaded not more than 50-60 bytes >>> >>> Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) >>> R&A Enterprise Architecture <https://ea.rna.nl/> (main site) >>> Book: Chess and the Art of Enterprise Architecture >>> <https://ea.rna.nl/the-book/> >>> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/> >>> >>> >/On 31 Jul 2022, at 11:58, Chris Jones <jonesc at hep.phy.cam.ac.uk >>> ><https://lists.macports.org/mailman/listinfo/macports-users>> wrote: >>> >/>//>//>//>>/On 31 Jul 2022, at 9:05 am, Gerben Wierda via macports-users >>> ><macports-users at lists.macports.org >>> ><https://lists.macports.org/mailman/listinfo/macports-users>> wrote: >>> >/>>//>>/ />>/gerben at hermione >>> ><https://lists.macports.org/mailman/listinfo/macports-users> >>> >macports-ports % sudo port -v selfupdate />>/---> Updating MacPorts base >>> >sources using rsync />>//>>/Willkommen auf dem RSYNC-server auf ftp.fau.de >>> ><http://ftp.fau.de/>. />>/Nicht all unsere Mirror sind per rsync >>> >verfuegbar. />>//>>/Welcome to the RSYNC daemon on ftp.fau.de >>> ><http://ftp.fau.de/>. />>/Not all of our mirrors are available through >>> >rsync. />>//>>//>>/receiving file list ... done />>//>>/sent 16 bytes >>> >received 55 bytes 142.00 bytes/sec />>/total size is 85861888 speedup is >>> >1209322.37 />>//>>/Willkommen auf dem RSYNC-server auf ftp.fau.de >>> ><http://ftp.fau.de/>. />>/Nicht all unsere Mirror sind per rsync >>> >verfuegbar. />>//>>/Welcome to the RSYNC daemon on ftp.fau.de >>> ><http://ftp.fau.de/>. />>/Not all of our mirrors are available through >>> >rsync. />>//>>//>>/receiving file list ... done />>//>>/sent 16 bytes >>> >received 62 bytes 52.00 bytes/sec/ >> >
