Hi Julien, |--==> Julien Danjou writes:
JD> Hi, JD> At 1193156066 time_t, Free Ekanayaka wrote: >>I would like to build packages both for i386 and amd64 on an amd64 >>system. This would be possible if the configuration file could support >>something like: >> >># dist name, arch name, package name, package version >>build_cmd = pbuilder build --basetgz /tmp/%s-%s.tgz %s_%s.dsc JD> Sure. >>As jobs have already an optional [arch] field, it should not be >>difficult to achive that, right? JD> Easy :) Thanks! I've seen that you've added a build_arch_any in the SVN code, how does it work exactly? >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? 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]> 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). >>(as you see below I got rebuildd running on debian etch, but it was a >>bit painful.. did you test it yourself on etch somehow?) JD> No, because it requires python 2.5. That's a pity :( I'd like to run it on a server with etch, possibly avoiding having a chroot. Anyway backporting some packages (sqlobject, libapt, pygdchart2) seems to make it working (even thought some other packages break). Ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
