Hi John,
> Commit: 0e588f35fc4ab1a94437653f1ad0ad5dc3b961dd
>
> https://github.com/NixOS/nixpkgs/commit/0e588f35fc4ab1a94437653f1ad0ad5dc3b961dd
> Author: John Wiegley
> Date: 2014-07-24 (Thu, 24 Jul 2014)
>
> Changed paths:
> M pkgs/development/libraries/haskell/thym
On Thu, Jul 24, 2014 at 11:03 PM, Eelco Dolstra wrote:
> Hi,
>
> On 24/07/14 21:32, Mathnerd314 wrote:
>
> Here it's really more appropriate to use nix-env (i.e. the imperative
> package
> management style), which makes it easy to mix packages from different
> Nixpkgs
> revisions.
>
> The declara
Hi,
On 24/07/14 21:32, Mathnerd314 wrote:
> So let me describe a little of my recent activities. I wanted the firefox from
> https://github.com/NixOS/nixpkgs/commit/872860e6de8e460fb11a79c46b8092bdcff35da8,
> the
> quassel from ~/nixpkgs, and the rest of the system from the latest hydra
> channe
Hi,
On 23/07/14 11:29, Mathijs Kwik wrote:
> - staging hasn't been merged for > 2 weeks
I don't think there were very urgent things that needed to be merged. Mostly
some Mac OS X improvements. There are some build issues with Atlas (which is an
inherently broken package anyway) and Clang on Darw
On Thu, Jul 24, 2014 at 12:52 PM, Vladimír Čunát wrote:
>
> On 07/23/2014 11:29 AM, Mathijs Kwik wrote:
>>>
>> If stuff causes regressions, revert it and move it to a feature-branch
>> to debug.
>>
>
> Perhaps. I'm not very clear about that. Typically I first try to fix the
> regressions within
Thank you. That helped.
Wat is the case with vim*Wrapper? It seting console interface by default
in some of .vimrc-s?
On 2014-07-24 17:38, Paul Colomiets wrote:
> Hi Alexander,
>
> On Thu, Jul 24, 2014 at 3:41 PM, Alexander Zubkov wrote:
>> Hello.
>> I have some strange problem. When I run comma
Hello.
I have some strange problem. When I run command gvim - then console
version of editor starts. At the same time gvim or vim with option "-g"
have no problems opening GUI version of editor. I do not understand why
this happens. Because I thaught that for gvim incocation GUI mode should
be
On 07/23/2014 11:29 AM, Mathijs Kwik wrote:
If stuff causes regressions, revert it and move it to a feature-branch
to debug.
Perhaps. I'm not very clear about that. Typically I first try to fix the
regressions within days, if possible.
Note that this revert+move workflow tends to hit a pro
Vladimír Čunát writes:
> Hi,
> it's not at all so bad as it used to be. Last year it happened we had
> ~10 months running stdenv-updates that was in the middle getting more
> and more breakages with added commits. That wasn't good and all agreed
> on that.
I'm glad things currently go a lot smoo
On 24/07/2014 11:10, José Romildo Malaquias wrote:
> Hello.
>
> When starting the enlightenment version 18 desktop manager on my
> unstable nixos system, I am getting the following error regarding the
> cpufreq module:
>
> Enlightenment Cpufreq Module:
> There was an error trying to set the cpu
Hello.
When starting the enlightenment version 18 desktop manager on my
unstable nixos system, I am getting the following error regarding the
cpufreq module:
Enlightenment Cpufreq Module:
There was an error trying to set the cpu power state setting via the
module's setfreq utility.
Cpufr
11 matches
Mail list logo
