Re: [Nix-dev] Stackage Support Will Be Discontinued

It might make sense to create an external repo (nix-hackage?) with the stackage releases and it's own release.nix. That way it can evolve independently from nixpkgs and not clobber the main repo. It can also offer it's own binary cache as a service to haskell developers. You might even be able to

[Nix-commits] [NixOS/nixpkgs] d22013: httpie: 0.9.2 -> 0.9.3 (#16067)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: d220132f222979db1350dde527408e445af3cf43 https://github.com/NixOS/nixpkgs/commit/d220132f222979db1350dde527408e445af3cf43 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-06-08 (Wed, 08 Ju

[Nix-commits] [NixOS/nixpkgs] 909f83: piqi: 0.6.12 -> 0.6.13

.com/NixOS/nixpkgs/commit/4e30ff7368a9c18658c209c4f5df84f1967456df Author: zimbatm <zimb...@zimbatm.com> Date: 2016-06-08 (Wed, 08 Jun 2016) Changed paths: M pkgs/development/ocaml-modules/piqi-ocaml/default.nix M pkgs/development/ocaml-modules/piqi/default.nix Log Message:

Re: [Nix-dev] Nixops fails to log into virtualbox machines on osx.

Maybe it should On Tue, 7 Jun 2016, 17:50 Maarten Hoogendoorn, <maar...@moretea.nl> wrote: > That did the trick. I assumed the ssh invoked in nixops would use it's own > ssh configuration file. > > 2016-06-07 17:22 GMT+02:00 zimbatm <zimb...@zimbatm.com>: > >&g

[Nix-commits] [NixOS/nixpkgs] c38a08: elixir: 1.2.5 -> 1.2.6

gs/commit/5811b47ba31902037bd487407740e7435aaaf109 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-06-07 (Tue, 07 Jun 2016) Changed paths: M pkgs/development/interpreters/elixir/default.nix M pkgs/servers/xmpp/ejabberd/default.nix Log Message: --- Merge pull request #16037 from couchem

Re: [Nix-dev] Nixops fails to log into virtualbox machines on osx.

Can you try to edit you ~/.ssh/config and add "StrictHostKeyChecking no" in the file ? What it does is automatically accept new hosts in the ~/.ssh/known_hosts provided the machine doesn't already exists. On Tue, 7 Jun 2016 at 14:24 Maarten Hoogendoorn wrote: > Hi there, > >

Re: [Nix-dev] Install Nix on OSX, install nixops -> runs python2.7-pytest tests

> behind the NixOS one? I thought if some package was present in the unstable > channel, that hydra would have build it and uploaded it to the binary cache? > > 2016-06-07 14:30 GMT+02:00 zimbatm <zimb...@zimbatm.com>: > >> In general I found that there are less pac

Re: [Nix-dev] Install Nix on OSX, install nixops -> runs python2.7-pytest tests

In general I found that there are less packages available from the cache on OSX. What probably happened is that the packages had to be built. If doCheck = true then tests are run after the build and this is the default for python packages. On Tue, 7 Jun 2016, 13:19 Maarten Hoogendoorn,

Re: [Nix-dev] GNOME packaging file structure

You could also have a package/base/default.nix for common things and override what you want in package/3.20/default.nix. I bet the dependency list would evolve independently. On Fri, 3 Jun 2016, 15:57 Luca Bruno, wrote: > Hello, > after GNOME 3.20 I'm planning to change

[Nix-commits] [NixOS/nixpkgs] a6593a: virtualbox: give full url for downloading the ext ...

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a6593a16f7aa1de03ed0d4f36e8bfb68c0459df5 https://github.com/NixOS/nixpkgs/commit/a6593a16f7aa1de03ed0d4f36e8bfb68c0459df5 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-06-01 (Wed, 01 Ju

[Nix-commits] [NixOS/nixpkgs] 1b682f: heroku: 3.42.20 -> 3.43.2

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 1b682f83f96014aa25fd5698498bec0ecfc3d955 https://github.com/NixOS/nixpkgs/commit/1b682f83f96014aa25fd5698498bec0ecfc3d955 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-23 (Mon, 23 Ma

[Nix-commits] [NixOS/nixpkgs] f8cc92: man-db: clean the expression a bit

y 2016) Changed paths: M pkgs/shells/fish/default.nix Log Message: --- fish: use a different alias man_db -> man-db Commit: 4d0a421f18cbb647af349d3a3bd7eceb534e57cc https://github.com/NixOS/nixpkgs/commit/4d0a421f18cbb647af349d3a3bd7eceb534e57cc Author: zimbatm &

