[Soc-coordination] Report 4 - Clang for build services
al.pashaliyski at gmail.com
Sun Jul 29 19:49:32 UTC 2012
Here is my report number 5. In these weeks:
I wrote complete documentation about setting up wanna-build, reprepro and
buildd ( and ). This makes a fully functional buildd infrastructure.
Now we have a full step by step tutorial.
I discussed my work with my mentor and we decided what should be kept the
way it is and what should be changed. As a result I made some changes to my
scripts. I also updated my patches to match the most recent versions of the
packages from git.
I set up another Debian sid development system the way it is explained in
the documentation and made a lot of tests. Everything works fine.
Me and my mentor set up the whole buildd infrastructure on a public server.
In the process we found some flaws in the documentation. All these flaws
are fixed in the most recent version of the documentation.
Together we modified the buildd daemon so it will be possible to be run
several instances of it for different architectures on a single physical
I reported a problem in the manual page of reprepro and send a patch that
fixes it. Then the project maintainer applied the patch.
It turned out there are some other things that need to be done. So me and
my mentor added a few new points to the project plan:
* Fix a view in the wanna-build database. It prevents a feature of pgstatus
* At the start of the chroot, see if we can setup a hook which will
configure the environment.
The idea behind is to install automatically clang from the repository and
update the alternatives before doing anything.
* We have to make sure that the package won't build with gcc or g++. We
want to fail the build if it is forced by the package.
* From the postgresql database results, generate something similar to 
Basically, we will need a list with:
- the name of the package
- status (failure, need to build, success)
- the url to the last log error
The points described above are already done. I added a new feature in
pgstatus that allows the user to create a full report of the state of all
builds. When a designated reports page is opened, a table with the current
state of the builds is shown, together with a list of all the reports saved
to files for the current distribution and architecture. The reports can be
downloaded directly from the interface. They are stored in JSON format.
We also contacted the Debian wanna-build team to connect our new service
with Debian. We explained what the current state of the project is and what
we need from them.
As of today the project progress is as planned. If there are no problems in
the next few weeks everything will be finished on schedule. The changes I
made should be applied to the corresponding packages and that doesn't
depend on me so I can't be sure it will all be done on time.
I thank my mentor for his presentation on DebConf 12. He showed our project
and it was seen that people are interested in it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Soc-coordination