Skip to content

One week to go...

In a week I'll be in Dublin already. My flight will leave at 13:00 and will arrive 13:35. (Don't you just love timezones?) So then I'll hopefully post more frequently.

Got one week then to get familiar with the city, and on Wednesday I'll have my "one day home search", which means someone will show me eight houses and I can make a decision and hopefully move into that house pretty soon then. :-D Until that happens I got temporary accomodation just around the corner from Google, so that's great. I can walk to work. :-)

Have to say I'm looking forward. It'll be an exciting time, I'm pretty sure about that.

Meanwhile I'm just trying to relax a bit. My long semi-holiday is almost over. Planning just the last things I can do while I'm still here. Meet some people, instruct my successor at my former job on Friday, etc. It'll be strange to be away from here for so long...

And of course I'm happy that testing.bitlbee.org is back in the air! It also helped me to find some very strange bugs that happen when using libevent and epoll and running BitlBee in ForkDaemon mode. Did you ever see processes receiving each other's event notifications? I did. ;-)

Oh yes, blog!

Just back from a short trip to Belgrade, and now I'm in the last days of my current job. As I could expect, time is running out, and there's always more to do than I thought, also thanks to having some "bad luck" with the only server with only one hard drive (yes, I know RAID != backup) and broken backup software. Suddenly it turns out that debugfs is not quite the best data recovery tool after all. ;-)

Meanwhile preparations for Dublin started. Looks like I'll go there on the 17th of January already to spend the rest of that week on an introduction tour through the city and another day for looking at some houses that might be good for me.

Meanwhile I didn't have too much time for hacking. The new BitlBee Jabber module isn't completely finished yet, I'm afraid. Would be nice to find some time for it soon...

Oh yes, and the following quote is making me a bit nervous: "All systems administrators have their horror stories. For me, it was setting up a HP Color Bubblejet under Linux using ghostscript before linuxprinting.org was alive. Well that was a piece of cake compared to what I am about to describe in this document."

I know how terrible the Linux printing hell is, so maybe I should go for Maildir after all... ;-) Continue reading "Oh yes, blog!"

.deb files are ar archives, but ...

Just to express my frustration of the day a bit. I want the left column to be higher than the right one here. ;-)

From time to time you hear people boasting that they can use standard tools to handle .deb archives. "ar x blablah_0.123-4_z80.deb" and you get two standard tar.gz files to play with. That's indeed convenient, more convenient than rpm2cpio.

However, just try, on a Linux system, to convert those two tarballs (and the debian-binary file, of course) back to a .deb. "ar cr blablah_0.123-4.1_z80.deb debian-binary control.tar.gz data.tar.gz" will do, right? Try to install it using dpkg... Yes, it works! But then, try to put it in your apt repository!

QUOTE:
pool/main:
E: This is not a valid DEB archive, missing 'debian-binary' member
E: Errors apply to file 'iso/pool/main/b/base-installer/base-installer_1.42ubuntu12_amd64.udeb'


Turns out that there are multiple ar formats and that Debian uses a very simple format and doesn't (fully) support the ar files produced by GNU ar. It's quite confusing that dpkg does support these files while apt does not. Some consistency (or at least packaging a version of ar that is compatible with apt) would be nice, guys.

Anyway, to not be too negative in this post: debian-installer is pretty cool, once you understand the internals a little bit. I just spent a couple of days now on customizing an USB stick installation image, and I think I understand the system at least for a few percents by now. ;-) Have to find the limits of what can be done with preseeding files now. Having fun!

... What ... if anyone reads this? Dunno. :-P

(See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=161593)