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
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
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
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
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,
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
@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.
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
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
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
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
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
<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
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
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
>>
--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
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
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
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.
>
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
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
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
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,
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!
>>
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
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
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
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
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
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.
>>
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
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
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
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
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)
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)
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 &
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
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
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
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
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…
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
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
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
201 - 252 of 252 matches
Mail list logo