Wookey <wookey@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 make HTML summaries.
> This is 90% expedience rather than any sort of useful general solution.
>
> rebuildd provides some basic web output, which mostly just shows that
> it is working, rather than being very useful from my POV. That could
> be expanded, but it's probably better to try and keep the buildd
> status web reporting separate from the buildd controller, not least
> because they are likely to be different machines. Which leads back to
> making pgstatus more versatile and able to talk to sbuild-db and
> rebuildd backends as well as wanna-build. But this is a little tricky
> because they provide different info.
I'm using rebuildd with a Pg database, I store build logs in the
database[1] and my reprepro is hosting a rebuildd-http with read access.
With this setup, I have a central view of all buildds[2], logs are not
realtime for now.
As I prefer to keep rebuildd as simple as possible, I'm not sure to
expand it more than this.
As expressed on IRC, I'm interested in a stronger build and repository
setup, mostly for dependency management[3].
Regards.
Footnotes:
[1] http://anonscm.debian.org/gitweb/?p=rebuildd/rebuildd.git;a=commit;h=28cff20ce35ebac255c7a7d4a3359f016c99a77d
[2] Take care to configure 'dists' and 'more_archs' in /etc/rebuildd/rebuilddrc
[3] Does anyone plug britney with reprepro somehow to pass packages
between an unstable and a testing distribution?
--
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
Attachment:
pgpQd6X1BYqS9.pgp
Description: PGP signature