* Blars Blarson ([EMAIL PROTECTED]) wrote: > I've been watching the sparc buildd queues for the past 9 months or > so, filing most of the ftbfs bugs for sparc, and prodding the buildd > maintainer when a package needs a simple build requeue or the sbuild > chroot is broken.
Great! What mechanisms have you been using to do that, and what could
we do to make it easier for other people to do that? Is there a way to
get the sparc buildd queues and associated information to be more
pro-actively sent to people? I know that, at least for myself, I'm much
more inclined to do things or at least try to help with things when an
email about a problem shows up in my email client than if I have to
periodically check a website, etc.
> >4) buildd software issues(pbuild,sbuild,wanna-build,etc)
>
> occasionally. sbuild is vulnerable to broken packages breaking it's
> chroot, sometimes in ways that only effect a few packages and may not
> be quickly noticed.
>
> wanna-build has scalability issues, but it can be bypassed for unstable
> if the buildd maintainer doesn't interfere. (Just build and upload
> all the new packages.)
>
> It looks like this software could use some redesign to put less work
> on the buildd maintainers and scale better to more buildds.
Do you have some specific insights into this? This certainly sounds
like a good area for us to work on..
Thanks,
Stephen
signature.asc
Description: Digital signature
