Re: [Nix-dev] Nixos wiki project

[Azul]

+4
On 10 May 2017 07:57, "Mic92"  wrote:

> As the official wiki is now finally part of the history:
> https://nixos.org/nixos/wiki.html,
> we have started our own community wiki:
>
>   https://github.com/nixos-users/wiki/wiki
>
> It is at the moment editable by every GitHub user and
> we use our IRC channel #krebs to review and track changes.
>
> We invite you to dump your knowledge and useful snippets,
> if you found out something cool about Nix/NixOS.
>
> Cheers Mic92.
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] c54529: mesos: 1.1.0 -> 1.1.1

[Azul]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: c545296adc2d2e4c17090e87eeec2d0e872c10d2
  
https://github.com/NixOS/nixpkgs/commit/c545296adc2d2e4c17090e87eeec2d0e872c10d2
  Author: Azul 
  Date:   2017-04-27 (Thu, 27 Apr 2017)

  Changed paths:
M pkgs/applications/networking/cluster/mesos/default.nix

  Log Message:
  ---
  mesos: 1.1.0 -> 1.1.1

(cherry picked from commit de688d90ba981497fb5a8d208351115c5ef7adef)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] de688d: mesos: 1.1.0 -> 1.1.1

[Azul]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: de688d90ba981497fb5a8d208351115c5ef7adef
  
https://github.com/NixOS/nixpkgs/commit/de688d90ba981497fb5a8d208351115c5ef7adef
  Author: Azul 
  Date:   2017-04-27 (Thu, 27 Apr 2017)

  Changed paths:
M pkgs/applications/networking/cluster/mesos/default.nix

  Log Message:
  ---
  mesos: 1.1.0 -> 1.1.1


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] still waiting for https://cache.nixos.org after 5 seconds...

[Azul]

If you have a local proxy you can save yourself a lot of bandwidth (and
nixos.org too) by setting your cache URL to http://



On Apr 20, 2017 10:24 PM, "Daniel Peebles"  wrote:

> It's all just AWS CloudFront. Sometimes there are hiccups in their
> service, but it's not really anything we have control over.
>
> On Thu, Apr 20, 2017 at 5:20 PM, Profpatsch  wrote:
>
>> I have the feeling the nixos caches are getting
>> less and less responsive lately.
>> Often the times are 15s+, and I checked
>> that my local connection is not the reason.
>>
>> Are there reasons for this?
>>
>> --
>> 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, call me.
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>>
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] updating my mesos cluster to 17.03

[Azul]

minor changes related to my own setup but looking good so far.

happy
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] garbage-collection of the last 'n' generations

[Azul]

Hi there,

I would like to cleanup my oldest  'n' nix generations.

nix-collect-garbage seems to only provide me with a older than 'n' days
option.

Any quick hacks to clean everything but keep my recent  'n' generations ?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] how to 'just run binaries' in nixos

[Azul]

thanks all,

*steam-run* just works




On 22 March 2017 at 11:24, Brian McKenna  wrote:

> I have a couple of methods for doing this. I just posted them onto my blog:
>
> https://brianmckenna.org/blog/running_binaries_on_nixos
>
> Hopefully one of them is suitable for you. I'd love to learn if there's
> ways to improve on these.
>
> On 22 March 2017 at 09:41, Azul  wrote:
>
>> is there a simple way to just run binaries in nixos ?
>>
>> stuff like go binaries or other bits and bobs ?
>>
>>
>> ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
>> interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.26
>>
>> ./my-binary
>> bash: ./my-binary: No such file or directory
>>
>>
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] how to 'just run binaries' in nixos

[Azul]

is there a simple way to just run binaries in nixos ?

stuff like go binaries or other bits and bobs ?


ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.26

./my-binary
bash: ./my-binary: No such file or directory
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] where is grep?

[Azul]

I just understood where it all went wrong:

 azul  /safe/home-azul  130  killall ssh
The program ‘killall’ is currently not installed. It is provided by
several packages. You can install it by typing one of the following:
  nix-env -iA nixos.busybox
  nix-env -iA nixos.psmisc



On 15 November 2016 at 13:18, Profpatsch  wrote:

> On 16-11-15 11:14am, Azul wrote:
> > "If you put busybox into your systemPackages, it will likely shadow many
> > other utilities" <-- kaboom, zing, slash, boooOOOmmm
> >
> > killed, gone
>
> There’s also a pretty long list of default packages
> which afaik cannot be shadowed by other
> environment.systemPackages entries:
> https://github.com/NixOS/nixpkgs/blob/master/nixos/
> modules/config/system-path.nix#L10
>
>
> --
> 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, call me.
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Shutting down prs.nix.gsc.io

[Azul]

Wished gmail would default to reply-all



On 2 Feb 2017 6:20 pm, "Thomas Hunger"  wrote:

You replied just to me :)

Hit reply-all if you want to cc the list as well.

On 2 February 2017 at 18:11, Azul  wrote:

