Re: [Nix-dev] NixOS wiki
On 04/10/2013 06:29 PM, Lluís Batlle i Rossell wrote: On Wed, Apr 10, 2013 at 05:55:11PM +0200, Vladimír Čunát wrote: I second all that, both online editing and possibility of distributed offline work seems important to me. Well, I don't see "distributed offline" as a strong requirement. Many of us have quite a regular internet link up. But there should be a way to evolve a branch until it can be discussed and approved for merge. Ah, well, to clarify: by "distributed" I meant the support of easy branching + something like pull-requests, which is usually together with the "offline" DVCS style. I agree that offline support isn't that necessary and I usually have an acceptable connection, except for ~5h/week in trains. I still prefer being without unnecessary dependencies (e.g. on being online). Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS wiki
On 04/10/2013 06:29 PM, Lluís Batlle i Rossell wrote: On Wed, Apr 10, 2013 at 05:55:11PM +0200, Vladimír Čunát wrote: I second all that, both online editing and possibility of distributed offline work seems important to me. Well, I don't see "distributed offline" as a strong requirement. Many of us have quite a regular internet link up. But there should be a way to evolve a branch until it can be discussed and approved for merge. Ah, well, to clarify: by "distributed" I meant the support of easy branching + something like pull-requests, which is usually together with the "offline" DVCS style. I agree that offline support isn't that necessary and I usually have an acceptable connection, except for ~5h/week in trains. I still prefer being without unnecessary dependencies (e.g. on being online). Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS wiki
On Wed, Apr 10, 2013 at 05:55:11PM +0200, Vladimír Čunát wrote: > On 04/10/2013 05:44 PM, Lluís Batlle i Rossell wrote: > >On Mon, Apr 08, 2013 at 11:55:40AM +0200, Marc Weber wrote: > >>>- some offline editing support (git)? > >>we talked about it - and we agree that there are ways - but also pay > >>attention to what Eelco said: He fears that the quality of the contents > >>of the wiki is not that great. So eventually start with telling us what > >>you would add, and why it is not possible or too much work to do it with > >>the current wiki. > > > >For me, a big problem of the current mediawiki is that it doesn't allow > >people to > >*propose* changes (as git branches + pull-requests allow). > > > >We agree that the wiki needs a major rework; but in mediawiki style, you > >either > >change the wiki for everyone, or you don't change it at all. > > I second all that, both online editing and possibility of > distributed offline work seems important to me. Well, I don't see "distributed offline" as a strong requirement. Many of us have quite a regular internet link up. But there should be a way to evolve a branch until it can be discussed and approved for merge. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS wiki
On 04/10/2013 05:44 PM, Lluís Batlle i Rossell wrote: On Mon, Apr 08, 2013 at 11:55:40AM +0200, Marc Weber wrote: - some offline editing support (git)? we talked about it - and we agree that there are ways - but also pay attention to what Eelco said: He fears that the quality of the contents of the wiki is not that great. So eventually start with telling us what you would add, and why it is not possible or too much work to do it with the current wiki. For me, a big problem of the current mediawiki is that it doesn't allow people to *propose* changes (as git branches + pull-requests allow). We agree that the wiki needs a major rework; but in mediawiki style, you either change the wiki for everyone, or you don't change it at all. I second all that, both online editing and possibility of distributed offline work seems important to me. Also having the manuals in there might be good thing, but Wiki is the main thing now. Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS wiki
On Mon, Apr 08, 2013 at 11:55:40AM +0200, Marc Weber wrote: > > - some offline editing support (git)? > we talked about it - and we agree that there are ways - but also pay > attention to what Eelco said: He fears that the quality of the contents > of the wiki is not that great. So eventually start with telling us what > you would add, and why it is not possible or too much work to do it with > the current wiki. For me, a big problem of the current mediawiki is that it doesn't allow people to *propose* changes (as git branches + pull-requests allow). We agree that the wiki needs a major rework; but in mediawiki style, you either change the wiki for everyone, or you don't change it at all. This ends up discouraging me from any attempt to improve the wiki: 1) I don't want to break it, while I do major structure changes 2) I feel that people can be offended, if my changes do not please them. And it'll be a hell to roll all back to start over. So, I think that the current wiki won't change much unless: 1) someone has a stone face to organize it caring little about others opinions 2) we agree giving full-control to somone in particular, to do those changes fearless 3) we switch to a system where people can branch the wiki, do the changes in the branch, and propose a merge For me, the 3rd looks like the least violent. I don't mean that the 3rd way should be the *only way* to change the wiki; the current click-and-edit is perfect, but not for major structure reworks. Regards, Lluís. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How to make Hydra generate an "overview page"
Hi Eelco, > It's on my to-do list to make Hydra /job URLs show all jobs with a > given prefix (so /job/nixpkgs/trunk/hsdns would show all hsdns.* > jobs). aha, I see. Thank you for the explanation. Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Hydra: summary of problems I've encountered
Hi. On 04/10/2013 03:58 PM, Eelco Dolstra wrote: The "gnucash" job no longer exist, instead there are now jobs named "gnucash.i686-linux" and so on. A side note: you remind me some problems I've encountered with hydra.nixos.org. - The "job status" tab now makes less sense. There's a table, but in every row we can only have one thing. - I also wonder if the "job status" tab and "job status" from jobset menu are different pages on purpose. - Why is it that "logdiff" links don't work? Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How to make Hydra generate an "overview page"
Hi, On 10/04/13 15:18, Peter Simons wrote: > Hydra provides "overview pages" for packages that build on more than one > platform -- i.e. http://hydra.nixos.org/job/nixpkgs/trunk/gnucash -- > that show all builds of that particular package at one glance. > > Now, Haskell packages vary in two dimensions: the platform and the > version of GHC that's being used. I tried to re-organize the > release-haskell.nix file [1] so that it shows all of those builds of a > given package on one page by appending the GHC version to the system > identifier, but for some reason that didn't work. My Hydra instance [2] > has the following jobs: > > hsdns.x86_64-linux-ghc6104 > hsdns.x86_64-linux-ghc6123 > hsdns.x86_64-linux-ghc704 > hsdns.x86_64-linux-ghc742 > hsdns.x86_64-linux-ghc762 > > Yet, there is no "overview page" for hsdns! Yes, because "hsdns" is not a job. However, it's on my to-do list to make Hydra /job URLs show all jobs with a given prefix (so /job/nixpkgs/trunk/hsdns would show all hsdns.* jobs). > GNU Cash has a page > > http://hydra.nixos.org/job/nixpkgs/trunk/gnucash Yes, but that page actually shows an obsolete job (note that the last build was on March 25). The "gnucash" job no longer exist, instead there are now jobs named "gnucash.i686-linux" and so on. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] How to make Hydra generate an "overview page"
Hi guys, Hydra provides "overview pages" for packages that build on more than one platform -- i.e. http://hydra.nixos.org/job/nixpkgs/trunk/gnucash -- that show all builds of that particular package at one glance. Now, Haskell packages vary in two dimensions: the platform and the version of GHC that's being used. I tried to re-organize the release-haskell.nix file [1] so that it shows all of those builds of a given package on one page by appending the GHC version to the system identifier, but for some reason that didn't work. My Hydra instance [2] has the following jobs: hsdns.x86_64-linux-ghc6104 hsdns.x86_64-linux-ghc6123 hsdns.x86_64-linux-ghc704 hsdns.x86_64-linux-ghc742 hsdns.x86_64-linux-ghc762 Yet, there is no "overview page" for hsdns! GNU Cash has a page http://hydra.nixos.org/job/nixpkgs/trunk/gnucash but the corresponding page for hsdns http://hydra.cryp.to:8080/job/nixpkgs/refactor-haskell-hydra-view/hsdns does not exist! Is there anything I can do to make Hydra recognize that all those hsdns build jobs refer to the same package? Take care, Peter [1] https://github.com/peti/nixpkgs/blob/c084bf567ef59f1c1b299f674118427187cebd3e/pkgs/top-level/release-haskell.nix [2] http://hydra.cryp.to:8080/jobset/nixpkgs/refactor-haskell-hydra-view ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix-channel can't process channel data from Hydra
On 04/10/2013 12:04 PM, Peter Simons wrote: ..., then the tarball referred to by /nix/store/n4hi4l4r5z7z5m20v9v5spwfb9xg728h-hydra-crypto.drv is broken, indeed, it's *not* a valid bz2-compressed tarball. Apparently, nix-channel downloads this file somehow differntly than my manual invocation of curl does. This looks like a problem in curl. In what way does the bad file differ? Is size OK at least? Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix-channel can't process channel data from Hydra
Hi Eelco, >> I use the channel from my own Hydra instance on several machines just fine, >> but on one of them I get this error during "nix-channel --update" for no >> apparent reason: > > Is this a reproducible problem on that machine? yes, it is. One difference between that machine and those that work fine is that it requires a proxy server to connect to the Internet. So, I guess, the problem could be due to a caching proxy server responding with a broken file. What is strange, though, is that a manually downloaded version of http://hydra.cryp.to:8080/jobset/nixpkgs/haskell-updates/channel/latest/nixexprs.tar.bz2 looks just fine -- it's an okay bz2-compressed tarball. Now, when nix-channel downloads the same file downloading Nix expressions from `http://hydra.cryp.to:8080/jobset/nixpkgs/haskell-updates/channel/latest/nixexprs.tar.bz2'... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 326720 326720 0 22659 0 --:--:-- 0:00:01 --:--:-- 22673 unpacking channels... bzip2: (stdin) is not a bzip2 file. /nix/store/cv12p8zpy0fp6spirw9ph78byz55r6n0-gnutar-1.26/bin/tar: This does not look like a tar archive /nix/store/cv12p8zpy0fp6spirw9ph78byz55r6n0-gnutar-1.26/bin/tar: Exiting with failure status due to previous errors builder for `/nix/store/n4hi4l4r5z7z5m20v9v5spwfb9xg728h-hydra-crypto.drv' failed with exit code 2 error: build of `/nix/store/n4hi4l4r5z7z5m20v9v5spwfb9xg728h-hydra-crypto.drv' failed cannot unpack the channels at /run/current-system/sw/bin/nix-channel line 145. ..., then the tarball referred to by /nix/store/n4hi4l4r5z7z5m20v9v5spwfb9xg728h-hydra-crypto.drv is broken, indeed, it's *not* a valid bz2-compressed tarball. Apparently, nix-channel downloads this file somehow differntly than my manual invocation of curl does. Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
