Tar Ate My Work (Cause I Told It To)
My stomach just turned inside out and dropped to my feet. Good bye to my local cvs changes to WordPress.
I recently patched the latest cvs of WordPress to keep your tags when using rss summaries, so that links show up in people’s clients. Thankfully, I uploaded it to Mosquito, and it’s now safe there. I thought it would be a good idea to apply this against the latest 1.2.1 for people who can’t wait. Here’s what I did, see if you can figure out where I went wrong.
virgil2:Documents] bjornrud% wget http://wordpress.org/latest.tar.gz
--10:47:06-- http://wordpress.org/latest.tar.gz
== `latest.tar.gz'
Resolving wordpress.org... done.
Connecting to wordpress.org[67.19.16.238]:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [application/force-download]
10:47:07 (226.26 KB/s) - latest.tar.gz saved [238639]
virgil2:Documents] bjornrud% mkdir t
virgil2:Documents] bjornrud% mv latest.tar.gz t/
virgil2:Documents] bjornrud% tar zxvvf t/latest.tar.gz
You see, I didn’t change my working directory to the directory I wanted to unzip WordPress into (t/). As you might have guessed, I had a directory named WordPress already, and it over-wrote the files in it.
Woe is me.
JD Said,
October 19, 2004 @ 11:50 am
Reminds me of the time I misused a ‘rm -rf’ and took out half of my website directory before i ctrl-c’d it. I bet we’ll never make the same mistake twice though.