> Very happy kimsufi user here.
>
> And with I saved from not using AWS i will put down on the nix foundation.
>
>
> On 2 Feb 2017 10:34 am, "Thomas Hunger"  wrote:
>
> Expensive data transfer out from EC2 is the reason I added digital ocean
> support to nixops. Our company fits into a few TB / month, but for more we
> could use e.g. kimsufi which has 100Mbit / second unmetered for £20-30 /
> month. Their servers also usually come with 2TB or more spinning disks
> which would be good for fitting build outputs.
>
> On 1 February 2017 at 12:38, Graham Christensen 
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>>
>> Hey everyone, :)
>>
>> I am touched by your offers to contribute to help pay for it. I am so
>> thrilled to be part of a community that takes care of its own. It
>> reminds me of this talk: https://www.youtube.com/watch?v=Xe1TZaElTAs.
>>
>> However, please instead take your generosity and perhaps donate to the
>> NixOS Foundation: https://nixos.org/nixos/foundation.html or another
>> worthy cause (up to you to know what that means.)
>>
>> Here is exactly how much the experiment cost:
>>
>> Usage Type| Usage   |  Price| Total
>> 
>> S3 PUT Requests   | 2,066,983   | $0.005/1,000  | $ 10.33
>> S3 GET Requests   | 4,812,149   | $0.004/10,000 | $  1.92
>> S3 Timed Storage  |   603 GB-Mo | $0.023/GB-mo  | $ 13.87
>> Data Transfer In  | 1,907.028 GB| $0/GB | $  0.00
>> Data Transfer Out | 3,698.464 GB| $0.090/GB | $332.86
>> - -
>>   $358.98
>>
>> Thank you so much,
>> Graham Christensen
>> -BEGIN PGP SIGNATURE-
>>
>> iQIcBAEBCAAGBQJYkdbAAAoJEAYSHTZv6UNcTcgP/38I07FjuexTkTIaRnzMawsN
>> My6+IfWWzv+MToaiYLLaj5gMXplrHIuzdUVxq0LXAxqLDQdMbw3txuUai4gglFGS
>> gWss7/3yYEyws0viT0OmWixq3+bDs57bAyC2k6LPt4QzxgFiLeAk1fyk7e2t1n6S
>> 3GOj7HW000kjK7caxqTsKMORrk1WsQ6i1R+XupwJw8NU+0mFvVM/C6B3d5w8lP2S
>> B9x0EcSV63rUh4IAio7EqU99KoJcLmc/HaE9uq4zYTFMhzcV1imV4bj9s+Qq6MQf
>> 7amIu5br7ntBwTWDzdGmiMLbIbSI5IB4hzfDOedkavpWfwfj7EBR9j4cK9PHbo0+
>> PoGR2x10wma6Sa0DrDgmRZx8WJypMXGYbgGZQCxr04wlYMh/hl7z9IhPZ8Z37GXx
>> ote01hRdS82hfWgRIagkBJG9L5MnVqS5WNLHmo4tg2sf7ADPJoXUz7MO/zaGx2Dh
>> dKzPDAA+cLOwcWI+rIoQTOIWTlskyjbJpymoNbhm1MZhqsGK4i+MLwFrDla8k6nh
>> uhWg8lCAwWEJ3QqGRdeW3Pp2+d9KAIAN5QLFRFmW8s8fmLxLdbo2bPr/sw7NSTdk
>> p7ZMJhC6K8bJkCleSxxGSsDvX5icokL0ZaaXVlZcyeZo8/ODQCBfxbC6M57uSrig
>> qhsZ2InUPjQGTJZeozOb
>> =Iu/C
>> -END PGP SIGNATURE-
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] linux-ck kernel config

[Azul]

Anyone here uses a linux-ck patched kernel ?
http://users.tpg.com.au/ckolivas/kernel/

and willing to share their config ?

my laptop tells me he seriously misses that kernel from it's Arch days
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] systemd dependencies for a network service

[Azul]

I have a systemd vpn service that is wantedBy 'network.target', and runs
after 'network-interfaces.target'.

However the service fails to start properly (it does start but not in a
useful way), as it requires DNS resolution to work and that doesn't seem to
be the case after 'network-interfaces.target' is complete.

Scratching my head to find out which of the systemd services provides that
functionality, or if I will have to write a simple service that probes and
waits for dns resolution and use that for my 'after=' systemd property.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] environment.etc.'filename'.owner ?

[Azul]

Is there a way to set the owner and group for a file as per the subject ?

couldn't grep for any example for this.

thanks
azul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] nixos-rebuild using $TMPDIR

[Azul]

thanks,

I ended up getting rid of tmpfs, causes more hassle than what it is worth

On 14 December 2016 at 17:37, Joachim Schiele  wrote:

> On 13.12.2016 16:14, Azul wrote:
> > Hey gang,
> >
> > Trying to do a nixos-rebuild where I added libreoffice to my list of
> > packages failing due to lack of disk space.
> > My /tmp is on tmpfs, so limited in disk space.
> >
> > I tried to set NIX_REMOTE="" and TMPDIR=/var/tmp/ but no joy,
> > nixos-rebuild just tells me to sod off and does its own thing.
> >
> > is there a way to tell nixos-rebuild to use my TMPDIR settings ?
> >
> > azul
>
>
> man nix-build
>
> lets to:
>
>TMPDIR
>Use the specified directory to store temporary files. In
> particular, this includes temporary build directories; these can take up
> substantial amounts of disk space. The default is /tmp.
>
> so:
>
> TMPDIR=/foo nix-build -A whatever
>
> should do the trick
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] nixos-rebuild using $TMPDIR

[Azul]

Hey gang,

Trying to do a nixos-rebuild where I added libreoffice to my list of
packages failing due to lack of disk space.
My /tmp is on tmpfs, so limited in disk space.

I tried to set NIX_REMOTE="" and TMPDIR=/var/tmp/ but no joy, nixos-rebuild
just tells me to sod off and does its own thing.

is there a way to tell nixos-rebuild to use my TMPDIR settings ?

azul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos vps

[Azul]

works on a 2GB 3quid/month OVH kvm instance, only had to rename eth to ens3

uname -a
Linux vps353091 4.4.36 #1-NixOS SMP Fri Dec 2 08:09:18 UTC 2016 x86_64
GNU/Linux

nice one chaps


On 12 December 2016 at 12:06, Azul  wrote:

> thanks all,
>
> as usual lots of really good answers,
>
> nixos-infect wins best github project name of the year !
> that bash code, some cloud-init or libcloud magic is probably enough and
> won't take too long.
>
> - azul
>
> On 12 December 2016 at 11:18, Profpatsch  wrote:
>
>> On 16-12-12 08:36am, Azul wrote:
>> > Now I would like to move those apps to nixos and just have one single
>> set
>> > of code to maintain, for that I just need some cheap vps provider
>> providing
>> > nixos instances.
>>
>> It is possible to “infect” existing distributions with nixos,
>> that is to basically convert them.
>>
>> https://github.com/elitak/nixos-infect
>> The script worked for me on an online.net box provisioned with
>> Arch, by running it, editing the configs that were generated,
>> manually executing the remaining three or four steps and then
>> rebooting.
>>
>> Maybe that helps.
>>
>> --
>> 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, call me.
>>
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos vps

[Azul]

thanks all,

as usual lots of really good answers,

nixos-infect wins best github project name of the year !
that bash code, some cloud-init or libcloud magic is probably enough and
won't take too long.

- azul

On 12 December 2016 at 11:18, Profpatsch  wrote:

> On 16-12-12 08:36am, Azul wrote:
> > Now I would like to move those apps to nixos and just have one single set
> > of code to maintain, for that I just need some cheap vps provider
> providing
> > nixos instances.
>
> It is possible to “infect” existing distributions with nixos,
> that is to basically convert them.
>
> https://github.com/elitak/nixos-infect
> The script worked for me on an online.net box provisioned with
> Arch, by running it, editing the configs that were generated,
> manually executing the remaining three or four steps and then
> rebooting.
>
> Maybe that helps.
>
> --
> 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, call me.
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos vps

[Azul]

Thanks I have used your steps on a kimsufi box, but really looking for
something that gives me nixos out of the box.

On 12 Dec 2016 9:05 am, "Augustin Borsu"  wrote:

> You can install nixos on ovh vps, its just a bit more work since you have
> to do it yourself from the resuce os.
> I documented the process here
> 
> (it might be a bit outdated as I did it over a year ago but so far I
> haven't had a single issue).
> Might not be worth it if you want to deploy multiple server though.
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Nixos vps

[Azul]

Hey there,

I use a set of really cheap OVH vps for a number of clustered apps (consul,
zookeeper and other stuff), however since OVH do not provide a nixos KVM
image I have deployed those on other OSs.
Now I would like to move those apps to nixos and just have one single set
of code to maintain, for that I just need some cheap vps provider providing
nixos instances.

What is out there that you have used ?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] List of companies using NixOS

[Azul]

ADP uses nix on SLES12.3 to deploy the good things that are not available
on suse.


On 20 November 2016 at 18:55, zimbatm  wrote:

> Hi all,
>
> I am collecting a list of companies that are using NixOS. The idea is to
> encourage adoption by validation.
>
> The list is over here:
> https://www.reddit.com/r/NixOS/comments/5dz8fp/list_of_
> companies_using_nixos/
>
> If you don't feel like posting on Reddit just post here and I'll add them
> over there.
>
> Cheers,
> z
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Put a cow in your iPhone with nix!

[Azul]

I used to run OSX builds using vagrant on a soyoustart box. However that
breaks the EULA, but we didnt care as a farm of mac minis wasnt really an
option.

