[gnome-love] Tinderbox (automatic daily build) for GNOME

[Luis Villa]

Hi Jerome, hi Guillaume,

[..]

What do the people from Brussels and others think about this?
Jerome, can you still offer your machine and the hosting?

As you may have noticed, Frederic, Guillaume and I are all members of
the same LUG, and we worked together to support and improve Fred's work.
The server is doing nicely with the builds already.
We setup both AMD64 and IA32(aka x86) builds, of which only AMD64 is
automated for now.
We'll try to setup more flavours in other chroots on the same machine as
felt needed (like maybe Ubuntu?).

If you're brave, the obvious thing to try is solaris x86 :)

[Sergio, I owe you two emails; I will try to do those tonight when I
leave work.]

Also, should we move this to gnome-packaging-list instead of
gnome-love? I'm sure the non-tinderbox hackers on gnome-love are sick
of us by now :)

Luis

[Glynn Foster]

Post by Luis Villa

Jerome, can you still offer your machine and the hosting?

As you may have noticed, Frederic, Guillaume and I are all members of
the same LUG, and we worked together to support and improve Fred's work.
The server is doing nicely with the builds already.
We setup both AMD64 and IA32(aka x86) builds, of which only AMD64 is
automated for now.
We'll try to setup more flavours in other chroots on the same machine as
felt needed (like maybe Ubuntu?).

If you're brave, the obvious thing to try is solaris x86 :)

For anyone who doesn't already know, Sun donated a box to GNOME explitly
for this purpose - we hope to get a tinderbox running on the Solaris
machine. Not sure what the ETA for this stuff is though.


Glynn

[Alejandro Garcia Castro]

[...]
Hard Requirements For a New Tinderbox Tool/Setup
* Supports Big List O'Modules: Support building a long chain of
modules- jhbuild is well north of 100 modules now for a default gnome
build. This may seem obvious, but it is relevant- at least some build
tools are basically optimized for one module/one checkout scenarios,
and as a result, some off-the-shelf stuff doesn't work for us.
[...]
* Documented: How the tool was made to work with GNOME must be
written down so that others can maintain it and use it. We've had too
many tools like this that were made to run once by a mad genius who
then left the project, or lost interest, and so when it broke we just
had to discontinue the service.

My two cents:
* Security, logs may be authenticated, maybe signed some way,
encription should not be an important requirement.
* Deployment, it would be nice if the compilation package for the
people running the integration process will be easily installed and
configured (.rpm, .deb, tar.gz packages), it must not have much
requirements, both software and connections.
* Regression testing, performance, memory, etc. Should be integrated
in the results and even in the information in the future: valgrinded
executions, profiling tests (maybe with some kind of conditions which can
cause an error), etc.
* Erros parsers easily modified, it would be interesting if they could
be independent of the client type: architecture, compiler, etc.
* Report in different formats and information summaries, that way a
lot of places can integrate different information from the main integration
site.

[Alejandro Garcia Castro]

[...]
I am one of the build guys over at Mozilla; I would be really curious
to know your initial impressions and how you use tinderbox. We are looking
at improving our own build infrastructure, so I have been watching
this conversation with some interest, and trying to get a feel for
what else is out there (buildbot seems quite popular).
What version of tinderbox are you looking at? Also are you considering
doing releases from it, or just using it as a sanity check (e.g.
"continous integration" vs. "autobuilder")?

We are using tinderbox2, if it is the selected solution for Gnome we will
talk to Mike Taylor in order to upload to the Mozilla repository the
required changes to compile with jhbuild. I think release construction is
not added to the requirements in this moment, but IMHO it can be a nice
bonus feature if it can help to the release team some way.

Regards.

[bear]

Post by Alejandro Garcia Castro

[...]
What version of tinderbox are you looking at? Also are you considering
doing releases from it, or just using it as a sanity check (e.g.
"continous integration" vs. "autobuilder")?

