Comments on: My plan for the gnome buildbot

By: itoral

itoral — Thu, 05 Jul 2007 11:02:10 +0000

Yeah, that is fixed already. The problem has to do with some binary chars that jhbuild inserts to format text in console. I fixed that some time ago, but there were still some build logs with these chars inside, I’ve cleaned all logs and rebuild again, that should make feeds work anywhere again.

Thanks for warning.

By: Murray Cumming

Murray Cumming — Thu, 05 Jul 2007 10:39:31 +0000

I love that there are RSS and Atom feeds but Firefox can’t seem to subscribe to them – nothing happens when clicking the Subscribe button.

The captcha here is far too difficult.

By: itoral

itoral — Thu, 05 Jul 2007 10:31:03 +0000

Thanks for looking after this. If you need to make any changes to jhbuild modulesets warn me (I’ll likely need to do some updates in that case).

Thanks also for the hint about the catchpa, I’ll ask our sysadmin to look for a fix to this.

By: Don Scorgie

Don Scorgie — Thu, 05 Jul 2007 10:13:08 +0000

re: the new failure.

Yep, that was the next error I saw after I fixed the first. Unfortunately, it was getting late and it’s a bit beyond my knowledge. I managed to hack around it only to run into another error. I’ve ping the Grand Master shaunm, but so far, nothing.

Oh, and once I finish work, I’ll make an effort to replace scrollkeeper with Rarian in jhbuild, which should remove the scrollkeeper problem (since, you know, different package).

(BTW, you’re catchpa is pretty difficult to read. It’d be useful to have a “regenerate” button next to it)

By: itoral

itoral — Thu, 05 Jul 2007 10:04:32 +0000

No yet, but you can subscribe to the RSS feed of failed builds. We will probably add email notification too in the future.

By: Vincent Untz

Vincent Untz — Thu, 05 Jul 2007 09:53:49 +0000

Re: “the good way to go here would be that project maintainers and core developers (at least) subscribe to the modules they are experts on”

Is there a feature to receive a mail when a build fails for a module?

By: itoral

itoral — Thu, 05 Jul 2007 09:11:56 +0000

Great, thanks!

Unfortunately, the error I get now when building is not in make check, but still in make, what prevents it from being installed (it would not matter that much if it was in make check):

Making all in xslt
make[3]: Entering directory `/usr/local/buildslave/gnome/work/src/gnome-doc-utils/doc/xslt’
[...]
xsltproc -o gnome-doc-xslt-C.omf –stringparam db2omf.basename gnome-doc-xslt –stringparam db2omf.format ‘docbook’ –stringparam db2omf.dtd “-//OASIS//DTD DocBook XML V4.4//EN” –stringparam db2omf.lang C –stringparam db2omf.omf_dir “/usr/local/buildslave/gnome/work/bin/share/omf” –stringparam db2omf.help_dir “/usr/local/buildslave/gnome/work/bin/share/gnome/help” –stringparam db2omf.omf_in “/usr/local/buildslave/gnome/work/src/gnome-doc-utils/doc/xslt/gnome-doc-xslt.omf.in” –stringparam db2omf.scrollkeeper_cl “`scrollkeeper-config –pkgdatadir`/Templates/C/scrollkeeper_cl.xml” ../../xslt/docbook/omf/db2omf.xsl C/gnome-doc-xslt.xml || { rm -f “gnome-doc-xslt-C.omf”; exit 1; }
Running xsldoc checks
The stylesheet db-common calls an undefined template l10n.gettext

Full details here:
http://build.gnome.org:8080/gnome-doc-utils/gnome-doc-utils-RHEL5/builds/18/step-gnome-doc-utils%20build/0

By: Don Scorgie

Don Scorgie — Thu, 05 Jul 2007 08:33:57 +0000

I fixed that build error last night
Unfortunately, there is a further error (in make check I believe) that was beyond me last night