On 21 Nov 2016 9:46 am, "Raahul Kumar"  wrote:

> Is there a way to get rid of the OS X box? Would Darling work, or a an OS
> X image in Virtual Box?
>
> https://www.darlinghq.org/project-status/
>
>
> On Sun, Nov 20, 2016 at 1:26 AM, Shea Levy  wrote:
>
>> Hi all,
>>
>> Leveraging the recent haskell cross-compilation and iOS
>> cross-compilation I've added to nixpkgs, you can now get a cow to talk
>> to you from your iPhone with nix! Check out the repo [1] and run
>> ./run-cow-in-sim.sh to get a simulation of this experience right from
>> your OS X box with the iPhoneSimulator 10.0 SDK (bundled with latest
>> xcode as of this writing)!
>>
>> Thanks,
>> Shea
>>
>> [1] https://github.com/shlevy/cowsay-haskell
>>
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] where is grep?

[Azul]

"If you put busybox into your systemPackages, it will likely shadow many
other utilities" <-- kaboom, zing, slash, boooOOOmmm

killed, gone



On 14 November 2016 at 20:55, Vladimír Čunát  wrote:

> On 11/14/2016 08:49 PM, Azul wrote:
> > some large refactoring left me with this one,
> >
> > /run/current-system/sw/bin/grep
> > grep: unrecognized option '--color=auto'
> > BusyBox v1.24.2 () multi-call binary.
> >
> > grep is coming from busybox,
> > which package provides the real thing?
>
> If you put busybox into your systemPackages, it will likely shadow many
> other utilities as well, so in your place I'd rather remove it (or used
> a version without those symlinks).
>
> --Vladimir
>
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] where is grep?

[Azul]

some large refactoring left me with this one,

/run/current-system/sw/bin/grep
grep: unrecognized option '--color=auto'
BusyBox v1.24.2 () multi-call binary.

grep is coming from busybox,
which package provides the real thing?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] how to set the prefered IO scheduler for a disk on nixos ?

[Azul]

Hi there,

Is there a way to set the IO scheduler on a specific disk?
I need to set the 'noop' scheduler on a disk I have, but can't find a way
on nixos to do so.

wonders if I may have to use a udev rule, cron job, or if there is a way to
execute a single command at boot, bit like rc.local.

thankz
azul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Too many open issues

[Azul]

triage exists to help manipulating a backlog, it is just another tool to
make sure team members are only working valuable issues and not spend the
time bikshedding, it also prevents duplication.
auto-closing issues due to being no longer applicable, or simply to reduce
the size of the backlog is another tool.
theming or (tagging) issues another process that helps to keep team members
with knowhow in a particular area aligned with the issues they care or are
able to fix in the shortest amount of time compared to other
dev/maintainers in the team.
voting is another good way to measure how important an issue is for a
number of users.
with these processes in place, someone responsible for managing the backlog
can look to every issue opened and work their way to reduce the overall
size of that backlog. then, it can be tagged and grouped into themes,
languages, maintainers, expertise and so on so that maintainers can find
then quickly.
if the backlog is then sorted by votes, common sense or other means then it
can be sliced and batched so that there is always a chunk of issues
available to be worked on ( attempt readers probably noticed by now I am a
kanban boy).

open source prj on github have the best tooling available to manage these
workflows, tools like the 'autoclose machine' mentioned here, zenhub for
managing work in progress in a simple board and others  are out there and
usually free for open source projects.

from this thread it seems to me that the most useful action would be to
nominate someone to manage that backlog and make a constant effort to bring
it down to a workable size, and always ordered by the ones that need to be
tackled first.
On 22 Jul 2016 17:58, "Guillaume Maudoux (Layus)" 
wrote:

> Hi,
>
> I have tried code triage for some weeks, and finally stopped using it.
>
> Yes, it allows to spread attention to many issues, but many issues do not
> need attention, either because they are already in progress, or because
> nobody really cares.
>
> Some issues are even weirder, like the 200 issues opened automatically for
> wiki migration. These are the only one that could benefit from auto close.
>
> Codetriage is not the solution, and not really a solution.
>
> Regards,
>
> -- Layus.
>
> Le 22 juillet 2016 20:12:18 UTC+07:00, Kevin Cox  a
> écrit :
>>
>> On 22/07/16 08:55, Alexey Shmalko wrote:
>>
>>>  This one: https://www.codetriage.com/nixos/nixpkgs
>>
>>
>>
>> That's it! I have subscribed to get a couple issues a day so hopefully I
>> can help a bit. This site seems like a nice way to spread the load.
>>
>> It's open source too, and I just opened an issue asking them to
>> implement filters as I'm not really interesting in seeing in-progress
>> issues.
>>
>> https://github.com/codetriage/codetriage/issues/498
>>
>>
>> --
>>
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 20bb54: pythonPackages.pygit2: 0.23.1 -> 0.24.0 (#15986)

[Azul]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 20bb5402dcc000c442a0d83b4f855fac05549c1e
  
https://github.com/NixOS/nixpkgs/commit/20bb5402dcc000c442a0d83b4f855fac05549c1e
  Author: Azul 
  Date:   2016-07-19 (Tue, 19 Jul 2016)

  Changed paths:
M pkgs/top-level/python-packages.nix

  Log Message:
  ---
  pythonPackages.pygit2: 0.23.1 -> 0.24.0 (#15986)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-dev] nix on the corporate world (no direct internet access)

[Azul]

Hey all,

So I am using nix on one of those nasty corp network environments, where
not even DNS works and everything needs to go through the corporate proxy.

The proxy is slow, a lot of URLs are blocked down as 'gambling' (just try
to download a jenkins plugin !!) and using tooling like cntlm is hard, as
it hangs more often than not on load.

in my production environment, I won't have internet access so I need to
install nix packages from a on-premises repository.


So we're looking into caching the nix packages we consume through a remote
repository in artifactory (which can get much friendlier 'red tape' in
accessing the outside world).

My question, is has anyone done this ?
would a silly url like http://artifactory/remote_nix/file_paths invalidate
the hydra cache and force all packages to be built locally ?

-azul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] patch: eclipse version 4.6

[Azul]

so what do you guys use as a quality gate then?
how do you make sure a patch won't break master? are you just testing it
locally on your machines?

- curious
On 3 Jul 2016 16:27, "Bjørn Forsman"  wrote:

> On 3 July 2016 at 17:20, Azul  wrote:
> > n00b to the nix community so forgive my ignorance here.
> > is this the correct way to submit patches to nixpkgs ?
> > I attempted a PR some time ago which I never managed to get to build
> > properly on Travis or identify why the Travis build scripts failed the
> the
> > build , so I scrapped it all together. Being new to nix and being very
> short
> > of time meant I didn't have the opportunity to debug it properly. I could
> > say I read some sort of contributor guidelines which lead to follow the
> > usual github PR, test, wait for green and ask for a review but maybe I
> just
> > dreamed it up or I was thinking of some other open source project?
> >
> > so what is the best way to send patches to nix in a sane and safe way
> that
> > won't break master ?
>
> In general the best way is github PRs. But patches on the mailing list
> may be applied too. Someone just have to do it...
>
> The Travis builds are unfortunately failing a lot. It is my feeling
> that most devs will look at PRs even if Travis are failing.
>
> - Bjørn
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] patch: eclipse version 4.6

[Azul]

n00b to the nix community so forgive my ignorance here.
is this the correct way to submit patches to nixpkgs ?
I attempted a PR some time ago which I never managed to get to build
properly on Travis or identify why the Travis build scripts failed the the
build , so I scrapped it all together. Being new to nix and being very
short of time meant I didn't have the opportunity to debug it properly. I
could say I read some sort of contributor guidelines which lead to follow
the usual github PR, test, wait for green and ask for a review but maybe I
just dreamed it up or I was thinking of some other open source project?

so what is the best way to send patches to nix in a sane and safe way that
won't break master ?
On 3 Jul 2016 16:11, "Bjørn Forsman"  wrote:

> On 3 July 2016 at 17:02, Karn Kallio  wrote:
> >
> > The attached patch adds the latest release of eclipse 4.6 (neon) to
> > nixpkgs.
>
> Tested on NixOS 64-bit and pushed to master (I edited the commit
> message to make it clear that this is eclipse-platform).
>
> Thanks!
>
> - Bjørn
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Multiple machines with nix store shared via NFS

[Azul]

how would you rollback a broken system if the /nix store was remote and the
box wouldnt boot or have no network ?

On 1 July 2016 at 21:34, Layus  wrote:

> I never sait it was a good idea, just soemthing worth investigating.
>
> Now, this has been discussed on the ML already
>
> See for example
> [Nix-dev] Sharing the Nix store between systems
> 
> *Rickard Nilsson *[Nix-dev] nix on compute cluster?
> 
>
> * Andreas Herrmann *And more generally Google search on site:
> http://lists.science.uu.nl/pipermail/nix-dev/ :-).
>
> -- Layus.
>
>
> On 01/07/16 21:55, Renato Alves wrote:
>
> I never tried it with sockets, only tcp ports.
>
> I need to move the socket to a different location. Currently it also
> sits on NFS. I can play with symlinks making it point to a local disk.
>
> The entire setup sounds terribly hackish though.
>
> If anyone has better alternatives I'd love to hear them.
>
> Thanks,
> R
>
> On 01/07/16 20:51, Layus wrote:
>
> Just one idea off the top of my head: Would it be possible to forward
> the unix socket of the daemon ?
>
> -- Layus ?
>
> On 01/07/16 15:10, Renato Alves wrote:
>
> Hi everyone,
>
>
> Recently I've been trying to setup nix on a multiple-machine shared
> environment. At the moment I have one machine setup with nix-daemon
> running from a store in a custom location (/shared/myuser/nix). This
> location is shared via NFS with several other machines. This is all
> still pretty new to me as I've only recently started using nix and
> haven't used nixos yet.
>
> Before setting up nix-daemon I ran into some problems with database
> corruption (sqlite) due to concurrent processes. With nix-daemon these
> have gone away.
>
> One limitation that I identified recently is that on any of the other
> machines that do not have nix-daemon running (but have read access to
> the store) I can run commands from the store without problems but
> cannot, for instance, use nix-shell.
> So I thought of spawning a nix-daemon instance on those machines but I'm
> not sure what is the best way to set it up without risking DB corruption
> again.
>
> These are the requirements I'd like to meet:
>  * /shared/myuser/nix is shared across multiple machines with the same
> architecture (x86_64-linux).
>  * All machines should be able to use nix-shell or any nix related
> command, including requesting installation of packages.
>  * Only some machines are allowed to compile. Machines that are not
> allowed should rely on something like remote-systems.conf to distribute
> work.
>
> Is this kind of setup currently possible with nix? If so, can someone
> provide some guidance?
>
>
> Thanks,
> Renato
>
>
>
> ___
> nix-dev mailing 
> listnix-...@lists.science.uu.nlhttp://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
>
> ___
> nix-dev mailing 
> listnix-...@lists.science.uu.nlhttp://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
> ___
> nix-dev mailing 
> listnix-...@lists.science.uu.nlhttp://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Disabling gnome-keyring xdg autostart configuration

[Azul]

I simply commit my .config folder into git.
there is so much customization to be done on the higher level window
managers and apps, that I personally don't think its worth the time finding
about a particular way to set a particular setting.
On 21 Jun 2016 22:35, "Philip Potter"  wrote:

> I got a solution to my problem in the end!
>
> I got stuck for a while because removing the /etc/xdg/autostart
> symlink is basically impossible without recompiling the gnome-keyring
> package.  However, the xdg autostart standard allows users to override
> these values by putting files into ~/.config.
>
> This askubuntu stack exchange answer captures it perfectly:
> http://askubuntu.com/a/607563/559764
>
> All I had to do was:
> cp /run/current-system/sw/etc/xdg/autostart/gnome-keyring-ssh.desktop
> ~/.config/autostart
> echo Hidden=true >> ~/.config/autostart/gnome-keyring-ssh.desktop
>
> and now gnome-keyring's ssh component no longer starts, and I can use
> gpg-agent as my ssh-agent again as desired.
>
> I think there may be a way to do this more declaratively by instead
> installing a package into the user profile which would drop the
> required file into
> ~/.nix-profile/etc/xdg/autostart/gnome-keyring-ssh.desktop but I
> haven't fully investigated this yet.
>
> Phil
>
>
>
> On 18 June 2016 at 12:24, Philip Potter  wrote:
> > Hello all,
> >
> > I'm using NixOS and trying to set up gpg-agent under gnome.  As part
> > of this, I want to use gpg-agent as an ssh-agent.
> >
> > However, gnome-keyring also acts as an ssh-agent, so I want to disable
> > this functionality.
> >
> > It's possible to disable this by compiling it out entirely [1] but
> > this seems heavyweight, not least because it would require recompiling
> > anything which depends on gnome-keyring.
> >
> > It seems it's also possible to disable it by removing the
> > /etc/xdg/autostart symlink for the ssh module [2].
> >
> > Is it possible to do this in NixOS? Enabling gnome causes the
> > gnome3.gnome_keyring package to be added to systemPackages, which
> > seems to automatically add all gnome-keyring /etc/xdg/autostart files
> > to the system profile. Can I suppress a single autostart script when
> > adding a package to systemPackages? Is there some sort of package
> > override that would let me do this?
> >
> > Phil
> >
> > [1]: https://wiki.gnome.org/Projects/GnomeKeyring/Ssh
> > [2]:
> https://wiki.archlinux.org/index.php/GNOME/Keyring#Disable_keyring_daemon_SSH_component
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Malicious installation methods

[Azul]

simple as that,
just don't do it.

https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/
On 17 Jun 2016 12:38, "Kevin Cox"  wrote:

> On 17/06/16 07:12, Yui Hirasawa wrote:
> >
> > Retrieving code straight from the internet and blindly executing is
> > never a good thing and you don't give any sort of recommendation for the
> > user to inspect the script before running it. This completely defeats
> > the point of having reproducible builds when your system can be
> > completely infected when you install the package manager. This also
> > means that anything installed through the package manager is potentially
> > malicious as well.
> >
> >> $ curl https://nixos.org/nix/install | sh
> >
>
> This has been discussed in many forms in many places. You are
> downloading code that you intend to run as root on your machine, and the
> distribution method is over a verified channel. This is no more
> dangerous then most other ways to download software that your root user
> will run.
>
> One improvement would be to sign the actual script with an offline key
> but while that would be safer the current method is perfectly fine.
>
> I know that people see `curl http...` and get all excited but, in this
> case at least, it is a sufficiently secure method.
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Importing a .nix.gpg file?

