This wasn’t a serious mistake and the only reason it took a while to sort out was my amazing thickness.
I had removed pciutils (and thereby lspci) from the system thinking that “now everything works, so I won’t ever need it again”. Just to show me the error of my ways the benevolent Debian decided to punish me by not giving me network. It turned out that Linux’ excellent support for a multitude of network cards worked against me on this one—which one to insert? After several uninspired thoughts I had an inspired one. Brute force! Insert them all!
# cd /lib/modules/2.6.17-2-686/kernel/drivers/net
# for f in *.ko; do insmod $f; done
A few error messages later I tried ifup eth0, and it worked Quick download of pciutils. Now I know the machine in question requires eepro100 to get network. I recorded that in /etc/modules.
At the moment I’m having a hard time resisting removing pciutils. I mean, now everything works, I won’t ever need it again, right?
Brett Parker’s been packaging django for Debian and making it available to the world. The latest update was just 2 weeks ago. Unfortunately the packages seem to have been made before the very recent move to Python 2.4 in Debian Sid, so they aren’t installable without downgrading
I just noticed that epilicious doesn’t work for me It seems the recent work done by the Python group in Debian Sid has resulted in the following line throwing an exception:
from elementtree.ElementTree import parse
Yes, I’ve double checked that python-elementtree is installed (python-celementtree is also installed). At the moment I’m too lazy to look into it myself and I’ve sent off an email to the Debian user list.
I just noticed that BZR 0.8 has been uploaded to Debian Sid. I’ve switched my repos to use that version’s default storage format. This means that you might have problems using my repos with earlier versions… You have been warned.