We are using tinderbox2, if it is the selected solution for Gnome we will
talk to Mike Taylor in order to upload to the Mozilla repository the
required changes to compile with jhbuild. I think release construction is
not added to the requirements in this moment, but IMHO it can be a nice
bonus feature if it can help to the release team some way.

In our tinderbox2 setup at OSAF we also have a routine at the end of the
build script that pushes the distribution bits to a staging server. It
first checks that all unit and functional tests have passed.

Given the basic nature of tinderbox2 client scripts, this is rather easy
to setup.

I would be glad to migrate into the tinderbox2 source tree any jhbuild
related changes - it would be a nice addition.

---
bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
***@osafoundation.org

[James Andrewartha]

Post by Luis Villa

As you may have noticed, Frederic, Guillaume and I are all members of
the same LUG, and we worked together to support and improve Fred's work.
The server is doing nicely with the builds already.
We setup both AMD64 and IA32(aka x86) builds, of which only AMD64 is
automated for now.
We'll try to setup more flavours in other chroots on the same machine as
felt needed (like maybe Ubuntu?).

If you're brave, the obvious thing to try is solaris x86 :)

I've just got Solaris/SPARC/gcc up and running:
http://jhbuild.bxlug.be/builds/2006-04-04-0004/

I'm using the jhbuildrc from
http://cvs.gnome.org/viewcvs/microtinder/jhbuildrc although updated for
2.16. Additionally, since I'm behind a firewall I added http proxy
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

Post by Luis Villa
From my point of view the most interesting thing would be to support

running builds in parallel, as this machine has 14 CPUs and 12GB of RAM,
but configure and checkout are usually the slowest parts of a build and
can't be parallelised by make -j. Davyd started something to do this at
http://cvs.gnome.org/viewcvs/jhfarmer/ but never got around to making it
actually build.

Regardless, the machine has CPU to burn, so I'm willing to test out
other tinderboxing setups people are working on - Sergio, can you
provide instructions on how to configure your tinderboxing setup? I also
remember Glynn talking about tinderboxing JDS ...

James Andrewartha


This goes into jhbuild/jhbuild/utils/HTTPProxyTransport.py and then
jhbuild/jhbuild/frontends/autobuild.py is modified to import
jhbuild.utils.HTTPProxyTransport and have
transport=jhbuild.utils.HTTPProxyTransport.HTTPProxyTransport() in
self.server = xmlrpclib.ServerProxy

#Nasty http proxy transport for xmlrpclib

import xmlrpclib

class HTTPProxyTransport(xmlrpclib.Transport):
def make_connection(self, host):
import httplib
host, extra_headers, x509 = self.get_host_info(host)
self.realhost = host
return httplib.HTTP("proxy.host", 3128) #hardcoded, eh

def send_request(self, connection, handler, request_body):
connection.putrequest("POST", "http://%s%s" % (self.realhost,
handler))

[Jerome Warnier]

Post by James Andrewartha

Post by Luis Villa

As you may have noticed, Frederic, Guillaume and I are all members of
the same LUG, and we worked together to support and improve Fred's work.
The server is doing nicely with the builds already.
We setup both AMD64 and IA32(aka x86) builds, of which only AMD64 is
automated for now.
We'll try to setup more flavours in other chroots on the same machine as
felt needed (like maybe Ubuntu?).

If you're brave, the obvious thing to try is solaris x86 :)

http://jhbuild.bxlug.be/builds/2006-04-04-0004/

Welcome then. I followed your tries, and it seems it does not get really
far so far, though.

Post by James Andrewartha
I'm using the jhbuildrc from
http://cvs.gnome.org/viewcvs/microtinder/jhbuildrc although updated for
2.16. Additionally, since I'm behind a firewall I added http proxy
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

Also:
- have a "failed" output on the console when a module fails. Currently,
there is no output at all that says "failed".
- the output is not sent on stdout apparently, so "tail -f" on nohup.out
when started using nohup or the mail of cronjob do not show anything
useful.

