Comments on: Note to self: Never run “sudo port upgrade all” again

By: aj

aj — Sun, 22 Mar 2009 17:34:08 +0000

Me 23.
Peeter is correct.

/opt/local Time Machine. Thank you Time Machine.

By: Peeter

Peeter — Wed, 18 Mar 2009 09:26:43 +0000

One more…
They should really have done something about this since the original post here in september 2006 – that’s two and a half years…
Of course “upgrade” should only mean to actually upgrade what has already been installed.
Oh well, uninstall installed and start over.

By: Damien Caselli

Damien Caselli — Thu, 12 Mar 2009 11:00:51 +0000

—> Fetching xorg-libXau
/ponder
/selfkernelpanic
ctrl-c, google, here, /laugh.

By: Zach

Zach — Thu, 05 Mar 2009 23:07:31 +0000

I did that just now, let it go for a few hours, 7.2 GB. The processor hit 90 C before I realized something was very wrong. Feeling pretty stupid right now. Ugh, apt-get, you have lead me astray with your sensible interface…

By: sc

sc — Mon, 19 Jan 2009 17:16:44 +0000

Did we all come from fink-land, where that kind of command made more sense? Who would ever want to run a command that installed anything and everything in the repository using “upgrade” if it wasn’t already explicitly installed? Shouldn’t that be

sudo port install all

instead of

sudo port upgrade all

Good grief! PS – I was on abiword, but it probably was installing a bunch of dependencies that I certainly don’t want. What a mess.

By: Jin Kwon

Jin Kwon — Fri, 07 Nov 2008 07:07:42 +0000

CTRL+C -> Google -> @Here -> Thanks

By: Simon

Simon — Thu, 06 Nov 2008 13:00:17 +0000

Heh, glad to see I’m not the first to make this mistake :/

I’m hoping that ditching /opt/local and restoring a Time Machine backup will sort it out.

By: /. 163409

/. 163409 — Sun, 02 Nov 2008 02:38:44 +0000

Nobody in this thread should feel bad about doing this.

I just did it, too.

To port that statement into perspective, I have been working with UNIX and UNIX-like systems since late 1987, and UNIX system administration has been part of my job since early 1997. This is NOT a newb error, this is the result of a design flaw. Which is probably why I stopped on “2Pong”, three minutes in.

Oh well, I still love mac ports.

By: Jeroen Leenarts

Jeroen Leenarts — Tue, 07 Oct 2008 18:56:59 +0000

@Wendy

Please have a look at this location:
http://guide.macports.org/#installing.macports.uninstalling

By: Wendy

Wendy — Tue, 07 Oct 2008 17:30:55 +0000

If you did this, and it’s sucking tons of disk space, how do you ‘blow away’ your mac ports install and start over? Is there a simple command, or a directory you remove?

I totally agree about the error message btw. We don’t want to become windows, but this is such an easy mistake to make, and totally not what anyone except a developer would really want to do.

By: Steven

Steven — Sat, 27 Sep 2008 08:19:07 +0000

Grah. I did it too. I let it go for about an hour before I realized it was “upgrading” some packages I hadn’t installed.

By: Justin

Justin — Wed, 24 Sep 2008 17:04:41 +0000

Well! Looks like MacPorts hasn’t changed anything yet! I just ran the command and stopped at qt4-mac.

My computer was freaking out. Thank god I googled this and stopped it while I could.

By: chris

chris — Wed, 20 Aug 2008 15:38:03 +0000

well, if you didnt get too far this will also work

sudo port -f uninstall installed

By: Joe

Joe — Mon, 14 Jul 2008 20:46:23 +0000

And the list of dummies goes on…

4.76gb…sigh…

I totally meant to type installed

By: Reed

Reed — Thu, 15 May 2008 08:26:47 +0000

I just got done with 4 hours of “upgrading” before I got suspicious and found your page… they should really put a big fat warning when you type that!

I was on “bison” before I canceled. I’m glad I heard the computer fan spin up in the middle of the night, or it would have been going all week!