[Nix-commits] [NixOS/nixpkgs] beae30: fcitx-qt5: kde5PackagesFun -> qt5LibsFun

Commit: c978183c5df77db0c5b8a44942c821e4f96c28ef https://github.com/NixOS/nixpkgs/commit/c978183c5df77db0c5b8a44942c821e4f96c28ef Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-23 (Mon, 23 May 2016) Changed paths: A pkgs/tools/inputmethods/fcitx/fcitx-qt5-ecm.patch

[Nix-commits] [NixOS/nixpkgs] 88ffa3: libuv: 1.9.0 -> 1.9.1

9fb4876e60fca26e1ceb4263ce1a0f8f5 https://github.com/NixOS/nixpkgs/commit/857a5229fb4876e60fca26e1ceb4263ce1a0f8f5 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-19 (Thu, 19 May 2016) Changed paths: M pkgs/development/libraries/libuv/default.nix M pkgs/development/w

Re: [Nix-dev] Why is there no way to run `nix-shell` in a chroot and without the user's .bashrc?

Yes, we should not load the `.bashrc` unless the nix-shell is interactive *and* non-pure. If it's not interactive then the user doesn't need to load his favorite environment. If it's pure then then it's causing problems because the assumptions of available software made in the .bashrc are usually

[Nix-commits] [NixOS/nixpkgs] 0cebbc: rssh: init at 2.3.4

commit/c276727dcaa9f92d2815af6362dbdd04c74d6658 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-16 (Mon, 16 May 2016) Changed paths: A pkgs/shells/rssh/default.nix A pkgs/shells/rssh/fix-config-path.patch M pkgs/top-level/all-packages.nix Log Message: --- Merge pull re

[Nix-commits] [NixOS/nixpkgs] 848432: guile-sdl2: init at 0.1.0

ub.com/NixOS/nixpkgs/commit/0d09437e230e7eb3cf4846ebf68f709a5bfed54e Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-15 (Sun, 15 May 2016) Changed paths: M lib/maintainers.nix A pkgs/development/guile-modules/guile-sdl2/default.nix M pkgs/top-level/all-packages.nix

Re: [Nix-dev] upgrading packer

you mean by upgrading packer itself? If I just bump the packer > reference in deps.nix, that cannot update the rest of the dependencies > (they are part of the expression, so they need to be evaluated before > building). Am I misunderstanding your suggestion? > > > On 11 May 2

[Nix-commits] [NixOS/nixpkgs] 902017: cava: update to 0.4.1

Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-11 (Wed, 11 May 2016) Changed paths: M lib/maintainers.nix M pkgs/applications/audio/cava/default.nix Log Message: --- Merge pull request #15382 from mirrexagon/cava-update cava: update to 0.4.1 Compare: https:

Re: [Nix-dev] upgrading packer

Did you try just upgrading packer itself? I believe those dependencies are included during the build now On Wed, 11 May 2016 08:39 Samuel, wrote: > Hi, > > I took a brief look into upgrading packer in nixpkgs, but it seems > that it has a long list of hardcoded

[Nix-commits] [NixOS/nixpkgs] 8335c6: simp_le: 2016-02-06 -> 2016-04-17

m/NixOS/nixpkgs/commit/89675e4a079a81adf498d59fea99d6a16352c05e Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-10 (Tue, 10 May 2016) Changed paths: M pkgs/tools/admin/simp_le/default.nix M pkgs/top-level/python-packages.nix Log Message: --- Merge pull reques

[Nix-commits] [NixOS/nixpkgs] 79c06a: usb_modeswitch: 2.2.1 -> 2.3.0

y 2016) Changed paths: M pkgs/development/tools/misc/usb-modeswitch/default.nix Log Message: --- usb_modeswitch: 2.2.1 -> 2.3.0 Commit: 96162777d826fa8d89fec1e30905da9c58c4d911 https://github.com/NixOS/nixpkgs/commit/96162777d826fa8d89fec1e30905da9c58c4d911 Author

[Nix-commits] [NixOS/nixpkgs] 3beda4: Python: re-enable default testing

ub.com/NixOS/nixpkgs/commit/da8c41814adef990daf8aeacaa78fee0221f3071 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/development/python-modules/generic/default.nix Log Message: --- Merge pull request #15326 from FRid

[Nix-commits] [NixOS/nixpkgs] 303e97: Python: allow installing wheels