[Azul]

:following

I simply keep my .gnupg in git, curious about what others do.
On 13 Jun 2016 11:39, "Michal Rus"  wrote:

> Hey,
>
> in my nixos-config, I’ve got wifi-passwords.nix.gpg (the rest of the
> config is publicly available), and what I’d like to do is:
>
> import ./wifi-passwords.nix.gpg;
>
> Or:
>
> imports = [ ./wifi-passwords.nix.gpg ];
>
> … somewhere in configuration.nix. And when issuing `nixos-rebuild
> switch`, GnuPG would be used to decrypt the file.
>
> How can I achieve that? Was this discussed before (I can’t find any
> mentions)? May I post a feature request in an issue or will it be
> rejected?
>
> This seems like a useful feature and I have quite a few other uses for
> it besides Wi-Fi passwords. Currently, I’m using gpg manually, though,
> and that’s asking for errors.
>
> Thank you!
>
> --
> Michal Rus
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] help with Travis builds

[Azul]

hmmm,

so I changed the Vagrantfile that was working and tried to break it (to
replicate the travis failed build), by adding the chroot option.
But it still works fine.

The Vagrantfile that fails is executing the same build steps as the travis
builds.
This is causing me an itch.



```
vbox_version = `VBoxManage --version`

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.network "private_network", ip: "192.168.33.96", nic_type:
"virtio"

  config.vm.provider "virtualbox" do |vb|
 vb.memory = "3072"
 vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
 vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
 vb.customize [ "guestproperty", "set", :id,
"/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 1 ]
 vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
 vb.customize ["modifyvm", :id, "--paravirtprovider", "kvm"] if
vbox_version.to_f >= 5.0
 vb.customize ["storagectl", :id, "--name", "SATAController",
"--hostiocache", "on"]
 vb.customize ["modifyvm", :id, "--ioapic", "on"]
 vb.customize ["modifyvm", :id, "--cpus",
`#{RbConfig::CONFIG['host_os'] =~ /darwin/ ? 'sysctl -n hw.ncpu' :
'nproc'}`.chomp]

 vb.linked_clone = true if Vagrant::VERSION =~ /^1.8/
  end
  config.vm.provision "shell", privileged: true, inline: <<-SHELL
groupadd nixbld
usermod -G nixbld vagrant
apt-get update
apt-get install -y build-essential git
test -e /swapfile || ( dd if=/dev/zero of=/swapfile bs=1M count=2048 &&
 mkswap /swapfile )
swapon /swapfile || echo
  SHELL

  config.vm.provision "shell", privileged: false, inline: <<-SHELL
 git clone https://github.com/NixOS/nixpkgs.git
 cd nixpkgs
 git config --global user.email "m...@example.com"
 git config --global user.name "Your Name"

 git remote add Azulinho https://github.com/Azulinho/nixpkgs.git
 set -e
 git fetch Azulinho
 git merge Azulinho/update_libgit2_to_v24
 set +e
 export NIXPKGS=$PWD
 export TRAVIS_PULL_REQUEST=15986
./maintainers/scripts/travis-nox-review-pr.sh nix
./maintainers/scripts/travis-nox-review-pr.sh nox
. /home/vagrant/.nix-profile/etc/profile.d/nix.sh
nix-build nixos/release.nix -A options --show-trace
nix-build pkgs/top-level/release.nix -A tarball --show-trace
  SHELL

  config.vm.provision "shell", privileged: true, inline: <<-SHELL
cd /home/vagrant/nixpkgs
. /home/vagrant/.nix-profile/etc/profile.d/nix.sh
nix-build --option build-use-chroot true $PWD -A python27Packages.pygit2
nix-build --option build-use-chroot true $PWD -A python35Packages.pygit2
  SHELL
end
```


On 10 June 2016 at 09:06, zimbatm  wrote:

> It doesn't look like your vms are using the nix sandbox so some things
> could get picked from the environment?
>
> On Thu, 9 Jun 2016, 22:36 Azul,  wrote:
>
>> n00b here
>>
>> Trying to sort out PR: https://github.com/NixOS/nixpkgs/pull/15986
>>
>> while "it works on my machine", travis barks out at me with:
>> https://travis-ci.org/NixOS/nixpkgs/builds/135414974
>>
>> so I looked into the travis builds to find out what they were doing, and
>> come up with this to replicate them locally.
>>
>> This Vagrantfile fails with the same error as Travis
>>
>> ```
>> vbox_version = `VBoxManage --version`
>>
>> Vagrant.configure(2) do |config|
>>   config.vm.box = "ubuntu/trusty64"
>>   config.vm.network "private_network", ip: "192.168.33.96", nic_type:
>> "virtio"
>>
>>   config.vm.provider "virtualbox" do |vb|
>>  vb.memory = "3072"
>>  vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
>>  vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
>>  vb.customize [ "guestproperty", "set", :id,
>> "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 1 ]
>>  vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
>>  vb.customize ["modifyvm", :id, "--paravirtprovider", "kvm"] if
>> vbox_version.to_f >= 5.0
>>  vb.customize ["storagectl", :id, "--name", "SATAController",
>> "--hostiocache", "on"]
>>  vb.customize [&qu

[Nix-dev] help with Travis builds

[Azul]

n00b here

Trying to sort out PR: https://github.com/NixOS/nixpkgs/pull/15986

while "it works on my machine", travis barks out at me with:
https://travis-ci.org/NixOS/nixpkgs/builds/135414974

so I looked into the travis builds to find out what they were doing, and
come up with this to replicate them locally.

This Vagrantfile fails with the same error as Travis

```
vbox_version = `VBoxManage --version`

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.network "private_network", ip: "192.168.33.96", nic_type:
"virtio"

  config.vm.provider "virtualbox" do |vb|
 vb.memory = "3072"
 vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
 vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
 vb.customize [ "guestproperty", "set", :id,
"/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 1 ]
 vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
 vb.customize ["modifyvm", :id, "--paravirtprovider", "kvm"] if
vbox_version.to_f >= 5.0
 vb.customize ["storagectl", :id, "--name", "SATAController",
"--hostiocache", "on"]
 vb.customize ["modifyvm", :id, "--ioapic", "on"]
 vb.customize ["modifyvm", :id, "--cpus",
`#{RbConfig::CONFIG['host_os'] =~ /darwin/ ? 'sysctl -n hw.ncpu' :
'nproc'}`.chomp]

 vb.linked_clone = true if Vagrant::VERSION =~ /^1.8/
  end
  config.vm.provision "shell", inline: <<-SHELL
groupadd nixbld
usermod -G nixbld vagrant
apt-get update
apt-get install -y build-essential git
test -e /swapfile || ( dd if=/dev/zero of=/swapfile bs=1M count=2048 &&
 mkswap /swapfile )
swapon /swapfile
  SHELL

  config.vm.provision "shell", privileged: false, inline: <<-SHELL
 git clone https://github.com/NixOS/nixpkgs.git
 cd nixpkgs
 export TRAVIS_PULL_REQUEST=15986
./maintainers/scripts/travis-nox-review-pr.sh nix
./maintainers/scripts/travis-nox-review-pr.sh nox
./maintainers/scripts/travis-nox-review-pr.sh build
  SHELL
end
```


But this Vagrantfile builds my PR correctly

```
vbox_version = `VBoxManage --version`

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.network "private_network", ip: "192.168.33.96", nic_type:
"virtio"

  config.vm.provider "virtualbox" do |vb|
 vb.memory = "3072"
 vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
 vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
 vb.customize [ "guestproperty", "set", :id,
"/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 1 ]
 vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
 vb.customize ["modifyvm", :id, "--paravirtprovider", "kvm"] if
vbox_version.to_f >= 5.0
 vb.customize ["storagectl", :id, "--name", "SATAController",
"--hostiocache", "on"]
 vb.customize ["modifyvm", :id, "--ioapic", "on"]
 vb.customize ["modifyvm", :id, "--cpus",
`#{RbConfig::CONFIG['host_os'] =~ /darwin/ ? 'sysctl -n hw.ncpu' :
'nproc'}`.chomp]

 vb.linked_clone = true if Vagrant::VERSION =~ /^1.8/
  end
  config.vm.provision "shell", inline: <<-SHELL
groupadd nixbld
usermod -G nixbld vagrant
apt-get update
apt-get install -y build-essential git
test -e /swapfile || ( dd if=/dev/zero of=/swapfile bs=1M count=2048 &&
 mkswap /swapfile )
swapon /swapfile || echo
  SHELL

  config.vm.provision "shell", privileged: false, inline: <<-SHELL
 git clone https://github.com/NixOS/nixpkgs.git
 cd nixpkgs
 git config --global user.email "m...@example.com"
 git config --global user.name "Your Name"

 git remote add Azulinho https://github.com/Azulinho/nixpkgs.git
 git fetch Azulinho
 git merge Azulinho/update_libgit2_to_v24
 export NIXPKGS=$PWD
 export TRAVIS_PULL_REQUEST=15986
./maintainers/scripts/travis-nox-review-pr.sh nix
./maintainers/scripts/travis-nox-review-pr.sh nox
. $HOME/.nix-profile/etc/profile.d/nix.sh
nix-build nixos/release.nix -A options --show-trace
nix-build pkgs/top-level/release.nix -A tarball --show-trace
nix-build $PWD -A python27Packages.pygit2
nix-build $PWD -A python35Packages.pygit2
  SHELL
end
```

Before I dig into reading about nox and getting into the grittier details,
does anyone has a hint for what could possibly be happening here?
happy to pay back with a merged PR

- azul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev