[Nix-dev] Literal “magic” strings in nixpkgs

I noticed there is a trend to use magic strings in some places of nixpkgs, e.g. in https://nixos.org/nixos/manual/ch-options.html#opt-security.pki.certificateFiles where the example is: [ ${pkgs.cacert}/etc/ca-bundle.crt ] I find that alarming, because in exactly that case it silently broke when

[Nix-dev] Hydra seems to be down

I’m not sure if this is the best place, but: hydra.nixos.org is not responding to requests. http://isitup.org/hydra.nixos.org This service confirms that it’s not just my local network. It works very seldomly, sometimes after 15 minutes, so it looks more like an overload problem. -- Proudly

Re: [Nix-dev] Fundraiser?

On 15-12-07 04:36pm, Tomasz Czyż wrote: > https://www.bountysource.com/search?query=nixos - maybe this is good > enough, no? Just needs a little more advertisement :-) My problem with Bountysource is that most bounties are a flipping joke compared to what someone would earn in even badly paid

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

On 16-01-04 12:34am, em...@vfemail.net wrote: > If someone is interested in a pure Rust implementation, then a prerequsite > would be to > come up with a rigorous definition of the language and all of the builtins, > and then > identifying the unix specific builitins and derivation behavior. I

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

Full ack for flattening all-packages.nix. I didn’t even know there where sections until a few days ago, the file is simply too large. Let’s just sort the top level by alphabet. On 16-01-08 01:10am, Luca Bruno wrote: > So I propose to still have directories, but chosen by maintainers. For >

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

On 16-01-08 08:53am, Daniel Peebles wrote: > and that > all-packages.nix should be abolished (use builtins.readDir by default and a > manual overrides file where necessary) Strong -1 on this one. #1: Explicit is better than implicit Things will get very ugly. -- Proudly written in Mutt with

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

On 16-01-08 10:16pm, Tomasz Czyż wrote: > 2016-01-08 14:58 GMT+00:00 Vladimír Čunát : > > The largest problem I see for categorization is ambiguity (mentioned > > already). The "categories" will always overlap nontrivially, so we would > > better track such information in a

[Nix-dev] Regarding the Wiki

We have basically decided to shut it down soon (™), right? Just now I tried to set up my printer again. For that I first looked at docs and the source, which didn’t provide any helpful info, and then I found the article on generating the correct Cups files here: https://nixos.org/wiki/Printers

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

