Re: [Nix-dev] glib-2.30 again
Jobset has been added: http://hydra.nixos.org/jobset/nixpkgs/glib-230 Cheers, Rob Yes it is possible, and I might have time later today to add it. The 'policy' is as follows: - hydra.nixos.org and specifically running a nixpkgs branch in hydra is a privilege, not a right - hydra.nixos.org is shared by many projects, so keep footprint (e.g. nr of builds) as low as possible - therefore we prefer a small subset of build to be defined - however if this is not possible, because you are working on a high impact change, you can use the normal set of packages to be built - try not merge trunk changes in daily -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] glib-2.30 again
Rob Vermaas wrote: Jobset has been added: http://hydra.nixos.org/jobset/nixpkgs/glib-230 Thanks! BTW, hydra says that it is disabled. About hydra cycles: we can start with x86_64 (and i686?) only. I can't fix anything else anyway. -- Yury G. Kudryashov, mailto: ur...@mccme.ru ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] glib-2.30 again
Michael Raskin wrote: Second, it makes no sense to build only a few packages on glib upgrade. Every package that depends on glib may fail. A few packages that do not depend on glib will add no overhead to hydra since their builds will be cached from the trunk jobset. Well, it does make sense to check that a few things build, not to spend time on getting very similar errors many times. What do you mean by very similar errors? I can't guess that package B fails to build in the same way as package A. -- Yury G. Kudryashov, mailto: ur...@mccme.ru ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] glib-2.30 again
Michael Raskin wrote: Second, it makes no sense to build only a few packages on glib upgrade. Every package that depends on glib may fail. A few packages that do not depend on glib will add no overhead to hydra since their builds will be cached from the trunk jobset. Well, it does make sense to check that a few things build, not to spend time on getting very similar errors many times. What do you mean by very similar errors? I can't guess that package B fails to build in the same way as package A. You mean that you have already tested, I don't know, five packages with GUI programs locally and they work OK? I guess not saying this in the original email was the mistake. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] glib-2.30 again
Hi, I've asked to add glib-2.30-take2 branch to hydra 3 times. When I asked on IRC, Rob asked me if I've already defined a small subset of packages to build. First, I never been told to do it. Me mentioning that was me telling you. Second, it makes no sense to build only a few packages on glib upgrade. Every package that depends on glib may fail. A few packages that do not depend on glib will add no overhead to hydra since their builds will be cached from the trunk jobset. So, I ask again. Could you please add this branch to hydra? Yes it is possible, and I might have time later today to add it. The 'policy' is as follows: - hydra.nixos.org and specifically running a nixpkgs branch in hydra is a privilege, not a right - hydra.nixos.org is shared by many projects, so keep footprint (e.g. nr of builds) as low as possible - therefore we prefer a small subset of build to be defined - however if this is not possible, because you are working on a high impact change, you can use the normal set of packages to be built - try not merge trunk changes in daily Cheers, Rob -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
