I'd like to have Node 8 in 17.03, is there any reason why we shouldn't do
that?
It would be a non-default attribute, like in master, so the only impact
would be on Hydra I suppose.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Nice! Why is it not perfect?
On Fri, Jun 16, 2017 at 1:21 PM Harmen wrote:
> Hi all,
>
> I while ago here I asked about using nix with drone.io (a CI system which
> uses docker), to deal with push based tests. I previously reported back
> with a solution with gitlab, but I did
Note, sharing /nix is already not really possible because the metadata is
stored in sqlite and its locking does not play nice with nfs. (*)
Another issue is that right now, nix does not /require/ the daemon to work,
and this proposal would change that.
However, you can totally share /nix between
This actually ties into my question about nodePackages. It seems to me that
for these large packaging systems, we should have separate repos that
update from their source, and you can then include them into your nixpkgs
configuration.
Only packages that are useful by themselves should get a
Hi,
I understand that there have been some changes that make Nixpkgs more
overridable.
Could anybody explain how to override the nodePackages derivations so I can
use the most recent versions? Node packages update much faster than
Nixpkgs/Hydra can follow, and compiling them is trivial…
ment.
> After reading the description of your issue I was left under an impression
> that you somehow managed to make it work without reconfiguring nix-daemon.
> Am I wrong?
>
> Without nix-daemon I don’t think there are any problems as of today.
>
>
> On Sat, May 27, 2017 at 9:08 PM
The problem is probably ssh-ing into the VM it should be using for
building. This probably fails due to not having the correct environment,
and then it silently decides building on OSX.
On Fri, May 26, 2017, 12:39 PM Kirill Elagin wrote:
> Hi,
>
> I have finally switched my
Very cool!
On Sat, Apr 22, 2017, 8:55 AM Linus Heckemann wrote:
> On 22/04/17 07:45, Linus Heckemann wrote:
> > On 22/04/17 07:03, Danylo Hlynskyi wrote:
> >> Great!
> >> A question: what does it mean when expression is in round parents?
> >>
> >> (wineUnstable.out)
Woohoo! Thanks everyone!!
(sorry for the noise but could not let this one go by)
On Fri, Mar 31, 2017, 4:29 PM Robin Gloster wrote:
> Dear community,
>
> I'm proud to announce the 7th NixOS stable release 17.03 named
> "Gorilla".
>
> With over 12479 (last release: 13283)
Yes I tried to convince the ML that prelinking /nix/store is sort of
deterministic, but could not get traction. IIRC there is a decent startup
improvement.
OS X does it well, there the dyld automatically does prelinking on the fly,
storing the metadata elsewhere.
On Tue, Mar 21, 2017, 7:36 PM
My $0.02:
* The bikeshedding in NixOS is indeed terrible; in nixpkgs a bit less
* It is hard to abstract over systemd, it has a huge scope. Simply using
runit means also adding a bunch of other services. This impacts all of
NixOS but nothing in nixpkgs.
* Agreed that we should make github
Hi all,
now that we got these wonderful overlays as a Chrismas gift (
http://lists.science.uu.nl/pipermail/nix-dev/2016-December/022386.html), I
was wondering if we can move some things out of nixpkgs into their own
repos.
There are a few package groups that I believe are not used in NixOS core
hanged paths:
M pkgs/development/libraries/sqlite/default.nix
Log Message:
---
sqlite: 3.16.2 -> 3.17.0
Commit: 9ed232b73041ebf7d82ba5b1a79ea4bba6aad857
https://github.com/NixOS/nixpkgs/commit/9ed232b73041ebf7d82ba5b1a79ea4bba6aad857
Author: Wout Mertens &
Maybe it's something else?
https://www.clearos.com/clearfoundation/social/community/solved-nfs-causing-high-load
To further troubleshoot, I'd look into NFS logging to see what is being
read/written, and snooping network traffic might be a quick way into that.
Maybe in the new versions one of the
for devices during resumption attempt
Also a microimprovement -- use `test -n` instead of `test -e`
since we have already checked that the file exists.
Commit: db8401f6036e0ea840c2baba299897151a2944f7
https://github.com/NixOS/nixpkgs/commit/db8401f6036e0ea840c2baba299897151a2944f7
Au
Ok fair enough, so no auto-closing but a 6 month reminder would be good.
Anybody up for C4?
On Tue, Jul 26, 2016, 9:18 PM Vladimír Čunát wrote:
> On 07/24/2016 01:32 PM, Matthias Beyer wrote:
> > As far as I remember, this was over a year ago and they told me
> > (again,
xpkgs/commit/62d11a6961fdae096de947f4971d078159f7b218
Author: Wout Mertens <wout.mert...@gmail.com>
Date: 2016-07-26 (Tue, 26 Jul 2016)
Changed paths:
M nixos/modules/programs/ssmtp.nix
Log Message:
---
Merge pull request #17206 from nathan-gs/patch-2
Fix #9759 SSMT
nsole output.
The only difference here -- it will not replace user configs.
This also fixes https://github.com/NixOS/nixpkgs/issues/16978.
Commit: 3bb18c68d2b767e53f3f9d90b310ede145315726
https://github.com/NixOS/nixpkgs/commit/3bb18c68d2b767e53f3f9d90b310ede145315726
Author: Wout Mertens <wo
t;m...@profpatsch.de> wrote:
> On 16-07-23 09:49am, Wout Mertens wrote:
> > To better triage issues, it would be good to have labels that indicate
> the
> > skillset needed to work the issue.
>
> Not only triaging, but also finding people interested in certain topics.
To better triage issues, it would be good to have labels that indicate the
skillset needed to work the issue. Here's a preliminary list, what is
missing?
- shell
- javascript
- python
- haskell
- ruby
- erlang
- c/c++
- vim
- emacs
- build toolchain
- darwin
- *Splitting the repo*: Indeed, losing history is bad, so no go. See
below for alternative.
- *Triage*: Good ideas to split the load. See below.
- *Autoclose*: Still convinced we should use it. See below.
For *triage*, we can indeed triage by section (just add labels) and then
Ok, how about this: We split nixpkgs in nixpkgs-core and nixpkgs-community
For any package or service, there need to be at least 3 active maintainers,
or it goes out of nixpkgs-core into a nixpkgs-community repo.
Hydra builds nixos from nixpkgs-core, and nixpkgs from both combined.
nixpgks-core
Will people need to constantly comment with `+1` just to reopen?
> Also if an issue is closed it may increase the number of duplicate issues,
> instead of adding onto the closed issue.
>
> On 22/07/2016 7:37 PM, Wout Mertens wrote:
>
> That's the thing about auto-reopening,
To give you an idea, there are still 109 issues that were updated in the
last 2 weeks:
https://github.com/NixOS/nixpkgs/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20%20updated%3A%3E%3D2016-07-08
This is already quite enough to work on.
On Fri, Jul 22, 2016 at 11:37 AM Wout Mertens <wout.m
22, 2016 at 10:15 AM Eelco Dolstra <
> eelco.dols...@logicblox.com> wrote:
>
>> Hi,
>>
>> On 07/22/2016 09:06 AM, Wout Mertens wrote:
>>
>> > We have 1238 open issues and 286 open PRs.
>> >
>> > That is just too much to reason about.
>>
gs/commit/434f9d158bbf3629a653b7d05abef450ea5273d5
Author: Wout Mertens <wout.mert...@gmail.com>
Date: 2016-07-22 (Fri, 22 Jul 2016)
Changed paths:
M pkgs/development/web/nodejs/nodejs.nix
M pkgs/development/web/nodejs/v6.nix
Log Message:
---
Merge pull request #17169 from holidaycheck/nodej
We have 1238 open issues and 286 open PRs.
That is just too much to reason about.
How about using something like https://github.com/twbs/no-carrier which
auto-closes after 14 days of inactivity, and reopens on a new comment?
I'm sure that if we have close to 0 open issues/PRs, there will be a
How about: name this new one npm2nix_2 and make it the default. If you want
the old one, instal npm2nix_1.
On Thu, Jul 14, 2016 at 1:19 PM Tomasz Czyż <tomasz.c...@gmail.com> wrote:
> 2016-07-13 22:13 GMT+01:00 Wout Mertens <wout.mert...@gmail.com>:
>
>> Great!
>>
Great!
I tried npm2nix a few times and never really got it to work. I can't
imagine that there are a lot of people that use npm2nix that would not be
able to switch to your new version if it got added as npm2nix.
Having multiple solutions for the same thing is a frustrating experience
for people
ixpkgs/commit/5bf4fd7a63bb0ec0ef8036a6880c3a310f7a5a3e
Author: Wout Mertens <wout.mert...@gmail.com>
Date: 2016-07-09 (Sat, 09 Jul 2016)
Changed paths:
M pkgs/applications/video/handbrake/default.nix
Log Message:
---
Merge pull request #16810 from rycee/fix/handbrak
config files in four separate places within the target packages. This
commit updates the docstring to reflect the actual implementation
behaviour.
Commit: 69df7b63ff6b20390fa177df6ed6357f192e34eb
https://github.com/NixOS/nixpkgs/commit/69df7b63ff6b20390fa177df6ed6357f192e34eb
Author
n 2016)
Changed paths:
M pkgs/applications/misc/makeself/default.nix
Log Message:
---
makeself: header wasn't being patched correctly
Commit: 3bbdfe5df7693b01b35365a0796bb4e29f425167
https://github.com/NixOS/nixpkgs/commit/3bbdfe5df7693b01b35365a0796bb4e29f425167
Author
--suffix-flags sounds ok, but perhaps a custom wrapper is better.
On Sun, May 8, 2016, 11:02 AM Philip Carlsen wrote:
> That's great to hear - Indeed you're not the only one having trouble with
> akonadi. I just gave up before I could make anything useful of it.
> Den 8. maj
Woah I love that! +1, I don't see why we can't do that…
Wout.
On Wed, Apr 20, 2016 at 1:52 PM Silvio Frischknecht wrote:
> Hello,
>
> I recently found out that if you set the SONAME of a library to an
> absolute path.
>
> gcc --shared -Wl,-soname="$(pwd)/libxyz.so" -o libxyz.so
The expressions are evaluated from the coordinator, so either you upgrade
the channel there or you check out nixpkgs somewhere and set
`NIX_PATH=nixpkgs=/path/to/your/clone` before running nixops.
On Wed, Apr 20, 2016 at 1:52 PM Teo Klestrup wrote:
> I believe the channels are
I thought this would be interesting for some people on this list:
http://gugel.io/ied/ :
Under the hood, ied maintains an "object database", similar to git. Instead
of storing packages by some arbitrary name, a SHA1-checksum is being
generated to approximate their contents. The checksums can not
BTW, that reminds me of https://github.com/NixOS/nixpkgs/issues/12898
On Tue, Apr 19, 2016 at 12:50 PM Wout Mertens <wout.mert...@gmail.com>
wrote:
> Thanks, that really helps!
>
> On Tue, Apr 19, 2016 at 12:21 PM Layus <layus...@gmail.com> wrote:
>
>> On 19/0
Thanks, that really helps!
On Tue, Apr 19, 2016 at 12:21 PM Layus <layus...@gmail.com> wrote:
> On 19/04/16 11:52, Wout Mertens wrote:
> > Hi,
> >
> > I would like to make a specialized image that just runs some tools and
> > has nothing else installed.
>
Nix on other systems has problems, and https://github.com/NixOS/nix/pull/452
is an attempt to solve some of those.
However, it has been sittin in PR limbo for over a year. Is Eelco not
aware, or too busy? Anything I can do to help?
To me, Nix on other OSes is a "gateway drug" to NixOS, so I
That one requires action on the part of the user, unlike the newfangled
group chat tools, but ok.
On Tue, Mar 8, 2016 at 3:16 PM Herwig Hochleitner <hhochleit...@gmail.com>
wrote:
> 2016-03-08 15:11 GMT+01:00 Wout Mertens <wout.mert...@gmail.com>:
>
>> ok, then how about
<nixp...@noreply.github.com>
Cc: Wout Mertens <wout.mert...@gmail.com>
nix-env -qa '*' |grep myspell
myspell-dict-he-1.1
myspell-dict-he-1.1
I don't know hebrew :(
On ubuntu, installing libreoffice and myspell-en-gb and possibly
libreoffice-l10n-uk worked.
Removing libreoffice and installi
t;
> Picking the tool is about engineering tradeoffs. Right now, IRC is optimal
> given optimization parameters, starting from not sharding the community,
> going through network resilience and system's fault tolerance, ending with
> the degree of democracy IRC provides.
> On M
Great job Sander!
Some thoughts:
- Node 5 layout is Node 4 compatible, so why not use only that?
- You can symlink the first level of modules instead of the modules
themselves to avoid the commonjs derefence thing. So a combination of
modules becomes a shallow copy.
- npm2nix
After having used Slack and Discord for a while, I can tell you that having
the recent chat log available with a quick scroll up is very handy.
Conversations can continue over a longer period of time.
With IRC, you have to open your client, fire off your question a few times
and hope that someone
Help on https://github.com/madjar/nox/issues/38 is appreciated methinks :-)
On Wed, Mar 2, 2016, 2:46 AM Herwig Hochleitner
wrote:
> 2016-02-14 19:44 GMT+01:00 zimbatm :
>
>> What if master was always the latest successful hydra build ? People
>>
Check it out: http://www.mattermost.org/
Any chance of using that instead of/in addition to IRC?
Wout.
--
Wout.
(typed on mobile, excuse terseness)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Now if we could run a query for that… :-)
On Sat, Feb 20, 2016, 10:26 AM Michael Raskin <7c6f4...@mail.ru> wrote:
> >Same for PRs, we have some really old ones. What is a good cutoff? 6
> months?
>
> I would start with «6 months without any updates except non-submitter
> pings and the submitter
Same for PRs, we have some really old ones. What is a good cutoff? 6 months?
On Thu, Feb 18, 2016, 7:50 PM Profpatsch wrote:
> 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
@copumpkin?
Is there anybody able to build v8 on Darwin (apart from the fact that you
need to turn on allowBroken because its platforms are set to linux)?
I'm getting
...
ACTION Generating icuuc shim headers.
The problem with nfs nix stores is that the metadata is stored in sqlite,
which can't guarantee proper locking on nfs. However, if you only write
from one host, there is no problem.
As for the python stuff, you can run it in a proot, or use nixos which
doesn't have /usr :-)
On Mon, Feb 8, 2016,
Sadly, I always build npm packages locally with a user created for the app.
Npm2nix is not usable yet afaik (I'd love to be wrong).
Last I saw, someone was proposing for it to piggyback on `npm shrinkwrap`,
which I think would be the way to go for determining version numbers. Worst
case, the
I looked into what would be needed to have multiple writers on the same
store here: https://github.com/NixOS/nix/issues/378#issuecomment-62724778
The same would apply for aufs-type multi writer setups.
The tl;dr is that Nix would need to treat sqlite as only a cache, with all
needed info written
net> wrote:
> On Sat, 26 Dec 2015 09:07:38 +0000,
> Wout Mertens wrote:
> > If web-of-trust is the best solution, and the only blocker is build
> reproducability, how about trying to classify
> > build differences?
> >
> > Each of the differences will have a re
If web-of-trust is the best solution, and the only blocker is build
reproducability, how about trying to classify build differences?
Each of the differences will have a reason, and either we can fix the build
to be deterministic (e.g. timestamps, build paths), or we can classify a
class of
¯\_(ツ)_/¯ good luck I'd say :)
On Sun, Dec 20, 2015 at 10:45 AM Matthias Beyer <m...@beyermatthias.de>
wrote:
> No.
>
> I need a way to describe debian/centos VM ISO images with Nix. Not
> more, not less.
>
> On 19-12-2015 23:01:22, Wout Mertens wrote:
> > So
So basically you need a frontend that creates .nix files for profs and a vm
image with all binaries for everything already on it?
On Sat, Dec 19, 2015 at 4:34 PM Matthias Beyer
wrote:
> On 11-12-2015 15:56:00, Marc Weber wrote:
> >
> > But serausly, if the profs need
https://blog.scaleway.com/2015/11/03/scaleway-is-growing-too-fast-out-of-stock/
:-)
On Fri, Nov 6, 2015 at 10:16 PM Hajo Möller wrote:
> Also, https://www.kimsufi.com may be worth checking out. I'm running
> 15.09 on a KS-1 and a KS-5.
>
> A KS-1 is amd64 and can be had for 5
http://techcrunch.com/2015/09/02/scaleway-now-provides-crazy-cheap-virtual-private-servers-starting-at-3-40-per-month/
It's a dedicated quad-core ARM server, and you even get 200Mb/s networking.
Has anybody tried to get NixOS running on these? Seems like this would be
amazing for web servers…
+1000 on just switching, pure-darwin rocks, impure has constant issues and
we need more eyeballs.
In case of severe breakage we can keep a non-building channel on impure so
people can get at the old binaries…
On Fri, Oct 2, 2015, 18:10 zimbatm wrote:
> Looking forward to
Hi all,
see
https://github.com/NixOS/nixpkgs/commit/9d82f7e53e66e5594b0c8b82f6c415a0a386b580
which
reverts a site-wide optional compression feature I added. The discussion
and lack of answering can be found at
https://github.com/NixOS/nixpkgs/pull/9407#issuecomment-134523359.
IMHO, configuring
nd i would like to have this as a nix
>> option as well! but eelco might be right as this should be a per vhost
>> option but i'm not sure about that.
>>
>> +1
>>
>> On 12.09.2015 11:05, Wout Mertens wrote:
>> > Hi all,
>> >
>> >
I don't use Nix on Windows but wanted to say the technical report was very
interesting!
One thing that stood out was that using bash was much slower than using
sed, is that change now on Linux as well? Just wondering...
Wout.
On Tue, Sep 8, 2015 at 1:15 PM Florian Friesdorf
Wout Mertens <wout.mert...@gmail.com> wrote:
> Well, what I mean is that there could be some bug in Node that is
> triggered... So using a diffferent Node might fix it.
>
> On Sun, Sep 6, 2015 at 7:12 PM Domen Kožar <do...@dev.si> wrote:
>
>> It's using bundled n
pt libraries tried to compile with native code and
> fails. But why does it succeed for some people but not for others?
>
> On Sun, Sep 6, 2015 at 7:10 PM, Wout Mertens <wout.mert...@gmail.com>
> wrote:
>
>> Shot in the dark: did you try varying nodejs versions?
>>
Good luck on your trip, sounds like fun! Unfortunately the Donau doesn't
pass Warsaw, otherwise, welcome!
On Mon, Jul 13, 2015 at 12:56 AM Joachim Schiele j...@lastlog.de wrote:
if you come near tübingen (where i live) or balingen let me know.
would be nice meeting you
On 07.07.2015 20:57,
Two approaches:
- Look through all the commits between your working system and your
broken system, finding anything related to boot, initrd or luks
- Mount the old and new initrds and compare contents
(I don't really know how luks works, I presume it runs in the initrd to
mount root)
Oh wow I never saw that before, and in a Perl script no less.
I think you may have memory corruption? Does memtest86 work fine?
Wout.
On Sat, May 16, 2015, 2:59 PM Amy de Buitléir a...@nualeargais.ie wrote:
Sigh... new problem:
[root@wombat9000:~]# nixos-rebuild switch
building Nix...
Of course, it can only be memory corruption if it is not repeatable,
otherwise there's something weird about the call Perl makes to syswrite(),
definitely a bug somewhere then.
On Sat, May 16, 2015, 3:03 PM Wout Mertens wout.mert...@gmail.com wrote:
Oh wow I never saw that before, and in a Perl
Well, that looks like hardware corruption somewhere. Might I recommend
using zfs or btrfs as your filesystem to ensure integrity?
On Sat, May 16, 2015, 4:58 PM Amy de Buitléir a...@nualeargais.ie wrote:
Wout Mertens wout.mertens at gmail.com writes:
so weird... what was the corruption
There are a few dependencies in nixos that are hidden from nix as to not
have to recompile the world when they change.
The instances I know of are the timezone files and CA certificates but
there's probably more. The timezone files expect TZDIR to be set, and all
programs are being compiled to
That's really a question about Unix in general, not just NixOS.
Basically, there are several (a lot) of input methods, but you can cover a
lot of them by setting up ~/.inputrc and xkb.
See:
- http://www.gnu.org/software/bash/manual/html_node/Sample-Init-File.html
-
Yeah, Charles seems to be AWOL for a bit, it would be nice if he merged my
PR... Charles?
Wout.
On Tue, May 12, 2015 at 4:30 PM Christian Theune c...@flyingcircus.io wrote:
On 12 May 2015, at 16:19, Christian Theune c...@flyingcircus.io wrote:
On 12 May 2015, at 16:11, Christian Theune
The build could run a quick check to see if ssh-keygen can read the
file? `ssh-keygen
-l -f filename` will return an error if it can't read a key in the file (it
only checks the first key)
On Tue, May 12, 2015 at 10:33 AM Christian Theune c...@flyingcircus.io
wrote:
Hi,
correct me if I’m
Please, install this extension on the NixOS Wiki:
http://www.mediawiki.org/wiki/Extension:BacktickCode
Thanks!
Wout.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Hi,
Our current stable is 3.14, our latest is 3.15, and on kernel.org the
latest longterm is 3.18.13 and stable is 4.0.2.
Is there a reason beyond manpower why we're not going with 3.18 for the
stable release and latest isn't 4.0?
Wout.
___
nix-dev
On Thu, May 7, 2015 at 8:32 AM, Wout Mertens wout.mert...@gmail.com
wrote:
Hi,
Our current stable is 3.14, our latest is 3.15, and on kernel.org the
latest longterm is 3.18.13 and stable is 4.0.2.
Is there a reason beyond manpower why we're not going with 3.18 for the
stable release
all-packages.nix is gigantic, and because it's so large, github search
doesn't index it.
Would it be a good idea to move the attribute definitions into files per
package section?
So everything would still be in the pkgs attrset, only the definitions
would be split across multiple files.
readDir. If not, it seems
like the majority of packages could work that way, along with room to
override where necessary.
On May 7, 2015, at 08:10, Wout Mertens wout.mert...@gmail.com wrote:
all-packages.nix is gigantic, and because it's so large, github search
doesn't index it.
Would
yes indeed that looks nice, it would eliminate some 3855 lines of 9351
non-empty lines... With more probably a small refactor away.
On Thu, May 7, 2015 at 3:08 PM Daniel Peebles pumpkin...@gmail.com wrote:
What went wrong? I think that's what I was thinking of
On May 7, 2015, at 08:50,
well, that traversal could be automated at commit time? It's just an
optimization...
On Thu, May 7, 2015 at 3:24 PM Eelco Dolstra eelco.dols...@logicblox.com
wrote:
Hi,
On 07/05/15 15:02, Daniel Peebles wrote:
No need to read all the files, right? You import them lazily based on
what
https://github.com/cstrahan/nix-packer/pull/14 makes it build a 14.12 image
On Tue, Apr 28, 2015 at 12:33 PM Domen Kožar do...@dev.si wrote:
I'd send emails to both authors asking if they plan to update the images :)
On Tue, Apr 28, 2015 at 9:45 AM, Rok Garbas r...@garbas.si wrote:
Quoting
Hi all,
Vultr is a cheap hosting provider (like digital ocean), and they allow iPXE
booting:
https://www.vultr.com/docs/ipxe-boot-feature
Does anybody have experience with this? It seems to me that you'd be able
to provide a minimal configuration in a query string and have the VM boot
an install
as I’ve been around we’ve also accepted patches via ML, why not?
On Apr 28, 2015, at 2:34 AM, Wout Mertens wout.mert...@gmail.com
wrote:
These patches look useful, but normally we work via github...
On Tue, Apr 28, 2015, 4:17 AM Jookia 166...@gmail.com wrote:
When bootstrapping from other
These patches look useful, but normally we work via github...
On Tue, Apr 28, 2015, 4:17 AM Jookia 166...@gmail.com wrote:
When bootstrapping from other distributions, nixos-install is unable to
find
various tools in the chroot since their paths aren't aware of NixOS
conventions.
This
I opened https://github.com/NixOS/nix/issues/377 a while ago and then I ran
some small tests and it didn't seem to matter. The links dir is of course
huge but it still performs fine on sane filesystems. IIRC, the only time
you do readdir on it is during GC to remove the ones with 1 link count.
I suppose we didn't really keep up with documenting important changes at
https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-unstable.xml
?
How shall we find all the breaking changes and highlights? Someone eyeballs
all commits, or we do a call for important changes
Yes, no problem.
On Tue, Mar 24, 2015, 9:34 PM Arseniy Seroka ars.ser...@gmail.com wrote:
Using nixos-unstable-small I have to build locally lots of pkgs :(
But can I mix nixpkgs-unstable and nixos-unstable? Using the first one
for nix-env and the second one for sudo nixos-rebuild?
My vote is to remove merged branches without historical significance
(version 0.5 is a keeper, like upstart), and then any branches that got
their last push before August 2014 are renamed to attic/...
That should make the github interface easier to navigate.
, yes, that's a good point. Filesystems with fancy things like
reflinks probably have their own tools for deduplication.
On 15 February 2015 at 01:48, Wout Mertens wout.mert...@gmail.com
wrote:
If you want to use reflinks, better to use the deduplication tools that
come
with the filesystem
If you want to use reflinks, better to use the deduplication tools that
come with the filesystem, e.g.
https://btrfs.wiki.kernel.org/index.php/Deduplication (duperemove is in
nixpkgs).
Also, it would be nice if we could patch GNU cp so that it always tries to
use reflinks (so that builds
Weird - what branch are you on? Anything special in you configuration.nix?
Sounds like a bug somewhere but could be anything. I have no idea what
causes that connection timed out for the session creation if it's not DNS.
You could try picking a different nixpkgs commit and see if your system is
Well, after you forked the nixbox repo you didn't change anything that
would impact DNS resolution, so there must be an issue with something in
NixOS. Did you try building with 14.04 to confirm that it worked at some
point?
I think the least-effort way forward is doing a bisection, trying to
On Fri Feb 13 2015 at 3:27:19 PM Vladimír Čunát vcu...@gmail.com wrote:
On 02/13/2015 12:10 PM, Wout Mertens wrote:
So it's hard to say what the effect is generally, but the disk space
saving is definitely there. If you are worried about seek times, you
might want to turn on filesystem
linking also happen if you use nix-copy-closure?
Rich
On Thu, Feb 12, 2015 at 3:47 AM, Wout Mertens wout.mert...@gmail.com
wrote:
Hi all,
(TL;DR: regain disk space, see at the bottom for instructions)
the Nix store can be optimised by hard-linking files with the same
contents together, so
Hi all,
(TL;DR: regain disk space, see at the bottom for instructions)
the Nix store can be optimised by hard-linking files with the same contents
together, so they are only stored once. This is done by reading all the
files in your store, calculating their checksums and linking them to
Your setting NIX_PATH to `nixpkgs=~/.nix-defexpr/channels/nixpkgs` makes a
lot of sense to me and I wouldn't mind it being the default for users...
In general though the whole home dir setup could use some love. There's
.nix-defexpr/, .nix-channels, .nix-profile@ and .nixpkgs/config.nix, where
it
There's another option : build natively with distcc pointing to
cross-compilers on x86 boxes. All the configuration etc happens natively
and the compiles themselves are sped up. I wonder if that's the approach
Vladimír Čunát took earlier? He made the notes on how to set up distcc for
raspberry pi
Just wondering out loud with probably no actionable change:
Why are the kernel options implemented as strings (FOO y) instead of an
attribute set ({ foo = y: })?
Of course that means you can easily import your own .config file as
described at
rb_enc_raise seems to be a ruby 2.0 thing and you're using 1.9.3. Some
mixup somewhere?
https://bugs.ruby-lang.org/issues/5650 was when it was added to 2.0 3 years
ago...
On Tue Feb 10 2015 at 11:05:56 PM Cillian de Róiste
cillian.deroi...@gmail.com wrote:
2015-02-10 19:25 GMT+01:00 Cillian
I see that the darwin machine butters is online (and idle) in Hydra, does
that mean the zalora cache is no longer needed for nixpkgs on Darwin?
On Tue Feb 03 2015 at 3:51:47 PM Domen Kožar do...@dev.si wrote:
:beers:
On Tue, Feb 3, 2015 at 3:40 PM, Shea Levy s...@shealevy.com wrote:
Hi all,
1 - 100 of 252 matches
Mail list logo