2

Using Ditz to Track Issues

Ditz is an issue tracking system for command line junkies. For those of us who live on the command line already, using vim, psql or mysql, svn, bzr or git, this makes us feel right at home tracking our issues. And I love it.

Ditz creates a directory within your project (or anywhere else you want it) and a config file in the project directory. Each issue then becomes a file in this directory. A powerful command line interface allows you to setup releases and components, and assign those to issues, as well as edit, complete and comment on issues. It even provides the ability to generate HTML files of issues.

The only thing Ditz doesn’t allow you to do is have your information stored in a remote location, which pretty much kills effective project collaboration as one would have to commit their Ditz directory ASAP, and other developers would have to update their working copy before managing issues.

But for solo projects, it’s perfect for command line junkies to track bugs, tasks and features for their project.

0

An Epic Struggle With Portage

Today I embarked on an epic struggle with the Portage package manager attempting to update the packages on my system. After I ran into what can only be described as a phantom package.

Continue Reading →

0

Removing Windows Newline Characters in Vim

Sometimes when working on projects in both Linux and Windows, a file will end up with Windows newline characters, which show up as ^M in Vim. Annoying as this is, there’s a quick fix to remove them in Vim using a regular expression replace:

:%s/<control-v><control-m>//g

Magically, all the ugly Windows newline characters are gone.

0

A Complete, Polished Look for Gnome

I’m not afraid to admit it: I’m a fan of Gnome. I think KDE looks to cartoonish. I actually prefer using OpenBox with a slew of lightweight apps for window manager addons, but that because too much to maintain, and I have better things to do with my time.

It’s hard to find a nice, clean set of decorations for Gnome that mesh well together. GDM theme, icons, wallpapers, GTK themes, etc that all blend well together to create a complete, polished look.

Recently I found the “Colors” theme set on Gnome Look.

GDM and Wallpapers: http://www.gnome-look.org/content/show.php/Arc-Colors+GDM-Walls?content=88305
GTK: http://www.gnome-look.org/content/show.php/Shiki-Colors?content=86717
Icons: http://www.gnome-look.org/content/show.php/GNOME-colors?content=82562

Nice and simple.

0

Failed Kernel Upgrade

The other day I upgraded my Gentoo kernel (after realizing I was about 7 kernel updates old). After compiling and setting up Grub, I rebooted and received this error:

RAMDISK: Compressed image found at block 0
RAMDISK: ran out of compressed data
invalid compressed format (err=1)
UDF-fs: No VRS found
List of all partitions:

No file system could mount root, tried: …
Kernel panic – not syncing: VFS: unable to mount root fs on unknown-block(1,0)

After painful research, I finally discovered the problem: I ran out of space on my boot partition.

Apparently genkernel does not complain when it runs out of space to compile the kernel. It just stops and outputs the same message it would it if succeeded.

A “quick” use of parted to allocate more space to the boot partition, and re-compiling the kernel solved the problem. It’s just sad that genkernel doesn’t bother reporting the fact that it ran out of space.

0

Windows -> Linux Path Problems

I had one hell of a time when I copied my Ruby on Rails application from my development machine (Windows XP, Apache 2.2) to my production machine (Linux, Apache 1.3). I floundered through a series of errors and problems, but one error really stumped me, and unfortunately I couldn’t find much help on the net for it:

Application error (Rails)

It took me forever to get past this problem, but I finally figured it out. The first line of a few files in the public/ folder contained a path to the Ruby binaries.

#!C:/ruby/bin

For obvious reasons, this wasn’t going to fly well on a *nix server. So I had to change it in the following files: dispatch.cgi, dispatch.fcgi, dispatch.rb.

In my instance, it was changed to:

#!/usr/local/bin/ruby

But obviously your server might be different. Try exploring /usr/local and /usr/bin or using locate ruby to try to find the correct path to Ruby.

After I made this modification the application worked fine.

Copyright © 2010 — phup 'n stuff | Site design by Trevor Fitzgerald