On 20 February 2012 13:30, Wookey woo...@wookware.org wrote:
Me too. Almost imediately after maing your buildd work you want a nice
web-interface onto that status. You say 'some of'. I am only aware of
one: 'pgstatus' from http://git.debian-ports.org/?p=pgstatus.git;a=summary
Are there
+++ Tim Retout [2012-02-15 21:19 +]:
On 15 February 2012 16:30, Wookey woo...@wookware.org wrote:
a related approach
here is the sbuild-db branch code in sbuild which is well on the way
to providing a much saner/more portable wanna-build implementation. My
(admittedly not very
Wookey woo...@wookware.org writes:
[...]
I've looked briefly at changing it to talk to rebuidd and/or
reprepro's databases instead but this seems non-trivial (at least for
me). I currently plan to make rebuildd record the sbuild status return
somehow, and have some simple awk/shell-age to
+++ Tim Retout [2012-02-13 11:59 +]:
Hi,
At my day job, we are attempting to set up wanna-build, buildd and
sbuild to support our (currently) in-house Debian derivative.
However, we had some trouble with wanna-build - we could not find
up-to-date deployment documentation, and had to
On 15 February 2012 16:30, Wookey woo...@wookware.org wrote:
a related approach
here is the sbuild-db branch code in sbuild which is well on the way
to providing a much saner/more portable wanna-build implementation. My
(admittedly not very well-informed) feeling is that work on this/docs
for
On Mon, Feb 13, 2012 at 07:36:32PM +0100, Andreas Barth wrote:
Anything that improves the status is appreciated. Improves of course
doesn't mean replaces broken stuff with even worse broken.
Documentation is good. Less hardcoded filenames as well, as long as a
working transition path is
* Tim Retout (dioc...@debian.org) [120213 12:25]:
However, we had some trouble with wanna-build - we could not find
up-to-date deployment documentation, and had to figure out various
hardcoded paths. So:
* Is there a wanna-build deployment guide that we can use?
* Would you be interested
