Hello,
I'm trying to add spamassassin to my email setup. So I added this to my
configuration.nix:
services.spamassassin = {
enable = true;
debug = true;
};
I then tried with `systemctl start spamd' which failed, because of
missing configs (I should admit now, that I'm very
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
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
I can't set nix.maxJobs in configuration.nix, because it is set in
hardware-configuration.nix:
error: The unique option `nix.maxJobs' is defined multiple times, in
`/etc/nixos/hardware-configuration.nix' and
`/etc/nixos/configuration.nix'.
Of course, I could work around this by editing
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
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
Op Tue, 17 Feb 2015 16:57:29 -0200
Anderson Torres torres.anderson...@gmail.com schreef:
2015-02-17 16:29 GMT-02:00 Berno Strik dutchma...@gmx.com:
I'm a big fan of the windowmanager windowmaker.
I'd like to contribute some dockapps for this.
Where should I put these dockapps:
A -
2015-02-17 16:29 GMT-02:00 Berno Strik dutchma...@gmx.com:
I'm a big fan of the windowmanager windowmaker.
I'd like to contribute some dockapps for this.
Where should I put these dockapps:
A - directory: nixpkgs/pkgs/applications/window-managers/windowmaker
B - directory:
I'm a big fan of the windowmanager windowmaker.
I'd like to contribute some dockapps for this.
Where should I put these dockapps:
A - directory: nixpkgs/pkgs/applications/window-managers/windowmaker
B - directory: nixpkgs/pkgs/applications/misc/dockapps
C - another directory
Please give me a
On 17 Feb 2015, at 10:34, Eelco Dolstra eelco.dols...@logicblox.com wrote:
Hi,
On 16/02/15 19:53, Ertugrul Söylemez wrote:
Software should be fully documented. If you don't know where the line
between regular users and advanced users is, don't draw one in the
first place.
Might I ask, what is the point of stale code not being executed?
And if code is being written to sit stale on a branch, isn't that wasted talent?
Lastly (if there is no renaming attic/name) it just confuses people.
Having code merged into a canonical branch asap makes for faster
feedback cycles
On 16 Feb 2015, at 19:53, Ertugrul Söylemez ert...@gmx.de wrote:
I believe everything should be documented at least in a technical
manual. But there is nothing wrong with putting a note there:
Regular users should not need to use this command.
I wouldn't be in such a hurry to document
Hi,
On 16/02/15 19:53, Ertugrul Söylemez wrote:
Software should be fully documented. If you don't know where the line
between regular users and advanced users is, don't draw one in the
first place.
It's not so much a question of regular vs. advanced use, but whether something
is a stable
Hi,
On 16/02/15 18:43, Matthias Beyer wrote:
what do you think about removing the old branches, as listed below (I
guess all before 12-2014 or something) should be removed,...
No, they should not be removed, unless they were merged. Deleting history kind
of defeats the purpose of having a
Umm, this is kinda the point that I was making, you were the one who
suggested to write that regular users should use this feature, so I
explained that you can't differentiate between regular and advanced
users to you need to treat all users equally and just document the
feature in a clear
Software should be fully documented. If you don't know where the
line between regular users and advanced users is, don't draw one
in the first place.
It's not so much a question of regular vs. advanced use, but whether
something is a stable interface. If we document a command like
16 matches
Mail list logo