ges.nix Log Message: --- pythonPackages.entrypoints: init at 0.2.1 Commit: 428db7857e8fae65c32e87f5d768af141cbb3ad5 https://github.com/NixOS/nixpkgs/commit/428db7857e8fae65c32e87f5d768af141cbb3ad5 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-09 (Mon, 09 May 2016)

[Nix-commits] [NixOS/nixpkgs] 0435ac: texlive.combine: patch paths into texmf.cnf

Log Message: --- texlive.combine: also patch `texmfcnf.lua` Fixes #14463. Commit: 9cc724e570ebe6dcb6089e2fcd9c65f79ca85a01 https://github.com/NixOS/nixpkgs/commit/9cc724e570ebe6dcb6089e2fcd9c65f79ca85a01 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-09 (Mon, 09 Ma

[Nix-commits] [NixOS/nixpkgs] 840d87: pytestdjango: init at 2.9.1

//pypi/ Commit: 02904055ecfba7fe9428b9acce893aeae800b13c https://github.com/NixOS/nixpkgs/commit/02904055ecfba7fe9428b9acce893aeae800b13c Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-09 (Mon, 09 May 2016) Changed paths: M pkgs/top-level/python-packages.nix Log Message:

[Nix-commits] [NixOS/nixpkgs] 14c22a: calibre: Fix file already exist building problem

hanged paths: M pkgs/applications/misc/calibre/default.nix Log Message: --- calibre: Fix file already exist building problem Commit: e892c52737bc6de4741f22a198013e34490b0d21 https://github.com/NixOS/nixpkgs/commit/e892c52737bc6de4741f22a198013e34490b0d21 Author: zimbatm

[Nix-commits] [NixOS/nixpkgs] 440ea1: p11-kit: 0.23.1 -> 0.23.2

07 May 2016) Changed paths: M pkgs/development/libraries/p11-kit/default.nix Log Message: --- p11-kit: 0.23.1 -> 0.23.2 Commit: a6db0572292647d80a70bb6fcf83c01190e5d387 https://github.com/NixOS/nixpkgs/commit/a6db0572292647d80a70bb6fcf83c01190e5d387 Author: zimb

[Nix-commits] [NixOS/nixpkgs] 4d1575: firefox: Fix build due to commit #ab0a0c

Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-08 (Sun, 08 May 2016) Changed paths: M pkgs/applications/networking/browsers/firefox/wrapper.nix Log Message: --- Merge pull request #15299 from sorpaas/fix-firefox2 firefox: Use refactored makeSearchPathOutput Co

[Nix-commits] [NixOS/nixpkgs] 39b334: numix-gtk-theme: 2.2.3 -> 2.5.1

hanged paths: M pkgs/misc/themes/gtk3/numix-gtk-theme/default.nix Log Message: --- numix-gtk-theme: 2.2.3 -> 2.5.1 Commit: 9c3c8f55b6d9222c723e81b2b51e1920a3e1f0aa https://github.com/NixOS/nixpkgs/commit/9c3c8f55b6d9222c723e81b2b51e1920a3e1f0aa Author: zimb

[Nix-commits] [NixOS/nixpkgs] 07a83f: firefox-bin: fixed missing icon

Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-08 (Sun, 08 May 2016) Changed paths: M pkgs/applications/networking/browsers/firefox-bin/default.nix Log Message: --- Merge pull request #15302 from taku0/firefox-bin-icon firefox-bin: fixed missing icon Co

[Nix-commits] [NixOS/nixpkgs] 7f34b6: tint2: 0.12.9 -> 0.12.10

08 May 2016) Changed paths: M pkgs/applications/misc/tint2/default.nix Log Message: --- tint2: 0.12.9 -> 0.12.10 Commit: 3ce3a424092f81af9dbce090650db8875ded0eb3 https://github.com/NixOS/nixpkgs/commit/3ce3a424092f81af9dbce090650db8875ded0eb3 Author: zimb

[Nix-commits] [NixOS/nixpkgs] 5b7a1b: travis: also check NixOS options

output unless there's a failure. Commit: 0d3aa5cfc99a3e908dd948ab828b2fda1579b894 https://github.com/NixOS/nixpkgs/commit/0d3aa5cfc99a3e908dd948ab828b2fda1579b894 Author: zimbatm <zimb...@zimbatm.com> Date: 2016-05-08 (Sun, 08 May 2016) Changed paths: M maintainers/script

Re: [Nix-dev] mcaffee on nixos?

Would running mcaffee in a windows VM count ? :p On Fri, 6 May 2016 13:01 Eike, wrote: > > Hi all, > > I may be allowed to install my favorite Linux distro on my corporate > notebook (a mac…). But there is the requirement that I run a mcaffee > agent. Does possibly anyone has

Re: [Nix-dev] [***SPAM***] Re: On commit naming conventions

Thanks for reading in between the lines of what I said by the way. Removing the naming convention is an implementation detail and my main concern is to avoid putting contributors off with details that seem too nit-picky. So the consensus is that: if no new data is provided for 3 months,

Re: [Nix-dev] Feedback requested: new `boot.kernelPatches` option

Just got some random thoughts attached to what you said. makeObject looks like a cleaner implementation of lib.makeOverridable which is used to wrap all callPackage derivations. I haven’t thought deeply about that stuff though. Regarding the naming, I think in nix an “object” is a set that has a

Re: [Nix-dev] mix bundlerEnv and python3.buildEnv

Or if the dependency is a runtime dependency then maybe create another pkgs.buildEnv that merges both environments. On Thu, 5 May 2016 at 00:25 Rok Garbas wrote: > Hi Maxim, > > i think you will have to adjust ``bundlerEnv`` to be able to "merge" > it with

Re: [Nix-dev] On commit naming conventions

t insightful (disregard the title) about how to not be > too much of a stickler with new committers: > https://blog.spreedly.com/2014/06/24/merge-pull-request-considered-harmful/ > > Graham > > > On May 4, 2016, at 6:26 AM, zimbatm <zimb...@zimbatm.com> wrote: > > > >

[Nix-dev] On commit naming conventions

Each contributor has his own motivations and every round were we provide feedback is another one where we might lose the contributor. He might run out of energy, or have moved onto other things. Even after improving the CONTRIBUTING.md, naming of commits is still a really big friction to getting

Re: [Nix-dev] Stripped down Linux distribution based on Nix/NixOS

Hi, Do you plan on using systemd as your system init ? I mean you can still use nixpkgs and it would probably be useful in itself but you would need to generate your own activation scripts. How do you plan on shipping security updates ? If the system is in the initrd I suppose it's immutable and

Re: [Nix-dev] Specifying timezone in systemd timer config startAt

Hi, did you try asking the systemd people directly ? I think they will best know as it's really a functionality of their sub-system. Best, z On Tue, 26 Apr 2016 at 12:55 4levels <4lev...@gmail.com> wrote: > Hi Nix-devs, > > is it possible to have the startAt attribute take a given timezone in

Re: [Nix-dev] runuser from utillinux not working.

Hi, Is the setuid flag set ? Suid programs are special in nixos so it's possible runuser didn't get classified properly. On Thu, 14 Apr 2016 03:03 Kevin Cox, wrote: > Hello, > > I was trying to use runuser from utillinux to run a process as another > user but ran into a

Re: [Nix-dev] User-oriented nixpkgs documentation (was: ioquake3 on nixos)

Good question. The wiki seems like the right place to me but it's read-only now. On Fri, 8 Apr 2016 at 11:36 Nikolay Amiantov wrote: > Hi, > > I want to add some documentation on how to use our ioquake3 derivation. > This brings me to question on _where_ should I actually add it.

[Nix-dev] import vs override

Hi, stupid question of the day. When I see things like recurseIntoAttr in all-packages.nix I am left wondering why this is better than repeated `import ./-packages.nix { lang = lang_1_0; }`, where lang_1_0 would vary. Does anybody know ? /z ___ nix-dev

Re: [Nix-dev] JAVA_HOME and other environment variables

be a > JAVA_HOME. That's Oracle's take on this, but... well, I prefer Nix to have > as few surprises as possible. > > On Sun, Mar 6, 2016 at 8:12 PM zimbatm <zimb...@zimbatm.com> wrote: > >> What if the JRE(s) also included a `java-env.sh` that can be sourced ? >> Th

Re: [Nix-dev] yet another npm2nix reengineering attempt

As long as it's more reliable than what we have right now I'm all for it. First we need reliable, then optimize closure size. On Tue, 1 Mar 2016 at 14:42 Sander van der Burg wrote: > Haha :) > > Well, I have been thinking about keeping the packages and all their >

Re: [Nix-dev] Open source team messaging: mattermost

The issue with these services is that everyone has to install their client. Then each community thinks this *other* tool is cooler, which obviously requires another client. And then I need 10 clients running at the same time, all with different UI and keyboard shortcuts. At least with IRC I've got

Re: [Nix-dev] Adding hostnames to 127.0.0.1 in /etc/hosts

