On Tue, Apr 21, 2015 at 06:18:48PM -0400, Mark H Weaver wrote: > We shouldn't ask Hydra to build it until all of the relevant patches are > pushed. Therefore, I have deleted the 'wip-glib' jobset for now, since > it was about to rebuild 1335 builds based on the libidn-1.30 update,
These were shared with master anyway, so the argument does not apply. I still think we should evaluate once without the patches in the new branch (which causes only little work, modulo the problems with the virtual machine...) so that we can see under "newly failing builds" what problems have been caused by the patches. Currently, all packages in wip-glib are listed under "new jobs", so the successful and the (currently close to 500) failed builds are mixed up in an enormous list of over 5000 packages, as well as those that already fail on master are mixed up with those that fail only in the new branch. > I also have an libxfont security update to add to the branch as well. Well, in an ideal world, these two patch sets would be built separately, so that any failure could be attributed to one or the other. So I would not call two rebuilds "wasted work" in such a context. Apart from that, maybe with the lack of build resources, we cannot afford to rebuild after each git commit... Andreas