Post by James Andrewartha

Post by Luis Villa
From my point of view the most interesting thing would be to support

running builds in parallel, as this machine has 14 CPUs and 12GB of RAM,
but configure and checkout are usually the slowest parts of a build and
can't be parallelised by make -j. Davyd started something to do this at
http://cvs.gnome.org/viewcvs/jhfarmer/ but never got around to making it
actually build.

There are already several documents written in the Wiki about //
building.
In short:
- inside a module, we know that some modules break while built in //.
- having jhbuild building several independent modules in // would be great.

[..]

Post by James Andrewartha
James Andrewartha

[..]

[James Andrewartha]

Post by Jerome Warnier

Post by James Andrewartha
http://jhbuild.bxlug.be/builds/2006-04-04-0004/

Welcome then. I followed your tries, and it seems it does not get really
far so far, though.

Yes, I'm hitting some linking issues - solaris libc has an iconv, but I want
to use the GNU iconv I have installed in /opt/csw/lib. Most things pick it
up from LDFLAGS=-L/opt/csw/lib, but often the linker doesn't include this
path in the ELF header (or something). Davyd reckons it's a lack of
-Wl,rpath -L/opt/csw/lib, but it's pot luck as to which modules work and
which don't - although some have a config.rpath which may be what makes it work.

[Jerome Warnier]

Post by James Andrewartha

Post by Jerome Warnier

Post by James Andrewartha
http://jhbuild.bxlug.be/builds/2006-04-04-0004/

Welcome then. I followed your tries, and it seems it does not get really
far so far, though.

Yes, I'm hitting some linking issues - solaris libc has an iconv, but I want

First question: why not use Solaris' iconv? I would imagine using most
tools from the original OS, when available and not too broken, would be
better. If it does not work, maybe try to fix it instead of installing
more and more "external" software.

Post by James Andrewartha
to use the GNU iconv I have installed in /opt/csw/lib. Most things pick it
up from LDFLAGS=-L/opt/csw/lib, but often the linker doesn't include this
path in the ELF header (or something). Davyd reckons it's a lack of
-Wl,rpath -L/opt/csw/lib, but it's pot luck as to which modules work and
which don't - although some have a config.rpath which may be what makes it work.

Couldn't you play with your moduleset of jhbuild and the "autogenargs" option?
Anyway, I would see this as bugs in the corresponding modules, and would
report them to the matching BTS as found.

[James Andrewartha]

Post by Jerome Warnier

Post by James Andrewartha

Post by Jerome Warnier

Post by James Andrewartha
http://jhbuild.bxlug.be/builds/2006-04-04-0004/

Welcome then. I followed your tries, and it seems it does not get really
far so far, though.

Yes, I'm hitting some linking issues - solaris libc has an iconv, but I want

First question: why not use Solaris' iconv? I would imagine using most
tools from the original OS, when available and not too broken, would be
better. If it does not work, maybe try to fix it instead of installing
more and more "external" software.

Last time I was tinderboxing I used it because glib was using it
http://mail.gnome.org/archives/gnome-packaging-list/2005-August/msg00001.html
I'll poke glib to see if it can use the native iconv - I suspect it was just
picking gnu iconv because it was the first one in LDFLAGS.

Post by Jerome Warnier

Post by James Andrewartha
to use the GNU iconv I have installed in /opt/csw/lib. Most things pick it
up from LDFLAGS=-L/opt/csw/lib, but often the linker doesn't include this
path in the ELF header (or something). Davyd reckons it's a lack of
-Wl,rpath -L/opt/csw/lib, but it's pot luck as to which modules work and
which don't - although some have a config.rpath which may be what makes it work.

Couldn't you play with your moduleset of jhbuild and the "autogenargs" option?
Anyway, I would see this as bugs in the corresponding modules, and would
report them to the matching BTS as found.

When I've got time I'll try and isolate the problem. My auto*- and
linking-fu aren't all that strong so I'll see if using native iconv fixes
the problem first.

[Frederic Peters]

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.



Regards,
Frederic

[Frederic Peters]

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.



Frederic

[Luis Villa]

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It seems like we've got a lot of things building, but very few builds
going to green. I haven't skimmed all the logs- is it that things
really are broken, or just that the build roots haven't been given
enough love to get them working right the first time?

Luis

[Luis Villa]

Post by Luis Villa

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It seems like we've got a lot of things building, but very few builds
going to green. I haven't skimmed all the logs- is it that things
really are broken, or just that the build roots haven't been given
enough love to get them working right the first time?

Whoa! I just started my own build again:

http://jhbuild.bxlug.be/builds/2006-04-15-0005/

And it tells me I have a regression... that rocks!

[Reads the log a bit...]

Ah-ha. I'm guessing that this is caused because I did not re-autogen
and languages changed. Perhaps to reduce false positives the tinderbox
mode could force -a?

[Also, I can no longer figure out how to cancel a build... did I just
forget where it was, or did it get taken away?]

Luis

Luis

[Luis Villa]

Post by Luis Villa

Post by Luis Villa

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It seems like we've got a lot of things building, but very few builds
going to green. I haven't skimmed all the logs- is it that things
really are broken, or just that the build roots haven't been given
enough love to get them working right the first time?

http://jhbuild.bxlug.be/builds/2006-04-15-0005/
And it tells me I have a regression... that rocks!
[Reads the log a bit...]
Ah-ha. I'm guessing that this is caused because I did not re-autogen
and languages changed. Perhaps to reduce false positives the tinderbox
mode could force -a?
[Also, I can no longer figure out how to cancel a build... did I just
forget where it was, or did it get taken away?]

I'm just stupid (and I've lost my password). That said, maybe it
should automatically cancel if a new build is started from the same
machine, since currently it thinks I have three builds going on the
same machine :)

i might also suggest making the front page look a little more like
what I've attached (terribly ugly mockup, but you get the idea) so
that it is easier to find out at a glance what is ongoing and what has
broken/succeeded in the past.

Anyway, this continues to rock-

Luis

[Frederic Peters]

Post by Luis Villa
http://jhbuild.bxlug.be/builds/2006-04-15-0005/
And it tells me I have a regression... that rocks!

I was away those last days, I hope to get back working on jhbuild by
the end of the week.


Regards,

Frederic

[Frederic Peters]

Post by Luis Villa
i might also suggest making the front page look a little more like
what I've attached (terribly ugly mockup, but you get the idea) so
that it is easier to find out at a glance what is ongoing and what has
broken/succeeded in the past.

Not yet integrated on the frontpage, I tried two things:

http://jhbuild.bxlug.be/index2
http://jhbuild.bxlug.be/index3

index2 has builds grouped by time (3-hour sections), this may help to
see when things start to go wrong but will have large empty parts.

Columns are for top-4 builders (for last ten days).


Waiting for comments, regards,


Frederic

[James Andrewartha]

Post by Frederic Peters

Post by Luis Villa
i might also suggest making the front page look a little more like
what I've attached (terribly ugly mockup, but you get the idea) so
that it is easier to find out at a glance what is ongoing and what has
broken/succeeded in the past.

http://jhbuild.bxlug.be/index2
http://jhbuild.bxlug.be/index3
index2 has builds grouped by time (3-hour sections), this may help to
see when things start to go wrong but will have large empty parts.
Columns are for top-4 builders (for last ten days).

http://lxr.mozilla.org/webtools/source/tinderbox3/server/Tinderbox3/ShowBuilds.pm
is the code for the mozilla tinderbox which has adapative time periods.

Access to the full history of builds would be very useful, currently I
have to guess URLs to find my older builds.

James Andrewartha