I don't know why [hostname]-encrypted exists but having multiple lines with the same address is fine. You can also have multiple names on the same like like: 127.0.0.1 node guzzle On Tue, 1 Mar 2016 at 12:11 4levels <4lev...@gmail.com> wrote: > Dear Nix'ers, > > I've been wondering how all my

Re: [Nix-dev] Commit access

IMO the mention bot already does a great job at getting notified without having to watch the whole repo. The next thing would be to get a more reliable and fast CI for the PRs. Right now there are too many false negatives which trains us to ignore the red. Waiting for hours for something small to

Re: [Nix-dev] NixON initiative

ner <hhochleit...@gmail.com> wrote: > 2016-02-28 15:35 GMT+01:00 zimbatm <zimb...@zimbatm.com>: > >> No, not the dead president :) JavaScript has JSON and Nix has NixON. A >> subset of the language that only contains literal values. >> > > > Cool Idea! Here is

Re: [Nix-dev] new tool: nixos-typecheck

Sounds good. Regarding the name, isn't that more of a nixos-lint or does it do type inference to find type mismatches ? On Mon, 29 Feb 2016 02:17 Thomas Strobel, <4ZKTUB6TEP74PYJOPWIR013S2AV29YUBW5F9ZH2F4D5UMJUJ6S@hash.domains> wrote: > Hi! > > There is the new tool "nixos-typecheck" available

Re: [Nix-dev] NixON initiative

and propose importJSON to be added to the stdlib. On Sun, 28 Feb 2016 at 17:48 Moritz Ulrich <mor...@tarn-vedra.de> wrote: > > zimbatm <zimb...@zimbatm.com> writes: > > ``` > > $ nix-prefetch-git git://github.com/direnv/direnv.git 2>/dev/null | tee > > repo.

Re: [Nix-dev] NixON initiative

> On Sun, Feb 28, 2016, 11:06 AM zimbatm <zimb...@zimbatm.com> wrote: > >> But we wouldn’t have the path type in JSON anymore ! Hmm maybe that’s a >> good thing actually :p >> >> importJSON = path: builtins.fromJSON (builtins.readFile path); >> >>

[Nix-dev] NixON initiative

No, not the dead president :) JavaScript has JSON and Nix has NixON. A subset of the language that only contains literal values. Thanks to Tim Cuthbertson (@gfxmonk) nix-prefetch-git now outputs valid NixON. Would it make sense to convert more of our tooling to using that notation forward ? The

Re: [Nix-dev] Fwd: Wiki is dead

phs around and edit to have the new content. We might > > > also compose a list of tags with examples on what we typically use them > > > for.) > > I can confirm that. For small edits, it is enough to copy from the > surroundings. > > On 16-02-23 10:22pm, zimbatm wr

Re: [Nix-dev] Should I install XCode when using Nix on OS X?

You shouldn't but In the mean time use `xcode-select --install` to just install the command-line tools. It should save you some space. On Wed, 24 Feb 2016 at 14:01 Anders Lundstedt wrote: > I use Nix on OS X 10.11.3. "nix-env -iA nixpkgs.vimHugeX" fails > because the

Re: [Nix-dev] Fwd: Wiki is dead

I started writing some docbook. Maybe I will get used to it but writing `foobar` is way more painful that `* foobar` in markdown. Especially in writing I think it's important to be able to move text around without too much overhead so that text can be reworked until it feels right. Thanks god

Re: [Nix-dev] On nixpkgs and reasonable code size

We have nixpkgs/pkgs/build-support/upstream-updater. I think it's a tool that takes metadata from a package to find updates. But it's used by 8 packages tops and it's doc is in doc/old/update-upstream-data.txt. Somewhere we also have a tool that tracks CVEs against packages with a heuristic but I

Re: [Nix-dev] On nixpkgs and reasonable code size

Related to the discussion, apparently even Debian has trouble keeping-up with security updates: https://statuscode.ch/2016/02/distribution-packages-considered-insecure/ It's not a simple problem for sure. On Mon, 22 Feb 2016 at 09:35 Adrien Devresse wrote: > I think the inflow

Re: [Nix-dev] How to set up your own Hydra server (video tutorial)

I have a tentative branch that you can steal. It compiles but I haven't tried to run it yet: https://github.com/zimbatm/nixpkgs/tree/hydra-module . It's really cool what you can do with release.nix but it's also hard to convert into a standard mkDerivation so I'm not sure I got all

Re: [Nix-dev] On nixpkgs and reasonable code size

their maintainer role and focus on the core packages to make sure they are in good shape. Cheers, z On Sun, 21 Feb 2016 at 14:58 Vladimír Čunát <vcu...@gmail.com> wrote: > On 02/21/2016 03:17 PM, zimbatm wrote: > > tl,td; I think that we should split nixpkgs/pkgs in two > > OK, l

[Nix-dev] On nixpkgs and reasonable code size

Hi list, tl,td; I think that we should split nixpkgs/pkgs in two nixpkgs is getting pretty huge. There is so much surface, I don't think that a single person can keep up with the pace of change and still manage to do other things in the same day. Luckily we do have ~5 super-human people taking

Re: [Nix-dev] Fractalide is ready to use.

Interesting. Do you have any further examples than the readme ? I wonder if we should extend nix's multi-line string syntax to accept a shebang-like so that editors can can switch the syntax in that context. On Sat, 20 Feb 2016 at 19:14 stewart mackenzie wrote: > Ah yes a

Re: [Nix-dev] codetriage.com

I was looking for a way to visualize the number of open issues over time and found this: https://9-volt.github.io/bug-life/?repo=nixos/nixpkgs .Unfortunately we have too much content and it's hitting the API rate/limit. The idea was to see the current trend. Maybe after 2-3 weeks of codetriage the

Re: [Nix-dev] Installing CA certificates

's 21 (unable to verify the first certificate). > > This is all way over my head. I have some more reading to do. Once I do > figure it out, I think I will suggest having the NixOS module take care of > whatever steps are necessary to fix this, assuming it can be done in a > reprodu

Re: [Nix-dev] Wiki is dead

in helping out cleaning the content and potentially become one of the owners of it. On Tue, 16 Feb 2016 at 17:28 Profpatsch <m...@profpatsch.de> wrote: > On 16-02-14 09:15pm, zimbatm wrote: > > But before I invest more time, do you think it's a path worth pursuing ? > > Also w

Re: [Nix-dev] Installing CA certificates

Found this which might be useful to you: http://mindref.blogspot.co.uk/2011/02/nssdb-add-ca-certificate.html On Fri, 19 Feb 2016 at 17:36 zimbatm <zimb...@zimbatm.com> wrote: > curl should work just fine then. Can you paste the output of `curl -v > https://yoursite.com` ? > >

Re: [Nix-dev] Installing CA certificates

eeds to happen for curl and Chromium to be able to use them? > > On Fri, Feb 19, 2016 at 9:26 AM zimbatm <zimb...@zimbatm.com> wrote: > >> What is the output of `echo $SSL_CERT_FILE` and `echo $CURL_CA_BUNDLE` ? >> If one of those is set, look in the pointed file if you can fi

Re: [Nix-dev] Installing CA certificates

What is the output of `echo $SSL_CERT_FILE` and `echo $CURL_CA_BUNDLE` ? If one of those is set, look in the pointed file if you can find your certificate. On Fri, 19 Feb 2016 at 15:12 Adam Russell wrote: > Thomas, I've not used the openssl command-line tool before, and

[Nix-dev] Bash style in nix expressions

Hi list, Haskell has a really cool package called ShellCheck which you can run against shell scripts. It's a linting tool that catches a ton of issues, especially escaping ones. Unfortunately nix expressions embed the shell fragments so it's hard to run the tool against them. Has anyone had any

Re: [Nix-dev] [***SPAM***] Using nix-shell in messy trees with symlinks and binary files

Maybe attach your default.nix so we can have a look. I suspect that you're loading the whole nixpkgs in your shell somehow. A version of nix and channels could also come handy On Thu, 18 Feb 2016 18:25 Kosyrev Serge wrote: > Good day, folks! > > What I'm seeing is a

Re: [Nix-dev] Installing CA certificates

Yes use `security.pki.certificates` or `security.pki.certificateFiles`. I don't know why there is a comment there, you can just ignore that bit. If you use `security.pki.certificateFiles` don't forget to add back "${pkgs.cacert}/etc/ssl/certs/ca-bundle.crt" in your array. On Thu, 18 Feb 2016 at

Re: [Nix-dev] How to set up your own Hydra server (video tutorial)

I watched the video yesterday and loved it. Before the video hydra was that thing that does the builds and I don't know how it works. After the video I feel like I can setup one myself. Thanks Peter ! One question that was raised, does anyone know why the hydra modules aren't part of nixpkgs ?

Re: [Nix-dev] loading the nix-shell in a jenkins job

.github.com/aespinosa/96ea991e0a938aaee109 > > I tried your wrapper and I get the same "undefined variable ‘jupyter’ > ..." error. However, running it on the console works manually works. > > On Tue, Feb 16, 2016 at 11:32 AM, zimbatm <zimb...@zimbatm.com> w

