|--==> Julien Danjou writes: JD> At 1193223671 time_t, Free Ekanayaka wrote: >>Thanks! I've seen that you've added a build_arch_any in the SVN code, >>how does it work exactly?
JD> IIRC, but I've paused the dev for too long, it's for allowing the node JD> to build the jobs with arch 'any' in the db. JD> Otherwise it will only build jobs with its own arch. Thanks, so if a job as arch 'any' in the db, what is the exact behaviour? 1) The job will be scheduled, regardless of the own arch of rebuildd, and rebuildd will try to build it ONLY for its own arch. or 2) The job will scheduled, regardless of the own arch of rebuildd, and rebuildd will try to build it ALL the archs it know (the ones in the [build]:archs config entry I would say) I think you mean 1), but just wanted to be sure. >>From what I understand, the code in version 2.2 doesn't run jobs which >>refer to an architecture other than the host architecture. Is this >>changed in SVN? JD> IIRC again, yes :) Ok. >>I've few other feature requests, like being able to retrieve the >>status of a job via telnet, like: >> >>[EMAIL PROTECTED]> job status >>E: usage: job status <id> >>[EMAIL PROTECTED]> job status 2 >>BUILDING >>[EMAIL PROTECTED]> JD> Please open a bug for that, I'll add that, it should be easy. Thanks. >>I'd like to have a look at the code and try to provide patches for >>them. In this case should work on the current trunk? (just to avoid >>sending you patches with conflicts). JD> Yes, patches should be against the trunk. :) Perfect, ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
