Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
On 20 Jun 2016 17:53, "Domen Kožar" wrote: > I do agree it's additional work, but it's better than current state where we all maintain our Hydra from carefully picked commits and that's REALLY some additional work. Completely agree, it's kind of annoying going through the commits determining which one is good. Once selected you're hesitant to move to a more recent commit as it could blow up. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
On Thu, Jun 16, 2016 at 2:50 PM, Tomasz Czyż wrote: > > > 2016-06-16 11:31 GMT+01:00 Domen Kožar : > >> On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż >> wrote: >> >>> Domen, >>> >>> do you know what's the strategy for hydra in nixos? Looks like module >>> file is not imported from hydra but is copied/prepared separately in nixos. >>> That means there are two module versions but one code base. >>> >>> Will hydra module be moved to nixos? If not, maybe would be better to >>> just import it from upstream? >>> >>> Is strategy (to keep modules inside nixos for external packages, even >>> those with nix modules) the way to go for all other projects? If yes, could >>> you explain why or point to some explanations? >>> >> >> Currently module in nixpkgs and the module in hydra will be maintained >> separately. Eelco will deploy Hydra as it's always been and update >> package/module in hydra.git, I'll port changes to nixpkgs. >> >> We currently don't have a better way to deal with this. I'll see how it >> goes, but the idea is Hydra repository should be self contained. >> > > IMHO, this makes additional work without giving too much. > > 1. you have to port module into nixos each time you fetch new hydra change > 2. if hydra will brake compatibility with nixos you have to fix ported > version (which makes situation where two modules needs to be maintained) > > but if you would just import module from nix you have: > > 1. when updating hydra you just check if tests pass > 2. if something is broken you can fix upstream or override hydra module to > create temporary fix > > So I assume second approach is lot less work with the same weak points. > Maybe I'm missing something but for me it looks like just adding more > manual work to do. > What do you think? > > Also, there is a case (not mine yet, but I assume will be at some point) > when you want to keep specific hydra version with it's module > implementation, is it possible to do that in a current version? (I mean > import hydra's module which override local module)? > I'd rather talk about specific use cases than hypothetical questions. I'll port new Hydra changes to nixpkgs now and then, but maybe some day hydra.nixos.org starts using hydraUnstable package from nixpkgs and we can get rid of all nix stuff in hydra.git repository. I do agree it's additional work, but it's better than current state where we all maintain our Hydra from carefully picked commits and that's REALLY some additional work. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
2016-06-16 11:31 GMT+01:00 Domen Kožar : > On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż > wrote: > >> Domen, >> >> do you know what's the strategy for hydra in nixos? Looks like module >> file is not imported from hydra but is copied/prepared separately in nixos. >> That means there are two module versions but one code base. >> >> Will hydra module be moved to nixos? If not, maybe would be better to >> just import it from upstream? >> >> Is strategy (to keep modules inside nixos for external packages, even >> those with nix modules) the way to go for all other projects? If yes, could >> you explain why or point to some explanations? >> > > Currently module in nixpkgs and the module in hydra will be maintained > separately. Eelco will deploy Hydra as it's always been and update > package/module in hydra.git, I'll port changes to nixpkgs. > > We currently don't have a better way to deal with this. I'll see how it > goes, but the idea is Hydra repository should be self contained. > IMHO, this makes additional work without giving too much. 1. you have to port module into nixos each time you fetch new hydra change 2. if hydra will brake compatibility with nixos you have to fix ported version (which makes situation where two modules needs to be maintained) but if you would just import module from nix you have: 1. when updating hydra you just check if tests pass 2. if something is broken you can fix upstream or override hydra module to create temporary fix So I assume second approach is lot less work with the same weak points. Maybe I'm missing something but for me it looks like just adding more manual work to do. What do you think? Also, there is a case (not mine yet, but I assume will be at some point) when you want to keep specific hydra version with it's module implementation, is it possible to do that in a current version? (I mean import hydra's module which override local module)? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż wrote: > Domen, > > do you know what's the strategy for hydra in nixos? Looks like module file > is not imported from hydra but is copied/prepared separately in nixos. That > means there are two module versions but one code base. > > Will hydra module be moved to nixos? If not, maybe would be better to just > import it from upstream? > > Is strategy (to keep modules inside nixos for external packages, even > those with nix modules) the way to go for all other projects? If yes, could > you explain why or point to some explanations? > Currently module in nixpkgs and the module in hydra will be maintained separately. Eelco will deploy Hydra as it's always been and update package/module in hydra.git, I'll port changes to nixpkgs. We currently don't have a better way to deal with this. I'll see how it goes, but the idea is Hydra repository should be self contained. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
Domen, do you know what's the strategy for hydra in nixos? Looks like module file is not imported from hydra but is copied/prepared separately in nixos. That means there are two module versions but one code base. Will hydra module be moved to nixos? If not, maybe would be better to just import it from upstream? Is strategy (to keep modules inside nixos for external packages, even those with nix modules) the way to go for all other projects? If yes, could you explain why or point to some explanations? 2016-06-16 9:54 GMT+01:00 Tomas Hlavaty : > Hi Domen, > > Domen Kožar writes: > > Hydra NixOS module and package are now available on nixpkgs master. > > thank you! > > > There's one bug I need to fix, then I'll backport these changes to > > 16.03. > > great! > > > Meanwhile, I used following commit on 16.03 before I moved to the > > fork using some improvements: https://github.com/snabblab/ > > snabblab-nixos/commit/20a3fe6e9cf9e0da2a855bd1df9ce7ebad434951 > > good, if I don't succeed with my upgrade, I'll try that. > > > Official releases will for now be pinned git revisions on nixpkgs, > > hopefully that will suffice for most of us. > > Will the official hydra be on 16.03 or unstable? > > > On Tue, Jun 14, 2016 at 4:21 PM, Tomas Hlavaty < > > 1258008 2016-04-15 hydraSrc → 177bf25 > > at https://hydra.nixos.org/jobset/hydra/master/evals?page=2 > > I am upgrading to hydra 177bf25 on nixos 16.03 and it seems to work > except that hydra lost the ability to do distributed builds. Has > something changed in this regard in hydra/nix/nixos? > > In "journal -xe" log, I can see that hydra-queue-runner loads a build > into nix-daemon but then the build is stuck as queued forever. > > I can't see any error messages from nix-daemon. Is there a way to debug > nix-daemon in order to see, what is it doing? > > Tomas > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > -- Tomasz Czyż ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
Hi Domen, Domen Kožar writes: > Hydra NixOS module and package are now available on nixpkgs master. thank you! > There's one bug I need to fix, then I'll backport these changes to > 16.03. great! > Meanwhile, I used following commit on 16.03 before I moved to the > fork using some improvements: https://github.com/snabblab/ > snabblab-nixos/commit/20a3fe6e9cf9e0da2a855bd1df9ce7ebad434951 good, if I don't succeed with my upgrade, I'll try that. > Official releases will for now be pinned git revisions on nixpkgs, > hopefully that will suffice for most of us. Will the official hydra be on 16.03 or unstable? > On Tue, Jun 14, 2016 at 4:21 PM, Tomas Hlavaty < > 1258008 2016-04-15 hydraSrc → 177bf25 > at https://hydra.nixos.org/jobset/hydra/master/evals?page=2 I am upgrading to hydra 177bf25 on nixos 16.03 and it seems to work except that hydra lost the ability to do distributed builds. Has something changed in this regard in hydra/nix/nixos? In "journal -xe" log, I can see that hydra-queue-runner loads a build into nix-daemon but then the build is stuck as queued forever. I can't see any error messages from nix-daemon. Is there a way to debug nix-daemon in order to see, what is it doing? Tomas ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
On Wed, Jun 15, 2016 at 3:40 AM, Domen Kožar wrote: > Hydra NixOS module and package are now available on nixpkgs master. > There's one bug I need to fix, then I'll backport these changes to 16.03. > > Meanwhile, I used following commit on 16.03 before I moved to the fork > using some improvements: > https://github.com/snabblab/snabblab-nixos/commit/20a3fe6e9cf9e0da2a855bd1df9ce7ebad434951 > > Official releases will for now be pinned git revisions on nixpkgs, > hopefully that will suffice for most of us. > Hooray! Thank you so much to all the people that contributed to this. Colin ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
Hydra NixOS module and package are now available on nixpkgs master. There's one bug I need to fix, then I'll backport these changes to 16.03. Meanwhile, I used following commit on 16.03 before I moved to the fork using some improvements: https://github.com/snabblab/snabblab-nixos/commit/20a3fe6e9cf9e0da2a855bd1df9ce7ebad434951 Official releases will for now be pinned git revisions on nixpkgs, hopefully that will suffice for most of us. On Tue, Jun 14, 2016 at 4:21 PM, Tomas Hlavaty < tomas.hlav...@knowledgetools.de> wrote: > Hi, > > does somebody know, what hydra and nixos versions/commits are deployed > at hydra.nixos.org? > > I am running hydra with nixos 15.09 and hydra > 993647d1e3b43f1f9b7dc2ebce889b475d156bb9 but I would like to upgrade my > local hydra machine to nixos 16.03. > > I can see that the last successful hydra build was > > 1258008 2016-04-15 hydraSrc → 177bf25 > at https://hydra.nixos.org/jobset/hydra/master/evals?page=2 > > but it would be nice to know what is actually used. > > Even better would be, if I could somehow find it out somewhere publicly > accessible without having to ask each time. > > What is the status of the official hydra releases? > > Thank you, > > Tomas > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] hydra and nixos versions/commits at hydra.nixos.org
Hi, does somebody know, what hydra and nixos versions/commits are deployed at hydra.nixos.org? I am running hydra with nixos 15.09 and hydra 993647d1e3b43f1f9b7dc2ebce889b475d156bb9 but I would like to upgrade my local hydra machine to nixos 16.03. I can see that the last successful hydra build was 1258008 2016-04-15 hydraSrc → 177bf25 at https://hydra.nixos.org/jobset/hydra/master/evals?page=2 but it would be nice to know what is actually used. Even better would be, if I could somehow find it out somewhere publicly accessible without having to ask each time. What is the status of the official hydra releases? Thank you, Tomas ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
