Sure would be nice if there were packages... but until then... I've condensed this post by florijan into the following:

# installing depends & version control
sudo aptitude install bzr python-webkit python-dbus python-gtk2 python-notify python-simplejson python-egenix-mxdatetime python-distutils-extra python-feedparser python-mako

# check out source with bzr
bzr branch lp:gwibber

# cd into dir where bzr put source / setup files
cd gwibber

# run setup script
sudo python setup.py install

Doesn't appear to add gwibber to the gnome menu by default, so you can launch gwibber from a terminal by typing gwibber, or do the same from alt+F2 prompt. Also, you can add a launcher to the panel that will run this command.

Actually, mostly it's not, but this really was a pleasant surprise today:

1. I type in really long key combination and get it right this time.
2. Emacs performs appropriate function
3. Emacs says "did you know there is this (really short) key combination for that?"

I think that's a first for me in any piece of software.

* TODO Get stuff done
* TODO Get it done now!
* TODO Stop, typing, do it!!!!

Also, remember that cron doesn't run in your context even if it is your own personal crontab running. This means you need to be explicit about everything!

For instance, are you writing to a file? Cron doesn't know what directory you are in, cause it runs all alone! You need to specify a full (absolute) path in your cron command or in the script that in launches.
Bad:
echo "hey, I just ran" >> my-script-log
Good:
echo "hey, I just ran" >> /home/myuser/logs/my-script-log
Info: I have found that if you don't specify an absolute path, cron assumes you are in your home directory, and will execute commands there, sometimes even if your script lives elsewhere (!) If you want actions to take place the same dir as your script, make your script specify the current dir by using ./myfile rather than myfile.

Likewise, are you launching a program? Cron may run with a different path than you, so specify the full path.

Finally, stuff that interacts with your visual and audio output won't go where you expect it to because cron is running in the background and not in your context. Witness the example of the zenity command that pops up a notification box.

Works when you type it but not when cron runs it:
zenity --info --text "hey, I just ran"
Tell zenity which display to send the popup to (cron doesn't know!):
DISPLAY=:0.0 /usr/bin/zenity --info --text "hey, I just ran"
Info:You can find which display you are using by running:
echo $DISPLAY

If you've set your scripts to run with cron, and they are not running, the likelihood is that you've set them to run at the wrong time. If you check, and you are definitely running them at the right time, make sure that your commands don't have script names with underscores or dots in them. This sillyness is a limitation of the run-parts script that cron uses.

I first found this here : http://www.debian-administration.org/articles/56#comment_17

sudo dpkg-reconfigure tzdata

.. another Germany themed post

With much help, we finished painting the rooms before our stuff arrived.  The bedroom and Nicole's office are painted in a light yellow tone.  The living room is painted in an off-white color, with the dining corner painted in a warm green.  The bathroom has a red stripe just above the tile, and the kitchen has a splash of red in a former doorway.  Ryan's office, which is also the guest room, will stay white.

Our bedroom (with balcony):

Our living room (where the ceiling is a bit lower and the wood floors are newer than in the rest of the apartment):

Ryan's office:

Our container of stuff arrived safely, but the no-parking-zone did not work 100%.  The police tracked down the owner of the car, borrowed their keys, and drove the car down the street instead of having it towed.  By the way, our stuff is only in the towed container -- the movers actually have beds in the truck and are away from their base in Hamburg for a week at a time. 

Drinks and snacks for the movers, who had to carry our stuff up the stairs to the 2nd floor (which is really the 3rd floor in the U.S. style of counting the ground floor as 1):

Two weeks later things are starting to come together slowly but surely.  Here is our bedroom with our beloved mattress and a new huge closet system we had to get since there are no built-in closets anywhere:

Our living room is still all over the place.  The futon will be moving into Ryan's office/guest room when our new couch gets delivered in a few weeks.  We will put curtains up on the left window too, but it's a holiday today (Good Friday) and we can't drill or do anything loud on holidays.

Second view of the living room with the green dining corner:

The kitchen (which was thankfully built-in, although we bought the washing machine):

Second view of our kitchen with Easter branches from Nicole's mom's garden, decorated with blown-out eggs and little Easter bunnies.  The red alcove used to be an open door to Nicole's office, but we had it closed with a thin wall.

We will get pictures up of the rest of the place as we settle in more.  We are starting to feel at home a little more every day.