[Frederic Peters]

Post by James Andrewartha
http://lxr.mozilla.org/webtools/source/tinderbox3/server/Tinderbox3/ShowBuilds.pm
is the code for the mozilla tinderbox which has adapative time periods.

I'll look at this but my perl-fu is low.

Post by James Andrewartha
Access to the full history of builds would be very useful, currently I
have to guess URLs to find my older builds.

Primitive access from http://jhbuild.bxlug.be/builds/machines/trs80-manbo/


Regards,
Frederic

[James Andrewartha]

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It's slightly broken - I changed all occurrences of self.verbose in
frontends/autobuild.py with self.config.verbose, except for the
verbose=False which I removed. It also doesn't print the phase log when
there's a failure.

What's the difference between an aborted build and trashed build?

In other news,
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/gtk-doc/#configure
vs
http://jhbuild.bxlug.be/builds/2006-04-04-0011/logs/gtk-doc/#configure

iconv still sucks in fontconfig
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/fontconfig/#build
https://bugs.freedesktop.org/show_bug.cgi?id=4083

SHELL=/bin/sh is nasty on solaris
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/shared-mime-info/#install
http://webcvs.freedesktop.org/mime/shared-mime-info/po/Makefile.in.in?rev=1.3&view=markup
and http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/dbus/#build
http://webcvs.freedesktop.org/dbus/dbus/dbus/make-dbus-glib-error-enum.sh?rev=1.3&view=markup

PolicyKit dependency on dbus not specified
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/PolicyKit/#configure

Lots of X crack I'm not even going to touch. Sleep now.


James Andrewartha

[Luis Villa]

Post by James Andrewartha

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It's slightly broken - I changed all occurrences of self.verbose in
frontends/autobuild.py with self.config.verbose, except for the
verbose=False which I removed. It also doesn't print the phase log when
there's a failure.
What's the difference between an aborted build and trashed build?
In other news,
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/gtk-doc/#configure
vs
http://jhbuild.bxlug.be/builds/2006-04-04-0011/logs/gtk-doc/#configure
iconv still sucks in fontconfig
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/fontconfig/#build
https://bugs.freedesktop.org/show_bug.cgi?id=4083
SHELL=/bin/sh is nasty on solaris
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/shared-mime-info/#install
http://webcvs.freedesktop.org/mime/shared-mime-info/po/Makefile.in.in?rev=1.3&view=markup
and http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/dbus/#build
http://webcvs.freedesktop.org/dbus/dbus/dbus/make-dbus-glib-error-enum.sh?rev=1.3&view=markup
PolicyKit dependency on dbus not specified
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/PolicyKit/#configure
Lots of X crack I'm not even going to touch. Sleep now.

The habit should be to report these kinds of things on desktop-devel,
where they get attention.

Luis

[Jerome Warnier]

Post by James Andrewartha

Post by Frederic Peters

Post by Frederic Peters

Post by James Andrewartha
support to xmlrpclib (see file at bottom). Frederic: Would it be
possible to add an option to print output to stdout like a normal
jhbuild? It'll make fixing local build problems a lot easier.

I'll prepare that.

Untested but attached; add --verbose, it will dispay short notices and
display the phase log on failures.

It's slightly broken - I changed all occurrences of self.verbose in
frontends/autobuild.py with self.config.verbose, except for the
verbose=False which I removed. It also doesn't print the phase log when
there's a failure.
What's the difference between an aborted build and trashed build?

I think that aborted means that you killed the process (well, at least
you know that it is not running anymore) while the jhautobuild server
does not know about it being aborted.
Trashed is when you judge it is not worth being kept in the logs any
longer (being previously aborted or failed).

Post by James Andrewartha
In other news,
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/gtk-doc/#configure
vs
http://jhbuild.bxlug.be/builds/2006-04-04-0011/logs/gtk-doc/#configure

[..]

