jd:/dev/blog

Everything seems to work, so just releasing it. I think it's becoming an amazing tool to do archive rebuild.

It just misses a good Web interface.

Googling around using the rebuildd keyword to find if people were talking about it, I found that patch from Ubuntu.

This patch is used to ship rebuildd Debian package in Ubuntu.

Wahou. First surprise! So, Ubuntu is fixing bugs and not telling me. I though that people saying "Ubuntu does not contribute back to Debian!" were exaggerating. Seems I was wrong.

Nevermind: I take the patch. I read the patch. I apply the pat… oh wait: the fix is wrong.

lol.

Running rebuildd for real since 48 hours, I've found some nasty bugs I have been able to fix. One of the biggest was me trying to do things that Python understood in a different maner, so it was quite interesting.

I'm now very happy about that project. From my point of view, I really managed to write a build handler daemon in a very better and more modern way that buildd used to do. It really fits my needs, and it's a real pleasure to use it. Ok, ok. stopping the self-congrats stuff.

I've updated the Web page to be more close to the 0.2.1 version.

After reading Mike Hommey's idea about buildd network for QA testing, I decided to try to implement the 10.1 policy recommendations check using rebuildd.

Here is how I proceeded.

Install and configure rebuildd

This is done by apt-get install rebuildd. Then, init database (I use sqlite) with rebuildd init.

Then I initialized build system with rebuildd-init-build-system. I had to add nostrip to DEB_BUILD_OPTIONS, so I decided to do quick and dirty and I edited /usr/bin/dpkg-build-package adding the good export info in the first lines.

Configuration file and post build cmd

My configuration file is simple and the one by default: I only changed email addresses and add a post_build_cmd script.

Here's the code for the script:

#!/bin/sh
dist=$1
pkg=$2
version=$3
arch=`dpkg --print-architecture`
RET=0
cd /var/cache/pbuilder/result || exit 1

for file in $(grep '.deb$' ${pkg}_${version}_${arch}.changes |cut -d\  -f6)
do
	echo Checking $file for stripped binaries...
	echo ---------------------------------------
	mkdir /tmp/$file
	dpkg -x $file /tmp/$file
	find /tmp/$file -type f | (while read line
	do 
		L=$(file $line | egrep 'ELF.*, stripped')
		if test ! -z "$L"
		then
			echo $L
			RET=1
		fi
	done; exit $RET)
	RET=$?
	rm -rf /tmp/$file
done
echo
echo ...done

echo Removing result files...
for file in $(grep-dctrl -sFiles . ${pkg}_${version}_${arch}.changes | sed '1d' | cut -d\  -f6)
do
	rm -f $file
	rm -f /var/cache/rebuildd/build/$file
done
rm -f ${pkg}_${version}_${arch}.changes
echo ...done

exit $RET

Fille the db

Then I fill the database with:

grep-dctrl -sPackage,Version .  /var/lib/apt/lists/ftp.fr.debian.org_debian_dists_sid_main_source_Sources | cut -d: -f2- | tr '\n' ' ' | sed 's/   /\n/g'| sed 's/  / /' | xargs -L1 -ixxxxxx echo xxxxxx sid | rebuildd-job add

And finally I just have to start rebuildd and let it do the job.

Argh, already 3 build logs received with stripped binaries…

Update: Bug list can be found here

Ahaha, no sorry, no 2.0 features for rebuildd yet.

I'm a bit lazy about implementing the Web interface, The problem is that everything is quite ready for it as you can see on demo server, but I can't convince myself to do HTML. I'm bad and even using mako templates and looking on different Python Web frameworks can't help me. I can't bear doing HTML pages, I don't know how to do clean things with CSS. And I don't want to learn.

A friend pointed me to Paste which should do a lot of things for me, but I'm too lazy to try to read this.

Actually, everything on the job-management side is quite ok. I'm just lacking of a Web interface to have a nicer overview of what's going on.

Anyway, I still like to do useless coding on client eye candy:

By the way, any help would be welcome.

During the last five days, I made a bunch of updates to rebuildd:

35 files changed, 709 insertions(+), 190 deletions(-)

That's mainly small enhancements, and a brand new Debian packaging. It's now very usable from my point of view. Moreover, the repository is now on Alioth.

There's still some code improvement to do and some features to add, but I'm quite happy with it.

Consequently, I just released the first version, numbered 0.1.0.

Last week I decided to begin a new project, whose name is now rebuildd.

If the name is not explicit to you, let me explain: it's like buildd, but its first purpose is to rebuild packages.

If you want to know more, you can take a look on the Web page I just set up.