[MacPorts] Migration modified

[MacPorts Wiki]

Page "Migration" was changed by raimue
Diff URL: <https://trac.macports.org/wiki/Migration?action=diff&version=132>
Revision 132
Comment: Move troubleshooting for restore_ports.tcl into the foldable
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Migration
=========================================================================
--- Migration (version: 131)
+++ Migration (version: 132)
@@ -107,10 +107,7 @@
       }}}
       Warning: if a port in `requested.txt` was ''not'' installed in the previous step, the iterative `setrequested` will terminate, leaving some ports still marked as not-requested. Edit `requested.txt` to remove any ports that were not installed and repeat this step. Double-check your desired ports are set as requested with `port echo requested`.
 
-}}}
-}}}
-
-== Troubleshooting ==
+=== Troubleshooting Old Migration Procedure ===
 
 Though it is now quite well-tested, the restore_ports script may fail in some cases. One known issue is that the script will fail if there are conflicting ports in the list. It's possible to have conflicting ports installed provided at most one of the conflicting set is active. If the script fails, for this reason, you can delete one of the conflicting ports from myports.txt and then simply run the script again. You may need to do this multiple times if there are multiple conflicting ports listed.
 
@@ -140,7 +137,12 @@
 }}}
 This will raise the file limit for the duration of the `restore_ports.tcl` command.
 
-Another potential problem comes from possible differences between ports that do compile on an older macOS, but no longer on the newer. For instance, you might have installed OpenBLAS on macOS Mojave. This was built with gcc10, the then preferred version of gcc. OpenBLAS sets a +gcc10 variant for this and it has remained like that as long as you were updating it. When upgrading to macOS Monterey according to the procedure above, MacPorts will try to exactly recreate what was on Mojave, hence OpenBLAS +gcc10. But gcc10 may not compile on macOS Monterey (it does not as I write this example). Hence, the migration of OpenBLAS and everything that depends on it fails.
+}}}
+}}}
+
+= Troubleshooting =
+
+A potential problem comes from possible differences between ports that do compile on an older macOS, but no longer on the newer. For instance, you might have installed OpenBLAS on macOS Mojave. This was built with gcc10, the then preferred version of gcc. OpenBLAS sets a +gcc10 variant for this and it has remained like that as long as you were updating it. When upgrading to macOS Monterey according to the procedure above, MacPorts will try to exactly recreate what was on Mojave, hence OpenBLAS +gcc10. But gcc10 may not compile on macOS Monterey (it does not as I write this example). Hence, the migration of OpenBLAS and everything that depends on it fails.
 
 Another issue may come from incompatibility between some additional components, which may manifest itself with ports failing with a message like
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/Migration>
MacPorts <https://www.macports.org/>
Ports system for macOS

This is an automated message. Someone added your email address to be
notified of changes on 'Migration' page.
If it was not you, please report to admin at macports.org.