"Clean all" bugs out in letter A when migrating on Lion

[clytie@…]

G'day :)

I recently upgraded to 10.7 (on Intel), so realised (after trying port selfupdate and it telling me it couldn't install macports 2.0.1 because the compiler didn't work) that I needed to follow the MacPorts migration instructions, as I had on previous OSX upgrades but blissfully forgot in between. After saving my port list, which was brief (30 items) as I had completely reinstalled the system fairly recently, I followed these steps.

Step 1 uninstall all ports:

sudo port -f uninstall --follow-dependents installed

Most of my ports reported an infinite loop. When I uninstalled each of these separately, I found the loop occurred because somehow they depended on themselves, e.g.

sudo port -f uninstall py26-crypto
--->  Unable to uninstall/deactivate py26-crypto @2.3_0, the following ports depend on it:
--->    py26-crypto @2.3_0

Self-assurance is one thing, but dizzy introspection is quite another. Fortunately, the individual uninstall forced the package-uninstall anyway. A few of the ports uninstalled normally in between, as I alternated "uninstall everything" with "just uninstall this one, and I don't want to hear about your psychiatric difficulties". So at this stage, I assumed uninstalling had sorta succeeded.

Step 2 clean all partial builds:

sudo port clean all

This started off well, but bugged out part-way through the letter A (A is for Angst when Migrating):

--->  Cleaning argus-monitor
--->  Cleaning argyll
--->  Cleaning aria2
Error: Unable to open port: invalid command name "get_canonical_archflags"
To report a bug, see <http://guide.macports.org/#project.tickets>

I couldn't find this error message anywhere when searching, so here I am dumping my problem in your lap. Sorry about that. I'm too sick to debug properly anymore.

The migration process also requires upgrading to Xcode 4, but I don't have enough quota left, so will have to wait for a couple of days until my plan rolls over. (It doesn't wiggle its paws in the air, it just rolls over once a month.) The migration instructions did not specify upgrading Xcode prior to uninstalling.

I'm going to look for a way to wipe macports and start again (being short of brain nowadays, I usually resort to the scorched-earth policy when confused), and hopefully that will make it possible to reinstall MacPorts.

Meanwhile, here is the issue. Good luck, and I wish I could help. :)

Clytie

[ryandesign (Ryan Carsten Schmidt)]

Port depending on itself is certainly a new failure to me. That... should not happen.

get_canonical_archflags is one of the new commands introduced in MacPorts 2; MacPorts 1.x won't be able to understand ports containing that or the other new commands.

The usual order of operations is:

• Upgrade to Lion
• Upgrade to the version of Xcode required by Lion (4.1+)
• Upgrade to MacPorts 2.0.1
• Follow Migration instructions (uninstall ports, reinstall them)

[jmroot (Joshua Root)]

Right, the first step is to reinstall MacPorts base and Xcode. Not doing that explains both these errors. Maybe those should be numbered steps too.