[13:11] <caribou> Q: when someone request an armhf build for a PPA, does the armhf build remains in place for good or is it a one shot deal ?
[13:12] <dobey> caribou: it's a per-ppa flag, not a per-build flag
[13:13] <caribou> dobey: good thanks. Then another question :
[13:13] <caribou> the wiki states that builds need to be less than 4 hours
[13:13] <caribou> it is a total for the PPA or for each build ?
[13:13] <caribou> (I'm trying to help the kodi team to build their PPA on armhf)
[13:14] <dobey> caribou: a single build cannot take more than 4 hours to complete
[13:14] <caribou> dobey: good. None of their build take more than 30min
[13:14] <caribou> dobey: thanks for your help
[13:14] <dobey> caribou: PPA builders are a shared resource, so the longer your build takes, the longer it takes to get to other PPAs for building
[13:15] <caribou> dobey: yeah, I understand that which is why I'm checking before going forward
[13:15] <caribou> they have quite a few packages in their PPA
[21:12] <nickoe> I was trying to look around, but I could not really find an answer. So I amsk my question here.
[21:12] <nickoe> Will a project that has a milestone or something  mark bug as fix released if they were fix comitted?
[21:12] <nickoe> *automatically
[21:13] <cjwatson> nickoe: No.
[21:13] <nickoe> cjwatson: Ok.  So they have to be done manually in some way?
[21:13] <cjwatson> Practices for when Fix Released is appropriate vary wildly among projects, so we don't attempt it.
[21:13] <cjwatson> Right.  You could script it using launchpadlib if you wanted.
[21:13] <nickoe> cjwatson: But is it not configurable in some way?
[21:13] <cjwatson> No.
[21:13] <dobey> you can write a script to do it automatically for you
[21:13] <cjwatson> https://help.launchpad.net/API/launchpadlib
[21:14] <nickoe> Yeah, I have looked a but on that launchpadlib.
[21:16] <nickoe> *a bit
[21:20] <nickoe> But