Re: [Nix-dev] Git + gettextWithExpat incompatibility

Can you create an issue ? I can reproduce the issue on master. If just `nixos.gettext` is installed it works fine. I also tried changing the EDITOR but that's not it. Note that git-rebase is implemented in bash On Tue, 16 Feb 2016 at 18:23 Mikhail wrote: > Hi! > > I've

Re: [Nix-dev] loading the nix-shell in a jenkins job

> #!nix-shell -i bash > > jupyter --version > > Hope somebody else finds this useful. > > Regards, > Allan > > On Tue, Feb 16, 2016 at 8:49 AM, zimbatm <zimb...@zimbatm.com> wrote: > > It looks legit. > > > > Something I noticed is that n

Re: [Nix-dev] loading the nix-shell in a jenkins job

It looks legit. Something I noticed is that nix-shell still drops me in a shell if it thinks that the input is interactive. Can you try to run the same command but with `cat | ` piped in front ? On Tue, 16 Feb 2016 at 02:06 Allan Espinosa wrote: > Hi, > > I've been trying

Re: [Nix-dev] Packaging Torch

qtwebkit doesn't appear if you grep pkgs/top-level/all-packages.nix but it's imported from pkgs/development/libraries/qt-5/5.4/qtwebkit at the moment. Good luck with the packaging ! On Tue, 16 Feb 2016 at 13:30 Sergey Mironov wrote: > Hi, List. I'd like to use Torch

Re: [Nix-dev] Wiki is dead

Also we are not alone with the spam :) [22:37] alad: I forgot to ask, how do you guys fight against spam on the wiki ? [22:38] zimbatm: there was a recent spam wave, so we've restricted mediawiki API access, add a more difficult captcha, and enabled some extensions like spamregex On Mon, 15

Re: [Nix-dev] Wiki is dead

Alright, let me know how I can help. Personally I am looking forward to much more scoped discussions like how to improve a specific page. On Mon, 15 Feb 2016 at 22:30 Rok Garbas <r...@garbas.si> wrote: > Hi Zimbatm and Peter, > > On Mon, Feb 15, 2016 at 1:41 PM, Peter Simons

Re: [Nix-dev] Are nix-shells supposed to nest?

/nix/store/dkwhsgc5qa52hbpn3pg9zzz4kqsclzv0-xz-5.2.2/bin:/nix/store/5idnvskkm4hky2fj335xfbqpfim3g9pd-gcc-4.9.3/bin:/nix/store/iyw7cmmg2yi5cwc1pswfm0wrn1ssk1zh-binutils-2.23.1/bin:/nix/store/n2wxp513rr00f6hr2dy0waqahns49dch-glibc-2.21/bin:/nix/store/9s9r019176g7cvn2nvcw41gsp862y6b4-coreutils-8.24/bin:/home/zimbatm

Re: [Nix-dev] Dynamic substituteInPlace

It's not super clear to me what you are trying to achieve. Maybe you've zoomed into that specific solution but with more context there might be others available. Is the file compiled or is it interpreted ? I understand that you want to provide some information at runtime and resolve the path to

Re: [Nix-dev] Wiki is dead

such an awesome wiki. how do you manage it, is somebody owning the wiki ? [21:30] zimbatm: pierre manages the technical side of the wiki, and you have like 3 people watching over the daily happenings [21:30] zimbatm: otherwise it's just community maintained [21:30] don't forget the goat blood

Re: [Nix-dev] Wiki is dead

be contributing in some other ways :) On Sun, 14 Feb 2016 at 21:19 Arseniy Seroka <ars.ser...@gmail.com> wrote: > There was a huge discussion about wiki's future [1]. > > [1] http://lists.science.uu.nl/pipermail/nix-dev/2015-November/018645.html > > 2016-02-15 0:15 GMT+03:00 zimbatm

Re: [Nix-dev] Wiki is dead

. The nice thing about that approach is that we can re-run the import any time until it's ready. But before I invest more time, do you think it's a path worth pursuing ? Also what would be required for this to be considered "ready" ? Link to repo: https://github.com/zimbatm/nixos-wiki-test

Re: [Nix-dev] Travis Testing Needs Rethinking

What if master was always the latest successful hydra build ? People could rebase on top and have cached builds. Nox could also have cached builds. Instead of merging a PR we would instruct Hydra to queue the build. If the build is successful hydra would merge it into master and close the PR.

Re: [Nix-dev] Wiki is dead

