Re: [Nix-dev] staging -- master merge imminent
On 03/02/2015 10:46 AM, Eelco Dolstra wrote: A few days passed. I merged staging from the libsigsegv change. I didn't know next commits, so I thought better not to merge them. That kind of defeats the purpose of the staging branch, which is to combine mass rebuild changes. See here: Why should it defeat the staging purpose? He merged version 953466f, which was completely built by Hydra on job 1173079 http://hydra.nixos.org/jobset/nixpkgs/staging . Therefore, if there was a significant amount of rebuilding after that merge, it was only because someone else has pushed mass-rebuild changes to master in-between, and this re-triggered them. Vladimir 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] staging -- master merge imminent
Hi, On 01/03/15 22:15, Lluís Batlle i Rossell wrote: If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. We'd better wait a few days for Hydra to catch up a bit: http://hydra.nixos.org/eval/1173079 A few days passed. I merged staging from the libsigsegv change. I didn't know next commits, so I thought better not to merge them. That kind of defeats the purpose of the staging branch, which is to combine mass rebuild changes. See here: http://comments.gmane.org/gmane.linux.distributions.nixos/13447 -- 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
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 20, 2015 at 11:45:01AM +0100, Vladimír Čunát wrote: On 02/20/2015 11:36 AM, Lluís Batlle i Rossell wrote: If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. We'd better wait a few days for Hydra to catch up a bit: http://hydra.nixos.org/eval/1173079 A few days passed. I merged staging from the libsigsegv change. I didn't know next commits, so I thought better not to merge them. If anyone wants to merge more commits, go on. Regards, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 20, 2015 at 11:33:40AM +0100, Vladimír Čunát wrote: On 02/20/2015 09:29 AM, Lluís Batlle i Rossell wrote: a trivial work-around for the libsigsegv issue is now in staging: This is not yet in 'master', right? What are we waiting to have it in 'master'? Hydra? Yes, ATM it's the only commit in master..staging. As I'm using staging to be able to build *anything*, I feel invited to commit to staging for non-stdenv-changing commits. :) If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. I'm keeping my changes local, waiting for the merge of staging into master. Regards, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On 02/20/2015 11:36 AM, Lluís Batlle i Rossell wrote: If that commit could be merged into master, it would be nice. I'd be able to commit to master instead. We'd better wait a few days for Hydra to catch up a bit: http://hydra.nixos.org/eval/1173079 Vladimir 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] staging -- master merge imminent
On 02/20/2015 09:29 AM, Lluís Batlle i Rossell wrote: a trivial work-around for the libsigsegv issue is now in staging: This is not yet in 'master', right? What are we waiting to have it in 'master'? Hydra? Yes, ATM it's the only commit in master..staging. Vladimir 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] staging -- master merge imminent
On Tue, Feb 17, 2015 at 11:56:00PM +0100, Lluís Batlle i Rossell wrote: On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote: Hi guys, a trivial work-around for the libsigsegv issue is now in staging: https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d I'll merge it to master within a couple of days, once Hydra has built binaries for the new stdenv version. If anyone is aware of a superior way to remedy this problem, please don't hesitate to improve on the change. Perfect! Thank you! I think this change is what most people affected did, and hence they will not notice a stdenv change. This is not yet in 'master', right? What are we waiting to have it in 'master'? Hydra? Thank you, Lluís. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On Tue, Feb 17, 2015 at 11:45:28PM +0100, Peter Simons wrote: Hi guys, a trivial work-around for the libsigsegv issue is now in staging: https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d I'll merge it to master within a couple of days, once Hydra has built binaries for the new stdenv version. If anyone is aware of a superior way to remedy this problem, please don't hesitate to improve on the change. Perfect! Thank you! I think this change is what most people affected did, and hence they will not notice a stdenv change. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
Hi guys, a trivial work-around for the libsigsegv issue is now in staging: https://github.com/NixOS/nixpkgs/commit/953466fcbaea0f7c4d48b5a6e3905d4e07b9a79d I'll merge it to master within a couple of days, once Hydra has built binaries for the new stdenv version. If anyone is aware of a superior way to remedy this problem, please don't hesitate to improve on the change. I hope this helps, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
About sigsegv, what is the recommended procedure? 2015-02-14 12:45 GMT-02:00 Anderson Torres torres.anderson...@gmail.com: 2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name: On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? Yep, it is the best thing to do now, imho. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ 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
Re: [Nix-dev] staging -- master merge imminent
The repository masters are silent about it. Niksut? Dr Pepper? Peti? I guess they don't experience the problem, so they are ready to wait to new kernels arrive. That's all guessing; I haven't seen any formal position. That's why I asked at the time staging was merged. An easier way would have been to commit directly the disable of check to master, but I'm not heavily affected by the issue. As for me, please disable the check until a libsigsegv update happens. Regards, Lluís. On Tue, Feb 17, 2015 at 02:58:58PM -0200, Anderson Torres wrote: About sigsegv, what is the recommended procedure? 2015-02-14 12:45 GMT-02:00 Anderson Torres torres.anderson...@gmail.com: 2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name: On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? Yep, it is the best thing to do now, imho. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ 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 -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
2015-02-13 20:31 GMT-02:00 Lluís Batlle i Rossell vi...@viric.name: On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? Yep, it is the best thing to do now, imho. -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ 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
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 13, 2015 at 11:07:27PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote: Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? What's the connection between libsigsegv and kernel.org? I noticed libsigsegv test failures the other day (I was playing with armv7 bootstrap), and I bisected the error to this commit: 88fd7f452703f3280a3747e97b938c8e50ae962c (Re-Revert merge #5505: util-linux: use /run/current-system/sw/bin/*) I was planning to make a gihub issue or post on nix-dev ML, but didn't get to it before now :-) I think that linus changed the signal of stack overflow from SIGSEGV to SIGBUS. At some point, people realized it was a bad idea, and they took the change back in recent kernels. But if you bisected it... no idea. :) That change you found is quite weird. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). - Bjørn ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. On 13 February 2015 at 14:12, Lluís Batlle i Rossell vi...@viric.name wrote: On Fri, Feb 13, 2015 at 11:07:27PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote: Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? What's the connection between libsigsegv and kernel.org? I noticed libsigsegv test failures the other day (I was playing with armv7 bootstrap), and I bisected the error to this commit: 88fd7f452703f3280a3747e97b938c8e50ae962c (Re-Revert merge #5505: util-linux: use /run/current-system/sw/bin/*) I was planning to make a gihub issue or post on nix-dev ML, but didn't get to it before now :-) I think that linus changed the signal of stack overflow from SIGSEGV to SIGBUS. At some point, people realized it was a bad idea, and they took the change back in recent kernels. But if you bisected it... no idea. :) That change you found is quite weird. ___ 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
Re: [Nix-dev] staging -- master merge imminent
On Fri, Feb 13, 2015 at 11:29:03PM +0100, Bjørn Forsman wrote: On 13 February 2015 at 23:26, James Cook jc...@cs.berkeley.edu wrote: https://github.com/NixOS/nixpkgs/issues/6028#issuecomment-72952987 The error is caused by an impurity, so bisecting might just reveal which version you had in the store before you switched to a newer kernel. Ah, right. Thanks. (I wasn't aware of issue #6028). Some people disabled doCheck in libsigsegv, but it's a stdenv change. Should we disable doCheck there until the storm passes? -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? Regards, Lluís. On Fri, Feb 13, 2015 at 10:16:24PM +0100, Peter Simons wrote: 'staging' has been merged to 'master' in 54ce1a1. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Escriu-me sempre xifrat / Write always ciphered PGP key D4831A8A - https://emailselfdefense.fsf.org/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
'staging' has been merged to 'master' in 54ce1a1. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
On 13 February 2015 at 22:20, Lluís Batlle i Rossell vi...@viric.name wrote: Thank you! Is the plan for failing libsigsegv to wait for kernel.org fixes? What's the connection between libsigsegv and kernel.org? I noticed libsigsegv test failures the other day (I was playing with armv7 bootstrap), and I bisected the error to this commit: 88fd7f452703f3280a3747e97b938c8e50ae962c (Re-Revert merge #5505: util-linux: use /run/current-system/sw/bin/*) I was planning to make a gihub issue or post on nix-dev ML, but didn't get to it before now :-) - Bjørn ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
Hi Georges, There's a curl update PR (https://github.com/NixOS/nixpkgs/pull/6171). Can it board that train, or should it wait for the next? IMHO, it looks innocent enough to be included: 7fc94dd3. Best regards, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] staging -- master merge imminent
There's a curl update PR (https://github.com/NixOS/nixpkgs/pull/6171). Can it board that train, or should it wait for the next? Georges Dubus 2015-02-09 17:08 GMT+01:00 Peter Simons sim...@cryp.to: Hi guys, I would like to merge the staging branch back into master as soon as http://hydra.nixos.org/jobset/nixpkgs/staging has completed building revision 7b99c149a4, i.e. in 2-3 days. Does anyone see a compelling reason to postpone that merge? Best regards, Peter ___ 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