Post by James Andrewartha
SHELL=/bin/sh is nasty on solaris
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/shared-mime-info/#install
http://webcvs.freedesktop.org/mime/shared-mime-info/po/Makefile.in.in?rev=1.3&view=markup
and http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/dbus/#build
http://webcvs.freedesktop.org/dbus/dbus/dbus/make-dbus-glib-error-enum.sh?rev=1.3&view=markup
PolicyKit dependency on dbus not specified
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/PolicyKit/#configure
Lots of X crack I'm not even going to touch. Sleep now.

Seeing those, I guess you are the person running jhbuild on a Solaris 11
Sparc?
I just wanted to let you know that I reported the following bug because
of your build logs:
http://bugzilla.gnome.org/show_bug.cgi?id=339060 (gnome-user-docs build
failure)

Post by James Andrewartha
James Andrewartha

[James Andrewartha]

Post by Jerome Warnier

Post by James Andrewartha
In other news,
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/gtk-doc/#configure
vs
http://jhbuild.bxlug.be/builds/2006-04-04-0011/logs/gtk-doc/#configure

User error - turns out a few packages had been removed from my system
that contained the Docbook DTDs.

Post by Jerome Warnier

Post by James Andrewartha
SHELL=/bin/sh is nasty on solaris
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/shared-mime-info/#install
http://webcvs.freedesktop.org/mime/shared-mime-info/po/Makefile.in.in?rev=1.3&view=markup

https://bugs.freedesktop.org/show_bug.cgi?id=6701
although there's still the libiconv problem. Some looking around in
bugs.fd.o finds https://bugs.freedesktop.org/show_bug.cgi?id=2774 which
says I should add
LDFLAGS="-R<path_to_libiconv> <path_to_libiconv>/libiconv.so"
although I think this will only work if I'm using GNU iconv. Possibly
removing the GNU iconv installation would work, but it's depended on by
a whole lot of other blastwave.org packages so I can't get rid of it.

So I'm going back to GNU iconv instead of the native solaris libc iconv.

Post by Jerome Warnier

Post by James Andrewartha
and http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/dbus/#build
http://webcvs.freedesktop.org/dbus/dbus/dbus/make-dbus-glib-error-enum.sh?rev=1.3&view=markup

https://bugs.freedesktop.org/show_bug.cgi?id=6700

Post by Jerome Warnier
Seeing those, I guess you are the person running jhbuild on a Solaris 11
Sparc?
I just wanted to let you know that I reported the following bug because
http://bugzilla.gnome.org/show_bug.cgi?id=339060 (gnome-user-docs build
failure)

Cool, thanks.

James Andrewartha

[Jerome Warnier]

Le jeudi 20 avril 2006 à 01:42 +0800, James Andrewartha a écrit :
[..]

Post by James Andrewartha
PolicyKit dependency on dbus not specified
http://jhbuild.bxlug.be/builds/2006-04-19-0008/logs/PolicyKit/#configure

And I submitted bug #339087 for this.
See: http://bugzilla.gnome.org/show_bug.cgi?id=339087
Similar to bug #339060.

Post by James Andrewartha
Lots of X crack I'm not even going to touch. Sleep now.
James Andrewartha

[Frederic Peters]

Post by James Andrewartha
It's slightly broken - I changed all occurrences of self.verbose in
frontends/autobuild.py with self.config.verbose, except for the
verbose=False which I removed. It also doesn't print the phase log when
there's a failure.

I'm back and updated source files on:
http://jhbuild.bxlug.be/downloads/jhbuild/commands/autobuild.py
http://jhbuild.bxlug.be/downloads/jhbuild/frontends/autobuild.py

--verbose now works much like the terminal (default) jhbuild mode
(without interactivity on failure).

Post by James Andrewartha
What's the difference between an aborted build and trashed build?

'Trashed build' was added for builds who complete but without doing
anything useful (for example if glib fails to checkout due to network
timeout).



Frederic