Is it possible to get a dump using dumpBackup.php ? https://en.wikipedia.org/wiki/Help:Export I would like to try something out now that the wiki is read-only. On Wed, 10 Feb 2016 at 16:50 Domen Kožar wrote: > Thanks! > > On Wed, Feb 10, 2016 at 4:49 PM, Eelco Dolstra < >

Re: [Nix-dev] FOSDEM 2016

One here ! On Fri, 29 Jan 2016 08:34 Domen Kožar wrote: > Hi all, > > who's going to FOSDEM this year? I'm skipping this year - I hope you all > have a really great time! > > I see there is one talk on Nix: > https://fosdem.org/2016/schedule/event/microkernels_genode_nix/ > >

Re: [Nix-dev] Going through hell with systemd timers

tart the service once. >> $ systemctl status urlwatch.service -l -n 1000 : See the systemd logs >> for the last run, up to 1000 full lines. >> # journalctl -xef --unit=urlwatch : Print all the logs, -f follows the >> output in real time. >> >> A very simple trick is indeed

Re: [Nix-dev] Going through hell with systemd timers

One common error with system services are missing environment variable. When testing with your shell you will have $HOME set for example. On Thu, 28 Jan 2016 09:43 4levels <4lev...@gmail.com> wrote: > Hi Exi, > > thank you for your reply. > > This is the timers config I'm using (note that I'm

Re: [Nix-dev] Redirect SDDM/LightDM (X.0.log & .xsession-errors) to JournalCTL

I don't know about X.0.log but since .xsession is just a bash script you could use something like: #!/usr/bin/env bash exec &> | logger & # the usual stuff On Tue, 26 Jan 2016 at 05:01 Roger Qiu wrote: > Hi, > > How does one redirect the logs (X.0.log) and

Re: [Nix-dev] How to get correct length of a string containing non-ascii characters

Related to that, the suckless conferent talk on UTF-8[1] was pretty interesting. The complexity of Unicode and all that goes with it is pretty crazy. That being said the libutf8 from the same guys seem to be pretty decent and takes sane defaults to a lot of these questions. [1]

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

Okay, now we just need *someone* to implement a proof of concept :p On Sun, 10 Jan 2016 at 11:13 ikrek vagyunk wrote: > dear fellow nixers, > > i followed this discussion and would like to propose (the already > proposed) way of sorting packages alphabetically and then

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

The issue with naming is that everyone has their opinion. Since other smart people have already played the categorization game can I suggest to restrict the discussion to which *existing* structure we should adopt ? There are a lot of big repositories out there: debian, gentoo portage, archlinux,

Re: [Nix-dev] Perl -> C++

On top of better defining the language it would also be helpful if the nix commands could be classified in core vs plumbing like git does. In theory only the core commands and the nixpkgs are required to bootstrap a fully-functioning nix platform right ? On Thu, 7 Jan 2016 at 13:18 Tomasz Czyż

Re: [Nix-dev] Perl -> C++

C++ supports on whole lot more platforms than the proposed alternatives. If Nix is to become a universal package manager it seems important as a feature. That being said, we're bound to have security issues if the nix-daemon is it's written in an unsafe language. On Thu, 31 Dec 2015 at 11:36 Luca

Re: [Nix-dev] How do you manage bare-metal local servers with nixops

Rohit, try something like this: https://gist.github.com/zimbatm/d466ef56f88605f78f99 On Mon, 14 Dec 2015 at 22:47 Domen Kožar <do...@dev.si> wrote: > You might want to test https://github.com/NixOS/nixpkgs/pull/11279 > > On Mon, Dec 14, 2015 at 10:45 PM, rohit yadav <rohity

Re: [Nix-dev] How do you manage bare-metal local servers with nixops

Hi rohit, Personally I just have a folder per machine with the /etc/nixos folder and a little script that runs rsync + `nixos-rebuild --switch` on the target machine. Over time I will probably switch to using nixops as well but for a start it's working super well for me. Especially since it

Re: [Nix-dev] Secure NixOS

Hi Seroka, just a couple of idea: (1) is really cool but could also be solved by having faster builds and binary diffs. I really liked the presentation at NixCon and think that it's a really cool hack but don't understand all of the implications. Just as an anecdote; ruby has had a release with

Re: [Nix-dev] nix for reproducible and self-updating developer environments

Lots of good points, definitely experiencing most of these issues myself (especially the SSL issues lately). In terms of language support, it seems that we're slowly getting there. That's what I got from NixCon, lots of people interested in helping out. But yeah, it takes time. I think that first

<    1   2   3   4   5   >