On 16-01-09 10:56am, Jonathan Glines wrote: > 2016/01/09 午前10:36 "Profpatsch" <m...@profpatsch.de>: > > > > On 16-01-08 08:53am, Daniel Peebles wrote: > > > and that > > > all-packages.nix should be abolished (use builtins.readDir by default &g

Re: [Nix-dev] Set up a Sufficiently Powerful Build Farm

On 15-12-22 10:27am, Christian Theune wrote: > I could put one or more mac minis in our office on a reasonable big pipe > (100mbit fibre up/down). Question is whether we could fund them somehow. > Would a single additional machine help or do we need multiple? (For > anchoring: the app store

Re: [Nix-dev] Meetup in Munich today

On 15-11-25 03:51pm, Franz Pletz wrote: > Don't worry, no advertising for our company will take place. We're not > yet using NixOS here but we're actively trying to infect all our > co-workers and the management. Having an active local community is one > of the best first steps in our opinion. ;)

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-24 09:14pm, zimbatm wrote: > Please no XML as the source, it adds way too much emphasis on the structure > instead of the content. > > Asciidoc is pretty good. It can be configured quite close to markdown >

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-19 05:17pm, Cillian de Róiste wrote: > 2015-11-19 16:57 GMT+01:00 Profpatsch <m...@profpatsch.de>: > > On 15-11-19 02:56am, Roger Qiu wrote: > > May I humbly suggest http://stevelosh.com/blog/2013/09/teach-dont-tell/ as > > a general documentation writing t

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-23 08:03pm, Jan Malakhovski wrote: > That is, I'd like > > * All the docs to be available and discoverable locally. > /run/current-system/sw/share/doc FTW. (easy to do) Yes, please. > * To have a thing that indexes all the man, info and haddock pages for > full text search using

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-19 02:56am, Roger Qiu wrote: > Can the manual be made as a gitbook with the chapters fleshed out better > and made more user friendly? One part of the manual can be very fact > based, another part can be story based. Kind of like the difference between > documentation vs api

[Nix-dev] Splitting packages silently breaks a lot of stuff

In the past month or so more and more packages have been split into multiple outputs. I like that, but: Doing so breaks lots of dependencies silently. I think that is a very bad problem we need to address. Every program with runtime dependencies does build just fine, but breaks once its

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

On 16-06-09 05:25pm, Anthony Cowley wrote: > I think that telling users to stick to a single version of nixpkgs and take > responsibility for cherry-picking individual security and bug fix commits to > all Haskell and system libraries they depend on is the worst job a package > management system

[Nix-dev] Wrapping single python executable in pulseaudio /bin

pulseaudio contains a python script called qpaeq which is not correctly packaged yet. First, the shebang needs to be patched. I managed to achieve that by call wrapPythonPrograms in postInstall. Second, the scripts has a dependency on pythonPackages.pyqt4. I tried inserting that into every

[Nix-dev] NixOS Hackathon Augsburg, June 25./26.

In parallel to the Berlin hackathon the OpenLab Augsburg invites everyone who can’t make it, to work on Nix/NixOS for two days and maybe stream the talks from Berlin. Since we are a hackerspace there will be drinks, there is a kitchen und an inviting amount of chaos for you to enjoy. :)

[Nix-commits] [NixOS/nixpkgs] c7d288: mpv: add script infrastructure & convert script

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: c7d288fd569cbd38df1cfdff91a757393475fd42 https://github.com/NixOS/nixpkgs/commit/c7d288fd569cbd38df1cfdff91a757393475fd42 Author: Profpatsch <m...@profpatsch.de> Date: 2016-05-28 (Sat, 28 Ma

[Nix-dev] Tomorrow NixOS Hackathon at Gullaschprogrammiernacht in Karlsruhe, Germany

We just organized a spontaneous Hackathon at GPN. Tomorrow, Sat 2016-05-28, 12:00–20:00 https://entropia.de/GPN16 We’ll try to set up some kind of sign. :) Zentrum für Kunst und Medientechnologie Karlsruhe Germany -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five

Re: [Nix-dev] Malicious installation methods

On 16-06-18 11:46pm, Bardur Arantsson wrote: > On 06/18/2016 11:18 PM, Profpatsch wrote: > > > > The script approach is not very bad. Maybe sign it with gpg for people > > who want to verify it. > > > > Have you been following along on the thread at all? Signing

Re: [Nix-dev] Malicious installation methods

On 16-06-18 05:27pm, Michiel Leenaars wrote: > Regarding the installer: it would be cool to have something like > http://appimage.org, http://orbital-apps.com, http://flatpak.org or > http://snapcraft.io instead of a shell script. That would have a SHA > that could be verified, etc. It would be

Re: [Nix-dev] Best way to install nix packages from github repo

On 16-06-25 12:25pm, Kelong Cong wrote: > Hi Nix devs, > > If I see a package I want in the nixpkgs GitHub repo but it is not > released yet, what's the best way to install it along side my current > nix packages? I suppose you could download the .nix file, but is there a > better way? you can

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

On 16-02-20 03:11pm, Anthony Cowley wrote: > The point being that once a wiki item gets a handful of positive votes, it > gets turned into an Issue on the manual for someone with a better > understanding of how things are put together to find it a home. At that > point, the wiki item could have a

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

> On Tue, 23 Feb 2016 at 21:29 Vladimír Čunát wrote: > > My personal opinion is that this is mostly an excuse. It's a XML subset > > and everyone should know at least a bit of (X)HTML or similar stuff. > > Note that for almost all docs we use ~10 types of tags and the format is

[Nix-dev] Notes and ideas about the Nix-UI proposal

Eelco wrote a first proposal about the new nix CLI tool https://gist.github.com/edolstra/efcadfd240c2d8906348 I thought about it and wrote down a few ideas and proposals where I think that can be improved: https://gist.github.com/Profpatsch/d5c8e1ccd68baab0e3f0 In particular I think I have found

Re: [Nix-dev] Put configuration.nix under version control

On 16-01-20 06:24pm, Owen Lynch wrote: > Hello, > > I'm wondering if there is a standard/recommended way to put > /etc/nixos/configuration.nix under version control. It would make managing > lots of virtual machines a lot easier, because I could have a script that > updated to the latest

Re: [Nix-dev] Redesign of documentation

On 16-02-15 06:57pm, Freddy Rietdijk wrote: > Furthermore, I can imagine a third > part with How To's could be added to the Nix user guide. These are commonly called “Cookbook” and in my experience they are an invaluable source of practical information. We kind of have something similar in the

Re: [Nix-dev] Wiki is dead

On 16-02-14 09:15pm, zimbatm wrote: > 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" ? Wow, that’s great! What are your thoughts on converting it to a nixos (and nix) cookbook, akin to the Python Cookbook

[Nix-dev] codetriage.com

I just created a Repo page for nixpkgs at codetriage.com. It is a simple site that sends you 1 open issue each day once you sign up with your Github account. Maybe a few people want to join me. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A:

Re: [Nix-dev] Installing CA certificates

On 16-02-18 01:53pm, Adam Russell wrote: > Hello Nix-Dev, > > I'm trying to understand how to install CA certificates in NixOS. Different question, related topic: I tried adding CA-Cert by default a while ago and had the impression it worked for a while and then suddenly stopped working (at

Re: [Nix-dev] codetriage.com

On 16-02-17 08:18pm, Rok Garbas wrote: > I would suggest closing tickets that you think are not crucial or > reporter does not provide code that we can include. Ofcourse be nice > in comment and ask reported to reopen if they think you are wrong to > do this. > > What you say, could this work and

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

On 16-03-08 06:30am, Wout Mertens wrote: > With IRC, you have to open your client, fire off your question a few times > and hope that someone will know the answer eventually. I can't have IRC > open at work all day. You haven't heard of bouncers? ZNC for example. If as a developer you run an IRC

Re: [Nix-dev] NixON initiative

On 16-02-28 04:44pm, zimbatm wrote: > So something like that ? https://github.com/NixOS/nixpkgs/pull/13552 > And then we would convert all of our tooling to output JSON ? As long as nixexprs embedded in the JSON are *not* evaluated in any way, we are fine. Think of { "hello" = "{ foo = (abort

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

On 16-03-01 11:46pm, Teo Klestrup Röijezon wrote: > Plain IRC sucks. It’s true, but it f* works. Especially for developers, devs who can’t configure an IRC client? Are those people devs? But I know the pain. Hm, we even use IRC as main communication tool in our Hackerspace, and so far even

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

On 16-02-29 03:16am, Hash Domains wrote: > What do you think? Tried to test it on my local nixpkgs, but can’t get it working. nixpkgs> nixos-typecheck printUnspecified ./nixos error: attribute ‘typechecker’ in selection path ‘typechecker.printUnspecified’ not found Happens also with --help, so

Re: [Nix-dev] Tool: Better code search on NixOS/*

On 16-03-04 08:25am, Vladimír Čunát wrote: > 2. > We have ctags wrapped with simple regexp that indexes simple 'foo =' > bindings. That has the advantage of integrating smoothly with many editors. Uh, that would be nice. Do you have a link? Right now I manually do the `foobar.=` search with

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

On 16-03-04 01:51pm, Thomas Strobel wrote: > Does the following command work: "nixos-typecheck printUnspecified -I > nixpkgs=/path/to/nixpkgs/from/PR/13607" ? It does indeed. But why can’t I directly give it the path to a module? -- Proudly written in Mutt with Vim on NixOS. Q: Why is this

Re: [Nix-dev] haskell structure for all of nixpkgs

On 16-04-25 03:15pm, Eric Merritt wrote: > I think these strongly win out, at at least for the Erlang/Beam world. The > downside is that grepping the > nixpkgs repository (my default way to search for a package) doesn't work > nearly as well. You are right, the „multiple releases“ approach

Re: [Nix-dev] Monitoring by default

On 16-04-22 02:08pm, Svein Ove Aas wrote: > - And I don't suppose I can deny being at Google, no, but this isn't a > Google project; I've just ended up using NixOS *everywhere* in my personal > life, so now I want monitoring. ;-) That’s what they always say right before they make a 10 person team

Re: [Nix-dev] break purity

On 16-04-22 06:33pm, Oliver Charles wrote: > It's certainly possible, because I just did it with Haskell ;) > > https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab Why do you need to put the atime two hours in the past? Does cabal recompilation check for it in order to find out

Re: [Nix-dev] Representation DevOpsDays Austin / Logo License?

On 16-04-28 07:19pm, Vladimír Čunát wrote: > Hi. > > On 04/28/2016 05:54 PM, Graham Christensen wrote: > > 1. Is there any promotional material I should pre-print / take with me / > >whatever to pitch NixOS? > > I'm fairly certain we don't have any official stuff like that. > > > 3. What is

Re: [Nix-dev] Nixbot - a little helper for pull requests

On 16-05-06 12:49pm, Rok Garbas wrote: > - another cool thing is that it would be nice to automatically merge > if somebody only changes version number (and that does not trigger to > much of a rebuild). how i envision this is that package can provide > default.json where we store all the metadata

Re: [Nix-dev] Nixbot - a little helper for pull requests

On 16-05-06 08:19am, Michael Raskin wrote: > >You can see it doing its thing here: > > > >https://github.com/nixbot/nixpkgs-sandbox/pull/9 > >So, thoughts and comments on this approach? I for one welcome our new cuteness overlord. Love the idea, because it makes it possible that people can

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

On 16-04-09 04:10pm, Anderson Torres wrote: > I prefer to start a documentation project, like the FreeBSD > Handbook[1]. It could contain some in-project documentation for every > module too. I proposed a Cookbook a while ago, akin to the Puppet one http://www.puppetcookbook.com/ We could write

Re: [Nix-dev] Difference between Pkgs, Super and Self in this Snippet

ver, and also their override mechanism which is very similar. e.g. https://github.com/openlab-aux/vuizvui/blob/master/machines/profpatsch/pkgs.nix#L15 -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read y

Re: [Nix-dev] Difference between Pkgs, Super and Self in this Snippet

On 16-04-13 06:56pm, Nicolas Pierron wrote: > On Mon, Apr 11, 2016 at 7:34 AM, Roger Qiu wrote: > > ``` > > { pkgs }: { # pkgs is the fully configured packages, after overrides > >packageOverrides = super: let self = super.pkgs; in rec { # super is > > without overrides,

Re: [Nix-dev] Upcoming PyPi URL Scheme Change

On 16-04-20 11:41am, Graham Christensen wrote: > I recently got word that PyPi is changing their URL scheme. > > Old example: > https://pypi.python.org/packages/source/a/ansible/ansible-1.8.2.tar.gz#md5=c2ac0e5a4c092dfa84c7e9e51cd45095 > > New example: >

Re: [Nix-dev] Too many open issues

On 16-07-24 03:12pm, Arnold Krille wrote: > FULL ACK! > > I couldn't said it any better. > > And please never, ever think about closing users contribution without > looking at them at least once by a human! +1 Having done a lot of triaging these past days there were (estimated) 30% issues

[Nix-commits] [NixOS/nixpkgs] e2f6c3: hasklig: 0.4 -> 0.9 (#17257)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e2f6c3b4d9bae53d39192b222f7e54fbdd6d2e75 https://github.com/NixOS/nixpkgs/commit/e2f6c3b4d9bae53d39192b222f7e54fbdd6d2e75 Author: Profpatsch <m...@profpatsch.de> Date: 2016-07-25 (Mon, 25 Ju

Re: [Nix-dev] Too many open issues

On 16-07-22 09:59am, Michael Walker wrote: > If there are 1000+ open issues, it's hard to know what to prioritise. > If inactive issues get closed, it at least helps cut down on things > which may no longer be relevant (and if they are, someone finds the > closed issue, comments in it, and it

Re: [Nix-dev] HaskellPackages in nix-dev, still maintained?

On 16-07-23 05:52am, andika.riyan wrote: > > > Hi, i just want to clarify on what i read somewhere in this mailing list > about the continuation of maintaining haskellPackages. From what i read > haskellPackages is no longer maintained in nix, is it true? > If so, then should we develop

[Nix-dev] Requesting issue closing rights

I like triaging, but not being able to close issues is a nuisance. Not sure what access rights are needed, but there’s probably a few people on the core team who know me by now. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es

Re: [Nix-dev] Requesting issue closing rights

On 16-07-25 05:36am, Rok Garbas wrote: > +100 lets get Profpatsch, kevincox and vrthra enough permission for nixpkgs > repo Bump. I moved the discussion to the nixpkgs repo, I think that might be a better place for it: https://github.com/NixOS/nixpkgs/issues/17379 -- Proudly written i

Re: [Nix-dev] Handling nix-shell shebangs with the new nix command

On 16-07-29 04:48pm, Shea Levy wrote: > Hi Eelco, > > For the perl->c++ work, how should we handle nix-shell shebangs given > that the command is now "nix shell"? Should the nix command itself > contain shebang-checking logic, or should we have a separate nix-shell > C++ program just for

[Nix-commits] [NixOS/nixpkgs] 632411: openjdk7: replace vulnerable cups version (#17214)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 632411c2b63b576e6d42f68f5588288f85a629d4 https://github.com/NixOS/nixpkgs/commit/632411c2b63b576e6d42f68f5588288f85a629d4 Author: Profpatsch <m...@profpatsch.de> Date: 2016-07-28 (Thu, 28 Ju

[Nix-dev] Packaging free software that costs money

Free software doesn’t mean it is free as in free beer. There are a couple of (very good) applications, that are sold, like for example Ardour or Radium. They are normally distributed as binaries, but come with the source code (as required by their license). I think nixpkgs should include them as

Re: [Nix-dev] Packaging free software that costs money

On 16-07-06 11:58am, zimbatm wrote: > We can provide the derivation but ask the user to download the source > themselves. I think we already have such a mechanism in place for non-free > software. But that’s not necessary at all. The source is available openly and we can also have hydra build the

Re: [Nix-dev] Packaging free software that costs money

On 16-07-06 10:16pm, Roger Qiu wrote: > I've been thinking about the mechanics of FOSS app stores. If you don't want > to handle the payments, you need to implement a kind of > payment-authentication, where the principle is the same as dealing with > private packages. Instead the key being used is

Re: [Nix-dev] Packaging free software that costs money

On 16-07-06 09:50am, Kevin Cox wrote: > On 06/07/16 09:25, Bjørn Forsman wrote: > > On 6 July 2016 at 14:19, Profpatsch <m...@profpatsch.de> wrote: > IIUC you can't "really require" money for a GPL program. You can charge > for the distribution or for binaries or

Re: [Nix-dev] Packaging free software that costs money

On 16-07-07 03:12am, Jookia wrote: > Is this going to be the Nix software store? No, but we should strife to enable developers however we can. We are only gathering stuff others gratiously provide us access to, after all. I think this goes further. Once we have e.g. donation info in nixpkgs, we

Re: [Nix-dev] Packaging free software that costs money

On 16-07-07 01:18am, Jookia wrote: > On Wed, Jul 06, 2016 at 04:35:51PM +0200, Moritz Ulrich wrote: > Is it really Nix's job to enforcing the business models of software, rather > than > just packaging it? Surely the application could just have a nag screen (if it > doesn't already.) How about

Re: [Nix-dev] new security possibilities?

On 16-07-05 04:12pm, Syd Brisby wrote: > Hi, > > NixOS has a unique packaging system, with app separation It goes deeper than that. Not only „apps“ are separated, but logical units, like e.g. config files as well. > and some > degree of encryption. None that I know of. Quite the contrary, the

Re: [Nix-dev] Packaging free software that costs money

On 16-07-07 01:18am, Renato Alves wrote: > To be honest I'm not even sure there's an issue here. I've never heard > of something called "free open-source that costs money". The first part > negates the second. That is incorrect. See https://www.gnu.org/philosophy/selling.html > Ardour was

Re: [Nix-dev] Packaging free software that costs money

On 16-07-08 01:58pm, Juho Östman wrote: >Basically, any distributor can require a payment, and if users are not >willing to pay, they would have to find some other way to obtain the >software. I think the idea is that people are generally okay to pay money, and if they are not, they

Re: [Nix-dev] Pinning nixpkgs on unstable channel: retention of cached packages

On 16-07-11 10:54am, Maarten Hoogendoorn wrote: > Hi there, > > I was wondering if it's safe to depend on any commit in the unstable > channel, and still be able to fetch the derivations build by Hydra from the > binary cache. You mean on the unstable channel itself? Or on commits the unstable

Re: [Nix-dev] GNU Guix & GuixSD 0.11.0 released

On 16-08-03 04:03pm, Ludovic Courtès wrote: > We are pleased to announce the release of GNU Guix & GuixSD 0.11.0, > representing 2,119 commits by 70 people over 4 months. Thumbs up for the effort. Would love to see some cross-fertilization between the projects. -- Proudly written in Mutt with

Re: [Nix-dev] Skillset labels

On 16-07-23 01:56pm, Wout Mertens wrote: > I don't know about using levels, you need to have a good knowledge of the > problem area to decide what level something is, and it can scare off people > that think they are not advanced even though they are. There is already the > good-first-bug label…

Re: [Nix-dev] Improve docs for overrideDerivation - overridable attributes

have a short overview of the various kinds of overriding mechanisms here: https://github.com/Profpatsch/nixpkgs-cheatsheet/blob/master/cheatsheet.org -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read

[Nix-dev] cache.nixos.org is down

It’s kind of flaky, so `curl https://cache.nixos.org` sometimes cannot resolve the host and sometimes outputs 404. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read your message. If it’s urgent,

Re: [Nix-dev] nix-bundle: Bundle Nix derivations to run anywhere

On 17-02-07 11:48am, Tomasz Czyż wrote: > I would vote for mirroring this tool in nixos github namespace (or even > trying to make this project official one) as it can have big impact of > propagating/implementing nix ideas into environments where it's not > straight forward to use it. > > What

Re: [Nix-dev] Arch is dropping i686. Should we?

On 17-01-26 08:37am, Graham Christensen wrote: > One person on IRC said they think they may have used it once. Does > anyone on this list use NixOS on i686? anyone on this list know anyone > using NixOS on i686? I’m using it for one old machine running the audio server of our hackerspace. --

[Nix-commits] [NixOS/nixpkgs] 31dac1: mpd: add avahi zeroconf support

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 31dac10c330faf453ba946cbf558c04ca19102b9 https://github.com/NixOS/nixpkgs/commit/31dac10c330faf453ba946cbf558c04ca19102b9 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-18 (Sat, 18 Fe

Re: [Nix-dev] cabal-install & nix (was: nix-shell pro/con (was: Python 3 as default))

On 17-02-23 12:45pm, Thomas Tuegel wrote: > The next version of cabal-install will perform this caching for you > automatically. It uses your shell.nix (if present) and adds GC roots for > the results. Your environment is not garbage collected or updated unless > you clear out the work directory

Re: [Nix-dev] cabal-install & nix (was: nix-shell pro/con (was: Python 3 as default))

On 17-02-23 07:52pm, Thomas Tuegel wrote: > Profpatsch <m...@profpatsch.de> writes: > > On 17-02-23 12:45pm, Thomas Tuegel wrote: > >> The next version of cabal-install will perform this caching for you > >> automatically. It uses your shell.nix (if present) and a

[Nix-commits] [NixOS/nixpkgs] e1656b: git-dit: init at 0.1.0

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e1656bc46da6c2001cfb992735a7daeb75f00bc0 https://github.com/NixOS/nixpkgs/commit/e1656bc46da6c2001cfb992735a7daeb75f00bc0 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-25 (Sat, 25 Fe

[Nix-commits] [NixOS/nixpkgs] 8e54fc: flpsed: ghostscript patch, fixes, new url

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 8e54fced988e4227c34bfc21417ac41eda4448c6 https://github.com/NixOS/nixpkgs/commit/8e54fced988e4227c34bfc21417ac41eda4448c6 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-23 (Thu, 23 Fe

[Nix-commits] [NixOS/nixpkgs] 5b2a71: droopy: init at 20160830 (#22499)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5b2a71fa250926010e6da0a6c6325dc1270770c1 https://github.com/NixOS/nixpkgs/commit/5b2a71fa250926010e6da0a6c6325dc1270770c1 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-11 (Sat, 11 Fe

Re: [Nix-dev] Python 3 as default

On 17-02-14 01:18pm, Peter Simons wrote: > I hardly ever use nix-shell and I don't want to, to > be honest Completely off-discussion: Why is that? Convenience? nix-shell does too many strange things? Personally I use nix-shell for nearly everything I do nowadays because it’s so convenient. Even

[Nix-commits] [NixOS/nixpkgs] ed8a0d: modules/searx: add package option (#22636)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: ed8a0d8e5e1b1de29db72373471b201b69865812 https://github.com/NixOS/nixpkgs/commit/ed8a0d8e5e1b1de29db72373471b201b69865812 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-10 (Fri, 10 Fe

[Nix-commits] [NixOS/nixpkgs] 91d026: modules/filesystems: disallow non-empty fstab fiel...

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 91d0260feba50b25b13d1e0dd2705039f75e09a2 https://github.com/NixOS/nixpkgs/commit/91d0260feba50b25b13d1e0dd2705039f75e09a2 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-15 (Wed, 15 Fe

[Nix-commits] [NixOS/nixpkgs] 7ee777: picard: 1.32. -> 1.4

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 7ee777d784de06a088c5ec933bfb2383c7001d1f https://github.com/NixOS/nixpkgs/commit/7ee777d784de06a088c5ec933bfb2383c7001d1f Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-15 (Wed, 15 Fe

Re: [Nix-dev] Python 3 as default

On 17-02-13 10:08am, Freddy Rietdijk wrote: > In any case, I would like to merge this as soon as possible. Any objections? +1 go for it; Good work! progress is breakage is progress \o/ -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A:

Re: [Nix-dev] Explicitly selecting sources for "src" in stdenv.mkDerivation?

On 17-02-16 01:28pm, Freddy Rietdijk wrote: > > src = [ ./subproject-A/schema.sql ./subproject-A/lib ]; > > Each of the files you mentioned here will be stored in a separate store > path. You could write a simple function that takes a list of derivations > and copies the contents of those

[Nix-commits] [NixOS/nixpkgs] 9debda: networking.bonds: add support for arbitrary driver...

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9debdaf512bc510f7f5d5450c4902e7d1f713274 https://github.com/NixOS/nixpkgs/commit/9debdaf512bc510f7f5d5450c4902e7d1f713274 Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-16 (Thu, 16 Fe

Re: [Nix-dev] nix-shell pro/con (was: Python 3 as default)

On 17-02-15 09:10pm, Ricardo M. Correia wrote: > Personally, I try to avoid using "nix-shell" as much as possible because I > want "nixos-rebuild switch" to atomically install (and upgrade) all the > software that I usually need, including development packages. > > With nix-shell, I risk having

[Nix-commits] [NixOS/nixpkgs] 21cdf3: pythonPackages: use a more direct mirror (#22833)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba https://github.com/NixOS/nixpkgs/commit/21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba Author: Profpatsch <m...@profpatsch.de> Date: 2017-02-15 (Wed, 15 Fe

[Nix-dev] Add @goetzst to maintainers

I suggest adding https://github.com/goetzst to nixpkgs. He is very thoroughly managing youtube-dl and probably some other packages. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read your message.

Re: [Nix-dev] Is it possible to limit nix access to sudoers and/or a group?

On 17-01-20 10:59am, Danylo Hlynskyi wrote: > Nix design doesn't support quotas on filled store per-user, and let's not > forget #8. https://github.com/NixOS/nixpkgs/pull/8 ? That looks unrelated. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A:

Re: [Nix-dev] Trying to install the SailfishOS SDK

On 17-01-19 09:13pm, Christoph-Simon Senjak wrote: > I get the error message > > Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: > Assertion `needed != NULL' failed! > > Any ideas what I could do about that? I am not sure, but have you tried a search, like:

Re: [Nix-dev] infinite recursion on newer nixpkgs

On 16-08-04 09:52pm, Sergey Mironov wrote: > Hi. > I've updated my nixpkgs up to 8983df7 and faced an infinite recursion > on the following peace of config: > > services = pkgs.lib.mkIf config.services.postgresql.enable { > postgresql.initialScript = pkgs.writeText "postgreinit.sql" '' >

Re: [Nix-dev] Best Practices on Modularizing Configuration.nix?

ne config in our vuizvui repo: I have a folder for my personal machines, with a lib.nix and pkgs.nix; these are included as attrsets with `import` https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L4 My config for workstation/se

Re: [Nix-dev] "Consider the Maintainer"

On 17-02-18 10:58pm, Graham Christensen wrote: > Linux.conf.au had this great talk called "Consider the Maintainer" about > being a software maintainer, and managing open source projects. I'd > encourage you all to watch it: > > https://www.youtube.com/watch?v=W2AR1owg0ao There’s also a talk

Re: [Nix-dev] Switch to dead TTY after nixos-rebuild switch succeeded?

On 16-08-31 04:48pm, zimbatm wrote: > Nothing much to add but same thing is happening here. This has been happening for a while now (~1 month). -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://five.sentenc.es May take up to five days to read

[Nix-commits] [NixOS/nixpkgs] e1e96a: youtube-dl: wrap with atomicparsley (#18066)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e1e96a8210cb753b8ea345146a46db3269147e72 https://github.com/NixOS/nixpkgs/commit/e1e96a8210cb753b8ea345146a46db3269147e72 Author: Profpatsch <m...@profpatsch.de> Date: 2016-08-30 (Tue, 30 Au

Re: [Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

On 16-09-03 07:24am, Shea Levy wrote: > Any other ideas that might be useful here? The nixpkgs-side is one dimension to what maintainers have to do, but what I’m stubling upon is the update-information-side. If I’m set as maintainer for a package, what are the best ways to get informed when new

Re: [Nix-dev] hydra.cryp.to will go offline by the end of this year

On 16-09-07 11:50am, Peter Simons wrote: > Fellow Haskell hackers, > > some of you rely on hydra.cryp.to as a source of binary packages for the > Haskell subset of Nixpkgs. Unfortunately, this service will go offline > in December 2016. I've run that machine mostly for my own private > purposes,

[Nix-commits] [NixOS/nixpkgs] 513146: searx: 0.9.0 -> 0.10.0 (#18608)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 51314631d6ee153dab70d99f7a08f04a89d23c5e https://github.com/NixOS/nixpkgs/commit/51314631d6ee153dab70d99f7a08f04a89d23c5e Author: Profpatsch <m...@profpatsch.de> Date: 2016-09-15 (Thu, 15 Se

[Nix-commits] [NixOS/nixpkgs] 67bec7: brogue: fix crash by stackprotector hardening (#18...

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 67bec77c68259166ba9e23921a0cec3af3ec7298 https://github.com/NixOS/nixpkgs/commit/67bec77c68259166ba9e23921a0cec3af3ec7298 Author: Profpatsch <m...@profpatsch.de> Date: 2016-09-24 (Sat, 24 Se

  1   2   3   >