Macs, Java, software development, IT related books and things I do for a living.
Note to self: Never run “sudo port upgrade all” again
“Ghee whiz… That was taking mighty long” I thought, “Why has my PowerBook been compiling and compiling for over 30 hours now?”
Then I remembered the command I entered to upgrade all installed MacPorts. I should have used installed instead of all. *Sigh!* I’ve just deleted my entire MacPorts install because I think it’s easier for me to actually just reinstall the few MacPorts I use.
MacPorts is a toolset for Mac OSX which allows you to get loads of unix tools ready and ported for the Mac OSX operating system. It’s a bit geeky, but it sure beats having to install everything by hand and hope you didn’t miss a mac specific patch.
| Print article | This entry was posted by Jeroen on September 7, 2006 19:03 at 19:03, and is filed under Mac OSX. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
about 3 years ago
thanks for dropping this note… didn’t find this suggestion anywhere else, surely I didn’t look at the right place.
about 3 years ago
Actually “sudo port upgrade outdated” is even more precise. Also before running such commands, don’t forget “sudo port selfupdate” as well. Else you won’t have the latest information available to the port command.
about 3 years ago
damn.. ran that yday. that explains it -_-
what a mess!
thanks for the note
about 3 years ago
hahahhah, I’ve just hit CTRL+C and then googlized “sudo port upgrade all”. The terminal was installing aspell, considering that the installation is in alphabetical order I’ve had a better luck.
about 2 years ago
I googled “sudo port upgrade all” just to see if I was the only person stupid enough to do this. I think there should be a warning; who actually intends to run this command?
about 2 years ago
Seriously, thanks for this post. I started my upgrade all two days ago and was looking at it — “why the heck is it upgrading openMotif????”. That answers it.
Yuck. Now /opt uses 6GB. Guess I’ll have to blow mine away, too
.
about 2 years ago
Thanks a lot! I was about to sit back and watch those 30 hours… :$
about 2 years ago
Yeah, I just googled this after more than 24 hours compiling… stopped my MacBook at apache2.
There should be some sort of “are you sure” when doing port upgrade all…
about 2 years ago
haha, I just started this too, and it began with ‘fetching libsdl’, and I was like – uhm…? – I had a feeling of what was about to happen, so I ctrl-c:ed and googled the line. sure enough
Macports are a nice initiative on OSX, but it sure has a loooong way to go to par up with apt-get on debian.
about 2 years ago
HaHa:) same here
about 2 years ago
Ouch – here we are at the end of March 2008, and I was almost the latest casualty of this one! I just hit Ctrl-C faster than you could say “sudo port upgrade outdated” !
about 2 years ago
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!
about 2 years ago
And the list of dummies goes on…
4.76gb…sigh…
I totally meant to type installed
about 1 year ago
well, if you didnt get too far this will also work
sudo port -f uninstall installed
about 1 year ago
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.
about 1 year ago
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.
about 1 year ago
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.
about 1 year ago
@Wendy
Please have a look at this location:
http://guide.macports.org/#installing.macports.uninstalling
about 1 year ago
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.
about 1 year ago
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.
about 1 year ago
CTRL+C -> Google -> @Here -> Thanks
about 1 year ago
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.
about 1 year ago
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…
about 1 year ago
—> Fetching xorg-libXau
/ponder
/selfkernelpanic
ctrl-c, google, here, /laugh.
about 1 year ago
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.
about 1 year ago
Me 23.
Peeter is correct.
/opt/local Time Machine. Thank you Time Machine.
Looks like this is fixed in ports 1.7.1