from:"Kamil Chmielewski"

[Nix-commits] [NixOS/nixpkgs] 9943e5: ponyc: 0.13.1 -> 0.14.0

2017-05-08 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9943e5635c592e284ac5a023822cce563ff9b236
  
https://github.com/NixOS/nixpkgs/commit/9943e5635c592e284ac5a023822cce563ff9b236
  Author: Kamil Chmielewski 
  Date:   2017-05-08 (Mon, 08 May 2017)

  Changed paths:
M pkgs/development/compilers/ponyc/default.nix

  Log Message:
  ---
  ponyc: 0.13.1 -> 0.14.0

https://github.com/ponylang/ponyc/issues/1877


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

Re: [Nix-dev] The .nixpkgs/config.nix file and user configuration

2017-05-03 Thread Kamil Chmielewski

Hi John,

you could find my https://github.com/kamilchm/.nixpkgs helpfull.
I use config.nix to manage user pacakges and dofiles and link them into ~
with simple script
https://github.com/kamilchm/.nixpkgs/blob/master/install.sh

Best regards,
Kamil

2017-05-04 3:55 GMT+02:00 John Ramsden :

> Thanks, for the information.
>
> Marc Weber mentioned
>
> 1) you can install system wide (nixos-rebuild ..)
>> 2) you can install as user into ~/.nix-profile.nix
>>
>>~/.config.nix is to "customize" user nixpkgs by
>>- setting settings such as allowUnfree
>>- override mplayer to use library X
>>- add your own packages FOO
>>
>
> In that case, if I did list my own packages in ~/.nix-profile.nix, would
> that install only into that user profile?
>
> When I run nixos-rebuild switch does that rebuild the user profiles as
> well?
>
> I don't like the idea of using nix-env, and I have strayed away from it on
> NixOS, the idea of having all my configuration explicitly written out in
> configuration files is part of what I like about Nix.
>
> ---
>   John Ramsden
>
> ___
> 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] caade7: ponyc: 0.11.4 -> 0.12.2

2017-03-30 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: caade79100ca9df22f7f5592811b05b34bef5cd6
  
https://github.com/NixOS/nixpkgs/commit/caade79100ca9df22f7f5592811b05b34bef5cd6
  Author: Kamil Chmielewski 
  Date:   2017-03-31 (Fri, 31 Mar 2017)

  Changed paths:
M pkgs/development/compilers/ponyc/default.nix
M pkgs/development/compilers/ponyc/pony-stable.nix

  Log Message:
  ---
  ponyc: 0.11.4 -> 0.12.2

https://github.com/ponylang/ponyc/issues/1786


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

[Nix-commits] [NixOS/nixpkgs] 15cc79: icewm: fix CFGDIR

2017-03-17 Thread Kamil Chmielewski

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 15cc79581724a745ecaf1f3a6a4add5bfd899510
  
https://github.com/NixOS/nixpkgs/commit/15cc79581724a745ecaf1f3a6a4add5bfd899510
  Author: Volth 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M pkgs/applications/window-managers/icewm/default.nix

  Log Message:
  ---
  icewm: fix CFGDIR

(cherry picked from commit fd61a33d2b42d86215c1697c8da11218279ac802)


  Commit: 0786d9f4ad09b1b52ab3800240749889a83c6fb5
  
https://github.com/NixOS/nixpkgs/commit/0786d9f4ad09b1b52ab3800240749889a83c6fb5
  Author: Profpatsch 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M nixos/modules/services/mail/mlmmj.nix

  Log Message:
  ---
  modules/mlmmj: fix a typo in listaddress folder

(cherry picked from commit 6da60bb10142ba2e63309da048044026f7158d0a)


  Commit: 05fcddf977485848c5d3b40141bd23823003df5c
  
https://github.com/NixOS/nixpkgs/commit/05fcddf977485848c5d3b40141bd23823003df5c
  Author: Léo Gaspard 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M nixos/modules/security/dhparams.nix

  Log Message:
  ---
  dhparams module: condition on enable option (#23661)

Hence, the init/cleanup service only runs when the dhparams module is enabled.
(cherry picked from commit 66e54f25a160ed1cd9d0a008c2c61f9c30a84eb1)


  Commit: 8cff9b9ccfe2b877ba2880d93b6b4eefada72926
  
https://github.com/NixOS/nixpkgs/commit/8cff9b9ccfe2b877ba2880d93b6b4eefada72926
  Author: Linus Heckemann 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M pkgs/development/interpreters/renpy/default.nix

  Log Message:
  ---
  renpy: mark as broken

(cherry picked from commit 9b62e41c1e13c363b679f07f4f677cfa2e6c2acd)


  Commit: 7b401c71ce644bc131139037829decc4f31ac83d
  
https://github.com/NixOS/nixpkgs/commit/7b401c71ce644bc131139037829decc4f31ac83d
  Author: Michael Raskin <7c6f4...@mail.ru>
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M nixos/tests/firefox.nix

  Log Message:
  ---
  nixos: tests: firefox: make more comprehensive

Run Firefox inside an XTerm, it doesn't crash mysteriously this way.
Also try opening developer tools and checking that Firefox doesn't
crash in the process.

(cherry picked from commit 14a3412048473e022e4bc2c687c66bb5f30c0e42)


  Commit: fadb858e880326bb1f6ec95598b369e9f76c3caf
  
https://github.com/NixOS/nixpkgs/commit/fadb858e880326bb1f6ec95598b369e9f76c3caf
  Author: Kamil Chmielewski 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M pkgs/development/compilers/ponyc/default.nix
M pkgs/development/compilers/ponyc/pony-stable.nix

  Log Message:
  ---
  ponyc: 0.11.0 -> 0.11.3

(cherry picked from commit 017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf)


Compare: https://github.com/NixOS/nixpkgs/compare/3879491de261...fadb858e8803___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 017fdd: ponyc: 0.11.0 -> 0.11.3

2017-03-17 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf
  
https://github.com/NixOS/nixpkgs/commit/017fddb4be7d5c074a0b3e2dfb26b88d5e90ceaf
  Author: Kamil Chmielewski 
  Date:   2017-03-17 (Fri, 17 Mar 2017)

  Changed paths:
M pkgs/development/compilers/ponyc/default.nix
M pkgs/development/compilers/ponyc/pony-stable.nix

  Log Message:
  ---
  ponyc: 0.11.0 -> 0.11.3


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

[Nix-commits] [NixOS/nixpkgs] 98cc72: chromium: flashplayer: 24.0.0.221 -> 25.0.0.127

2017-03-16 Thread Kamil Chmielewski

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 98cc721bc4ec537f411835f90dba18ec50062b52
  
https://github.com/NixOS/nixpkgs/commit/98cc721bc4ec537f411835f90dba18ec50062b52
  Author: Kamil Chmielewski 
  Date:   2017-03-16 (Thu, 16 Mar 2017)

  Changed paths:
M pkgs/applications/networking/browsers/chromium/plugins.nix

  Log Message:
  ---
  chromium: flashplayer: 24.0.0.221 -> 25.0.0.127

[Critical security fix]
https://github.com/NixOS/nixpkgs/pull/23889


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

[Nix-commits] [NixOS/nixpkgs] 91e874: chromium: flashplayer: 24.0.0.221 -> 25.0.0.127

2017-03-16 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 91e87421cd6acc57d740494a6e1f7a89bc39e5d7
  
https://github.com/NixOS/nixpkgs/commit/91e87421cd6acc57d740494a6e1f7a89bc39e5d7
  Author: Kamil Chmielewski 
  Date:   2017-03-16 (Thu, 16 Mar 2017)

  Changed paths:
M pkgs/applications/networking/browsers/chromium/plugins.nix

  Log Message:
  ---
  chromium: flashplayer: 24.0.0.221 -> 25.0.0.127

[Critical security fix]
https://github.com/NixOS/nixpkgs/pull/23889

(cherry picked from commit 15e49a95d9c9bdf1efcf08d266f491e54dd51cfb)


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

[Nix-commits] [NixOS/nixpkgs] 1f87bd: go2nix: 1.1.1 -> 1.2.0

2017-03-16 Thread Kamil Chmielewski

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 1f87bd6d3e001ea08e491c9f1d804c944dec2972
  
https://github.com/NixOS/nixpkgs/commit/1f87bd6d3e001ea08e491c9f1d804c944dec2972
  Author: Kamil Chmielewski 
  Date:   2017-03-16 (Thu, 16 Mar 2017)

  Changed paths:
M pkgs/development/tools/go2nix/default.nix

  Log Message:
  ---
  go2nix: 1.1.1 -> 1.2.0

(cherry picked from commit d16b08ac85128c2a74cf21463987f4bab0f1dcab)


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

Re: [Nix-dev] Wrong tags in nixpkgs

2017-03-01 Thread Kamil Chmielewski

On Feb 28, 2017 at 10:05 PM, "Vladimír Čunát"  wrote:

> On 02/28/2017 09:26 PM, Kamil Chmielewski wrote:
>
> > I've never had write permissions to NixOS/nixpkgs so i got:
> Then it would be very strange if you managed to push the tags to nixpkgs.
> Still, it's possible someone else with commit access pulled from your
> repo(s) and then pushed to nixos/nixpkgs by mistake. I looked at
> https://github.com/orgs/NixOS/dashboard but I can't see enough history to
> see creation of the tags - it only shows about last 7 hours, ending during
> Peter's pushing all those branches. --Vladimir
>

3 more left with names starting with 'black@'

Best regards,
Kamil
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Wrong tags in nixpkgs

2017-02-28 Thread Kamil Chmielewski

On Feb 28, 2017 at 09:18 PM, "Bjørn Forsman" 
wrote:

> On 28 February 2017 at 21:16, Vladimír Čunát wrote:
>
> > On 02/28/2017 09:12 PM, Kamil Chmielewski wrote: >> I don't how could
> than happened and how could I remove it from upstream? > > I just ran: > $
> git push origin :v192 > To github.com:NixOS/nixpkgs.git > - [deleted]
> v192 > > You can finish with the others (I'm not certain which they are).
> Oh, I just took the rest! $ git push origin --delete black@2016-05-13
> v206 v208 To https://github.com/nixos/nixpkgs.git - [deleted]
> black@2016-05-13 - [deleted] v206 - [deleted] v208 Hehe, I wondered what
> happened to v192 :-) Best regards, Bjørn Forsman
>

I've never had write permissions to NixOS/nixpkgs so i got:

$ git push upstream :v208
fatal: remote error:
  You can't push to git://github.com/NixOS/nixpkgs.git
  Use https://github.com/NixOS/nixpkgs.git
$ git push upstream :v208
remote: Permission to NixOS/nixpkgs.git denied to kamilchm.
fatal: unable to access 'https://github.com/NixOS/nixpkgs.git/': The
requested URL returned error: 403

Anyway, sorry for the buzz and thx for cleaning it.

Best regards,
Kamil
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Wrong tags in nixpkgs

2017-02-28 Thread Kamil Chmielewski

Yep, something went wrong, those are tags from my private *channel*.
I don't how could than happened and how could I remove it from upstream?

Best regards,
Kamil

On Feb 28, 2017 at 08:49 PM, "Bjørn Forsman" 
wrote:

> Hi Kamil, I think you mistakenly pushed some tags to upstream nixpkgs repo
> (some of those tags are annotated, so they contain your email): $ git pull
> ... From https://github.com/nixos/nixpkgs 63fee95d58..40de598c60
> release-16.09 -> origin/release-16.09 0dee2a1bcc..62c5f68847 master ->
> origin/master * [new branch] release-17.03 -> origin/release-17.03
> 079353e208..ffcc897090 staging -> origin/staging * [new tag]
> black@2016-05-13 -> black@2016-05-13 * [new tag] v192 -> v192 * [new tag]
> v206 -> v206 * [new tag] v208 -> v208 Care to remove them? Best regards,
> Bjørn Forsman
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] ac4559: chromium: flashplayer: 24.0.0.194 -> 24.0.0.221

2017-02-17 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: ac4559e7e9466e32c48744bac736b3c21ab6cd17
  
https://github.com/NixOS/nixpkgs/commit/ac4559e7e9466e32c48744bac736b3c21ab6cd17
  Author: Kamil Chmielewski 
  Date:   2017-02-17 (Fri, 17 Feb 2017)

  Changed paths:
M pkgs/applications/networking/browsers/chromium/plugins.nix

  Log Message:
  ---
  chromium: flashplayer: 24.0.0.194 -> 24.0.0.221

[Critical security fix] - see #22792

(cherry picked from commit 1a77e4141d83b1b0025c226303b77428f6eb74af)
Signed-off-by: Robin Gloster 


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

[Nix-commits] [NixOS/nixpkgs] 1a77e4: chromium: flashplayer: 24.0.0.194 -> 24.0.0.221

2017-02-15 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 1a77e4141d83b1b0025c226303b77428f6eb74af
  
https://github.com/NixOS/nixpkgs/commit/1a77e4141d83b1b0025c226303b77428f6eb74af
  Author: Kamil Chmielewski 
  Date:   2017-02-15 (Wed, 15 Feb 2017)

  Changed paths:
M pkgs/applications/networking/browsers/chromium/plugins.nix

  Log Message:
  ---
  chromium: flashplayer: 24.0.0.194 -> 24.0.0.221

[Critical security fix] - see #22792


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

[Nix-commits] [NixOS/nixpkgs] 100795: vagrant: 1.8.7 -> 1.9.1

2016-12-18 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 100795e45f4f4279bc1f777e4483d60d81ea4c1b
  
https://github.com/NixOS/nixpkgs/commit/100795e45f4f4279bc1f777e4483d60d81ea4c1b
  Author: Kamil Chmielewski 
  Date:   2016-12-18 (Sun, 18 Dec 2016)

  Changed paths:
M pkgs/development/tools/vagrant/default.nix

  Log Message:
  ---
  vagrant: 1.8.7 -> 1.9.1

(cherry picked from commit 9aa6c95d5a5e2221459c0153e2628ec09d69f9ac)


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

Re: [Nix-dev] Nixos vps

2016-12-12 Thread Kamil Chmielewski

I have done basic NixOps deploy support for CloudSigma:
*
https://github.com/kamilchm/nixpkgs/commit/a64c343cd4baa07fea1bcac422a4eaa9fb2f86d9
*
https://github.com/kamilchm/nixops/commit/c2ec202f6b9a1bd488fa27abf3c218241b37b5d5

But it's just a PoC.

Best regards,
Kamil

2016-12-12 10:31 GMT+01:00 Nathan Bijnens :

> I have used Vultr, but you first need to create an image, see:
> https://www.vultr.com/docs/install-nixos-on-vultr
>
> You can also use NixOS on Azure and Amazon AWS, ideally using NixOps...
>
> Best regards,
>   Nathan
>
>
> On Mon, Dec 12, 2016 at 9:37 AM Azul  wrote:
>
> 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
>
>
> ___
> 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] f3d9eb: vagrant: make patches a list (#18364)

2016-10-10 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: f3d9eb8467fdc8229fe932d94069716915663200
  
https://github.com/NixOS/nixpkgs/commit/f3d9eb8467fdc8229fe932d94069716915663200
  Author: Aneesh Agrawal 
  Date:   2016-10-10 (Mon, 10 Oct 2016)

  Changed paths:
M pkgs/development/tools/vagrant/default.nix

  Log Message:
  ---
  vagrant: make patches a list (#18364)

This has more correct semantics, allows for multiple patches, and makes
using overrideDerivation to add/remove patches work as expected.
(cherry picked from commit b1c83e8928288044d110528642d8af24389ac73b)


  Commit: 0c022c45df220159233d591eadcd85118dd70345
  
https://github.com/NixOS/nixpkgs/commit/0c022c45df220159233d591eadcd85118dd70345
  Author: Kamil Chmielewski 
  Date:   2016-10-10 (Mon, 10 Oct 2016)

  Changed paths:
M pkgs/development/tools/vagrant/default.nix

  Log Message:
  ---
  vagrant: 1.8.5 -> 1.8.6

(cherry picked from commit 4f6870bb4b2e95f1f9488ce0f0a2a3e959bd4c99)


Compare: https://github.com/NixOS/nixpkgs/compare/704713d916e2...0c022c45df22___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 23e34f: go2nix: 1.1.0 -> 1.1.1

2016-09-27 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 23e34fb71bc587db46f7f0b92a2eb38a2cf85e78
  
https://github.com/NixOS/nixpkgs/commit/23e34fb71bc587db46f7f0b92a2eb38a2cf85e78
  Author: Kamil Chmielewski 
  Date:   2016-09-27 (Tue, 27 Sep 2016)

  Changed paths:
M pkgs/development/tools/go2nix/default.nix

  Log Message:
  ---
  go2nix: 1.1.0 -> 1.1.1

(cherry picked from commit badd0ce218b6ed98972db2890f1cc53dabb4f430)


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

[Nix-commits] [NixOS/nixpkgs] 9ab3dc: buildGoPackage: deps.json -> deps.nix in NIXON

2016-09-15 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9ab3dc25ceb7c604a072313492b9dca418bec87e
  
https://github.com/NixOS/nixpkgs/commit/9ab3dc25ceb7c604a072313492b9dca418bec87e
  Author: Kamil Chmielewski 
  Date:   2016-09-16 (Fri, 16 Sep 2016)

  Changed paths:
M doc/languages-frameworks/go.xml
M nixos/doc/manual/release-notes/rl-1609.xml
M pkgs/applications/misc/hugo/default.nix
R pkgs/applications/misc/hugo/deps.json
A pkgs/applications/misc/hugo/deps.nix
M pkgs/applications/misc/mop/default.nix
R pkgs/applications/misc/mop/deps.json
A pkgs/applications/misc/mop/deps.nix
M pkgs/applications/misc/wego/default.nix
R pkgs/applications/misc/wego/deps.json
A pkgs/applications/misc/wego/deps.nix
M pkgs/applications/networking/drive/default.nix
R pkgs/applications/networking/drive/deps.json
A pkgs/applications/networking/drive/deps.nix
M pkgs/applications/networking/instant-messengers/pond/default.nix
R pkgs/applications/networking/instant-messengers/pond/deps.json
A pkgs/applications/networking/instant-messengers/pond/deps.nix
M pkgs/applications/networking/instant-messengers/xmpp-client/default.nix
R pkgs/applications/networking/instant-messengers/xmpp-client/deps.json
A pkgs/applications/networking/instant-messengers/xmpp-client/deps.nix
R pkgs/applications/networking/syncthing/inotify-deps.json
A pkgs/applications/networking/syncthing/inotify-deps.nix
M pkgs/applications/networking/syncthing/inotify.nix
M pkgs/applications/networking/syncthing012/default.nix
R pkgs/applications/networking/syncthing012/deps.json
A pkgs/applications/networking/syncthing012/deps.nix
M 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/default.nix
R 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/deps.json
A 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/deps.nix
M pkgs/development/go-modules/generic/default.nix
M pkgs/development/tools/deis/default.nix
R pkgs/development/tools/deis/deps.json
A pkgs/development/tools/deis/deps.nix
M pkgs/development/tools/go-repo-root/default.nix
A pkgs/development/tools/go-repo-root/deps.nix
M pkgs/development/tools/go2nix/default.nix
R pkgs/development/tools/go2nix/deps.json
A pkgs/development/tools/go2nix/deps.nix
M pkgs/development/tools/golint/default.nix
R pkgs/development/tools/golint/deps.json
A pkgs/development/tools/golint/deps.nix
M pkgs/development/tools/gotools/default.nix
R pkgs/development/tools/gotools/deps.json
A pkgs/development/tools/gotools/deps.nix
M pkgs/development/tools/gox/default.nix
R pkgs/development/tools/gox/deps.json
A pkgs/development/tools/gox/deps.nix
M pkgs/development/tools/leaps/default.nix
R pkgs/development/tools/leaps/deps.json
A pkgs/development/tools/leaps/deps.nix
M pkgs/development/tools/remarshal/default.nix
R pkgs/development/tools/remarshal/deps.json
A pkgs/development/tools/remarshal/deps.nix
M pkgs/development/tools/textql/default.nix
R pkgs/development/tools/textql/deps.json
A pkgs/development/tools/textql/deps.nix
M pkgs/development/web/minify/default.nix
R pkgs/development/web/minify/deps.json
A pkgs/development/web/minify/deps.nix
M pkgs/misc/vim-plugins/default.nix
M pkgs/servers/caddy/default.nix
R pkgs/servers/caddy/deps.json
A pkgs/servers/caddy/deps.nix
M pkgs/servers/etcd/default.nix
R pkgs/servers/etcd/deps.json
A pkgs/servers/etcd/deps.nix
M pkgs/servers/gotty/default.nix
R pkgs/servers/gotty/deps.json
A pkgs/servers/gotty/deps.nix
M pkgs/servers/interlock/default.nix
R pkgs/servers/interlock/deps.json
A pkgs/servers/interlock/deps.nix
M pkgs/servers/mesos-dns/default.nix
R pkgs/servers/mesos-dns/deps.json
A pkgs/servers/mesos-dns/deps.nix
M pkgs/servers/monitoring/prometheus/cli.nix
R pkgs/servers/monitoring/prometheus/cli_deps.json
A pkgs/servers/monitoring/prometheus/cli_deps.nix
M pkgs/servers/monitoring/prometheus/collectd-exporter.nix
R pkgs/servers/monitoring/prometheus/collectd-exporter_deps.json
A pkgs/servers/monitoring/prometheus/collectd-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/haproxy-exporter.nix
R pkgs/servers/monitoring/prometheus/haproxy-exporter_deps.json
A pkgs/servers/monitoring/prometheus/haproxy-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/mesos-exporter.nix
R pkgs/servers/monitoring/prometheus/mesos-exporter_deps.json
A pkgs/servers/monitoring/prometheus/mesos-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/mysqld-exporter.nix
R pkgs/servers/monitoring/prometheus/mysqld-exporter_deps.json
A pkgs/servers/monitoring/prometheus/mysqld-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/nginx-exporter.nix
R

[Nix-commits] [NixOS/nixpkgs] 914e0e: buildGoPackage: deps.json -> deps.nix in NIXON

2016-09-15 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 914e0e594ca2d0fa5d456be208bf703d79f04fa3
  
https://github.com/NixOS/nixpkgs/commit/914e0e594ca2d0fa5d456be208bf703d79f04fa3
  Author: Kamil Chmielewski 
  Date:   2016-09-16 (Fri, 16 Sep 2016)

  Changed paths:
M doc/languages-frameworks/go.xml
M nixos/doc/manual/release-notes/rl-1609.xml
M pkgs/applications/misc/hugo/default.nix
R pkgs/applications/misc/hugo/deps.json
A pkgs/applications/misc/hugo/deps.nix
M pkgs/applications/misc/mop/default.nix
R pkgs/applications/misc/mop/deps.json
A pkgs/applications/misc/mop/deps.nix
M pkgs/applications/misc/wego/default.nix
R pkgs/applications/misc/wego/deps.json
A pkgs/applications/misc/wego/deps.nix
M pkgs/applications/networking/drive/default.nix
R pkgs/applications/networking/drive/deps.json
A pkgs/applications/networking/drive/deps.nix
M pkgs/applications/networking/instant-messengers/pond/default.nix
R pkgs/applications/networking/instant-messengers/pond/deps.json
A pkgs/applications/networking/instant-messengers/pond/deps.nix
M pkgs/applications/networking/instant-messengers/xmpp-client/default.nix
R pkgs/applications/networking/instant-messengers/xmpp-client/deps.json
A pkgs/applications/networking/instant-messengers/xmpp-client/deps.nix
R pkgs/applications/networking/syncthing/inotify-deps.json
A pkgs/applications/networking/syncthing/inotify-deps.nix
M pkgs/applications/networking/syncthing/inotify.nix
M pkgs/applications/networking/syncthing012/default.nix
R pkgs/applications/networking/syncthing012/deps.json
A pkgs/applications/networking/syncthing012/deps.nix
M 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/default.nix
R 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/deps.json
A 
pkgs/applications/version-management/git-and-tools/git-annex-remote-b2/deps.nix
M pkgs/development/go-modules/generic/default.nix
M pkgs/development/tools/deis/default.nix
R pkgs/development/tools/deis/deps.json
A pkgs/development/tools/deis/deps.nix
M pkgs/development/tools/go-repo-root/default.nix
A pkgs/development/tools/go-repo-root/deps.nix
M pkgs/development/tools/go2nix/default.nix
R pkgs/development/tools/go2nix/deps.json
A pkgs/development/tools/go2nix/deps.nix
M pkgs/development/tools/golint/default.nix
R pkgs/development/tools/golint/deps.json
A pkgs/development/tools/golint/deps.nix
M pkgs/development/tools/gotools/default.nix
R pkgs/development/tools/gotools/deps.json
A pkgs/development/tools/gotools/deps.nix
M pkgs/development/tools/gox/default.nix
R pkgs/development/tools/gox/deps.json
A pkgs/development/tools/gox/deps.nix
M pkgs/development/tools/leaps/default.nix
R pkgs/development/tools/leaps/deps.json
A pkgs/development/tools/leaps/deps.nix
M pkgs/development/tools/remarshal/default.nix
R pkgs/development/tools/remarshal/deps.json
A pkgs/development/tools/remarshal/deps.nix
M pkgs/development/tools/textql/default.nix
R pkgs/development/tools/textql/deps.json
A pkgs/development/tools/textql/deps.nix
M pkgs/development/web/minify/default.nix
R pkgs/development/web/minify/deps.json
A pkgs/development/web/minify/deps.nix
M pkgs/misc/vim-plugins/default.nix
M pkgs/servers/caddy/default.nix
R pkgs/servers/caddy/deps.json
A pkgs/servers/caddy/deps.nix
M pkgs/servers/etcd/default.nix
R pkgs/servers/etcd/deps.json
A pkgs/servers/etcd/deps.nix
M pkgs/servers/gotty/default.nix
R pkgs/servers/gotty/deps.json
A pkgs/servers/gotty/deps.nix
M pkgs/servers/interlock/default.nix
R pkgs/servers/interlock/deps.json
A pkgs/servers/interlock/deps.nix
M pkgs/servers/mesos-dns/default.nix
R pkgs/servers/mesos-dns/deps.json
A pkgs/servers/mesos-dns/deps.nix
M pkgs/servers/monitoring/prometheus/cli.nix
R pkgs/servers/monitoring/prometheus/cli_deps.json
A pkgs/servers/monitoring/prometheus/cli_deps.nix
M pkgs/servers/monitoring/prometheus/collectd-exporter.nix
R pkgs/servers/monitoring/prometheus/collectd-exporter_deps.json
A pkgs/servers/monitoring/prometheus/collectd-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/haproxy-exporter.nix
R pkgs/servers/monitoring/prometheus/haproxy-exporter_deps.json
A pkgs/servers/monitoring/prometheus/haproxy-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/mesos-exporter.nix
R pkgs/servers/monitoring/prometheus/mesos-exporter_deps.json
A pkgs/servers/monitoring/prometheus/mesos-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/mysqld-exporter.nix
R pkgs/servers/monitoring/prometheus/mysqld-exporter_deps.json
A pkgs/servers/monitoring/prometheus/mysqld-exporter_deps.nix
M pkgs/servers/monitoring/prometheus/nginx-exporter.nix
R pkgs

[Nix-commits] [NixOS/nixpkgs] e4d629: python27Packages.cairocffi: FIX test_scaled_font

2016-09-09 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e4d62926d657a1529dc990aad4675ff0e594a24c
  
https://github.com/NixOS/nixpkgs/commit/e4d62926d657a1529dc990aad4675ff0e594a24c
  Author: Kamil Chmielewski 
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
A pkgs/development/python-modules/cairocffi/fix_test_scaled_font.patch
M pkgs/top-level/python-packages.nix

  Log Message:
  ---
  python27Packages.cairocffi: FIX test_scaled_font

workaround for https://github.com/Kozea/cairocffi/issues/88

(cherry picked from commit 9e18b81dedec6d06f5bdfc80c26f281f1b07a2d1)
Signed-off-by: Domen Kožar 


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

[Nix-commits] [NixOS/nixpkgs] 55f91c: python27Packages.cairocffi: FIX test_scaled_font

2016-09-09 Thread Kamil Chmielewski

  Branch: refs/heads/release-16.09
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 55f91c2e2558c4a7ac76ba80b3f42e3075d05ccf
  
https://github.com/NixOS/nixpkgs/commit/55f91c2e2558c4a7ac76ba80b3f42e3075d05ccf
  Author: Kamil Chmielewski 
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
A pkgs/development/python-modules/cairocffi/fix_test_scaled_font.patch
M pkgs/top-level/python-packages.nix

  Log Message:
  ---
  python27Packages.cairocffi: FIX test_scaled_font

workaround for https://github.com/Kozea/cairocffi/issues/88

(cherry picked from commit 9e18b81dedec6d06f5bdfc80c26f281f1b07a2d1)
Signed-off-by: Domen Kožar 
(cherry picked from commit e4d62926d657a1529dc990aad4675ff0e594a24c)
Signed-off-by: Domen Kožar 


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

[Nix-commits] [NixOS/nixpkgs] 7b1efb: mesos: 0.28.0 -> 0.28.2 (#18220)

2016-09-02 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7b1efbf6212b6e111fb999da9b62eeb9d6c15d80
  
https://github.com/NixOS/nixpkgs/commit/7b1efbf6212b6e111fb999da9b62eeb9d6c15d80
  Author: Kamil Chmielewski 
  Date:   2016-09-02 (Fri, 02 Sep 2016)

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

  Log Message:
  ---
  mesos: 0.28.0 -> 0.28.2 (#18220)


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

[Nix-commits] [NixOS/nixpkgs] 532b22: vagrant: cleanup FIX plugin install from #17614 (#...

2016-08-12 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 532b965377e77ed884c463ee2751fb51dba3
  
https://github.com/NixOS/nixpkgs/commit/532b965377e77ed884c463ee2751fb51dba3
  Author: Kamil Chmielewski 
  Date:   2016-08-12 (Fri, 12 Aug 2016)

  Changed paths:
M pkgs/development/tools/vagrant/default.nix

  Log Message:
  ---
  vagrant: cleanup FIX plugin install from #17614 (#17663)


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

Re: [Nix-dev] Rework goPackages

2016-08-02 Thread Kamil Chmielewski

Hi,

I refactored all Go applications, moving from deps.json to deps.nix and
encapsulating program dependecies instead of single shared libs.json.
I'm waiting for feedback in https://github.com/NixOS/nixpkgs/pull/17254
especially from Nix maintainers ;)

--
Kamil

2016-06-21 8:20 GMT+02:00 Scott Devoid :

> Hope I didn't kill the thread. :-(
>
> The TL;DR of my post was that I think go2nix is great and needed for
> many Go projects that don't vendor go-dependencies. But, from my Go
> development experience, one shouldn't try to boil-the-ocean and solve
> all Go packaging for everything.
>
> I've also started a PR to add vendoring to github.com/hashicorp/otto. [1]
>
> Cheers,
> ~ Scott
>
> [1] https://github.com/hashicorp/otto/pull/519
>
> On Fri, Jun 17, 2016 at 10:07 AM, Scott Devoid  wrote:
> > Hi Kamil,
> >
> > First thank you for working on this! Having go2nix as a tool certainly
> > makes packaging Go programs much easier! I don't do a lot of Nix
> > packaging but I do write Go software---so maybe I have a different
> > perspective on this. Anyhow here are some thoughts:
> >
> > - Many Go software projects try to be careful to vendor their
> > dependencies. For example, the Caddy server does this and it works
> > very well. Nix only needs to record the top-level package's SHA1 and
> > use fetchFromGithub + buildGoPacakge [1]. No need to recursively
> > expose all dependencies.
> >
> > - An exception to this rule are projects that make use of C or C++
> > linked libraries. [2] For these you would need to add explicit
> > packages.
> >
> > - Then I take a look at Otto's Makefile and the updatedeps target [3]
> > and I am shocked! This is a terrible practice that the Hashicorp folks
> > should fix. They do things correctly with Vault so I don't see why
> > they can't fix it here. In any case, here go2nix is awesome since it
> > can effectively discover each dependency (tooling around the `go list`
> > command and the contents of GOPATH) and produce Nix derivations for
> > each component.
> >
> > - However, putting all of these in a "flat" go-packages.nix seems
> > incorrect. At the very least, two Go programs may require different
> > versions of the same package. And, as you mention, there's the
> > question of how to consistently name these packages. This is even more
> > complicated since packages may be named one thing but reside somewhere
> > else. And some packages get "folded in" to the standard library with
> > subsequent Go releases. [4] Or terrible redirect "services" like
> > gopkg.in [5]
> >
> > - What's the goal here? I would expect that Nix has packages for
> > 'major' Go programs and tooling to make it easy to package new
> > programs or update releases. The tooling should be designed so that an
> > update to one program doesn't break or alter dependencies for other
> > programs. I think this implies that the tooling produces a
> > 'go-libs.json' per-program as opposed to a single top-level
> > go-packages.nix file. This might cause redundant downloads of common
> > dependencies but that cost seems relatively minor compared to the
> > organizational headache that a flat-namespace would require.
> >
> > ~ Scott
> >
> > [1]
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/servers/caddy/default.nix
> > [2] https://golang.org/cmd/cgo
> > [3] https://github.com/hashicorp/otto/blob/master/Makefile#L35
> > [4] See golang.org/x/net/context -> net/context in go1.7
> > [5] http://labix.org/gopkg.in
> >
> > On Fri, Jun 17, 2016 at 6:55 AM, Kamil Chmielewski 
> wrote:
> >> Hi,
> >>
> >> few days ago I started a PR called [WIP] Rework goPackages
> >> https://github.com/NixOS/nixpkgs/pull/16017 which is now on master and
> can
> >> leads to confusion for everyone creating goPackages before. I was also a
> >> little surprised how fast it was merged but I thought it was the effect
> of
> >> how many people feel the same pain as me, trying to manage or introduce
> new
> >> goPackages so there wasn't a lot of discussion there. But now it starts
> in
> >> few places and I think that this will be better place to make decisions
> >> about Go packaging in Nix.
> >>
> >> I want to start with the motivation which led me to this topic. Few
> months
> >> ago I wanted to introduce Otto (https://www.ottoproject.io/) to Nix. I
> was
> >> starting with Nix back then i tried to do things

Re: [Nix-dev] Mesos fetcher

2016-07-26 Thread Kamil Chmielewski

Hi,


I've just tested it on my local NixOS with one simple tgz and everything
works:

I0726 11:59:08.197223 18213 fetcher.cpp:187] Fetching URI
'file:///tmp/fetcher-test/command.tgz'
I0726 11:59:08.197238 18213 fetcher.cpp:167] Copying resource with
command:cp '/tmp/fetcher-test/command.tgz'
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5/command.tgz'
I0726 11:59:08.202335 18213 fetcher.cpp:84] Extracting with command:
/nix/store/3wd1y5bjl4xzhwwd5z3dy7153w5mfmyr-gnutar-1.29/bin/tar -C
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5'
-xf
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5/command.tgz'
I0726 11:59:08.208693 18213 fetcher.cpp:92] Extracted
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5/command.tgz'
into
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5'
I0726 11:59:08.208735 18213 fetcher.cpp:456] Fetched
'file:///tmp/fetcher-test/command.tgz' to
'/tmp/mesos/slaves/7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0/frameworks/2681c520-9d76-413a-ac03-fa28ced72d75-/executors/fetcher-test-sh.5b8ccc91-5328-11e6-a2fb-0a002700/runs/687f7177-cb6a-441a-b59f-e51b89d559d5/command.tgz'
I0726 11:59:08.258139 18210 exec.cpp:143] Version: 0.28.0
I0726 11:59:08.259668 18222 exec.cpp:217] Executor registered on slave
7a5d365d-959a-4942-ba0d-0de6ebf1bd98-S0

I'll try to find some time later to check your example.

--
Kamil


2016-07-26 13:21 GMT+02:00 Maarten Hoogendoorn :

> Hi,
>
> Is anyone on the list using mesos?
>
> I've tried to deploy a mesos framework (mesos-kafka) that depends on the
> extraction of archives, that are downloaded by the mesos fetcher [1].
>
> I've opened an issue about this on the nixpkgs repository as well [2].
>
> [1] http://mesos.apache.org/documentation/latest/fetcher/
> [2] https://github.com/NixOS/nixpkgs/issues/16917
>
> ___
> 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] On npm2nix and the NPM package set in Nixpkgs

2016-07-05 Thread Kamil Chmielewski

+1.. I'll do this in go2nix.

--
Kamil

2016-07-05 15:10 GMT+02:00 Rok Garbas :

> +1 ... i did just that recently for pypi2nix. but i'll also add a link
> to the project home.
>
> [1]
> https://github.com/garbas/pypi2nix/commit/339aee3b149909430ebe7e3e27b8cf158addaef1
>
> On Tue, Jul 5, 2016 at 2:47 PM, Graham Christensen 
> wrote:
> > I've found myself confused by multiple projects using the same lang2nix
> > name, and big changes in format. One consistent complaint I have is the
> top
> > of the file usually says:
> >
> > // Generated by lang2nix
> >
> > but having more information like a version number and a URL to the
> project
> > would have saved hours of searching and trying different tools. Something
> > like:
> >
> > // Generated by lang2nix v0.1.0
> > // See more at https://github.com/myuser/lang2nix
> >
> > would be a really nice usability adjustment.
> >
> > On Tue, Jul 5, 2016 at 7:36 AM Rok Garbas  wrote:
> >>
> >> we can still keep and old version of npm2nix in nixpkgs for ppl who use
> >> it.
> >> and also a branch with old code could be created, for people that want
> >> pudh bugfixes or develop further (very unlikely).
> >>
> >>
> >> On Tue, Jul 5, 2016 at 11:16 AM, Tomasz Czyż 
> >> wrote:
> >> > Rok,
> >> >
> >> > what about people who are already using previous solution? Why break
> >> > their
> >> > workflows?
> >> >
> >> > 2016-07-05 7:36 GMT+01:00 Rok Garbas :
> >> >>
> >> >> +1 for just keeping the name npm2nix and bumping up the version.
> >> >>
> >> >> i'm not using it on any active project, but i'm going to in the near
> >> >> future.
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Jul 4, 2016 at 10:11 PM, Tobias Pflug 
> >> >> wrote:
> >> >> > Hi Sander,
> >> >> >
> >> >> > sorry for my very late response. I'll make this one brief as I am
> >> >> > sadly
> >> >> > on
> >> >> > my phone.
> >> >> >
> >> >> > I  belong to one of those who tried your new npm2nix and in fact am
> >> >> > already
> >> >> > using it regularly. I am very much in favor of having your
> >> >> > re-engineeering2
> >> >> > branch replacing npm2nix as the de-facto node integration tool.
> >> >> >
> >> >> > I also definitely want to see the current set of auto-generated
> node
> >> >> > packages removed from nix. They are almost exclusively *totally*
> >> >> > outdated.
> >> >> >
> >> >> > Thank you a lot for your continued efforts on this. Working with
> >> >> > npm/node is
> >> >> > annoying but we are better off with your contributions.
> >> >> >
> >> >> > cheers,
> >> >> > Tobi
> >> >> >
> >> >> > On 22 Jun 2016, at 20:24, Sander van der Burg <
> svanderb...@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> > Hello Nix and Node.js users,
> >> >> >
> >> >> > I have been absent for a while in this discussion, but as far as I
> >> >> > know
> >> >> > the
> >> >> > state of the NPM packages in Nixpkgs is still quite bad and despite
> >> >> > some
> >> >> > discussions on the mailing list we have not really come to any
> >> >> > consensus
> >> >> > yet.
> >> >> >
> >> >> > As some of you may know, I have my own re-engineered version of
> >> >> > npm2nix
> >> >> > that
> >> >> > lives in a specific branch in my own personal fork
> >> >> > (https://github.com/svanderburg/npm2nix/tree/reengineering2). A
> few
> >> >> > months
> >> >> > ago, I did some major efforts in getting npm 3.x's behaviour
> >> >> > supported,
> >> >> > which I have documented in this blog post:
> >> >> >
> >> >> >
> >> >> >
> http://sandervanderburg.blogspot.com/2016/02/managing-npm-flat-module-installations.html
> >> >> >
> >> >> > I have been using this reengineering2 branch for all my public and
> >> >> > some
> >> >> > of
> >> >> > my private projects since the beginning of this year, and for me it
> >> >> > seems to
> >> >> > work quite well, despite the fact that some of npm 3.x's flat
> module
> >> >> > installation oddities are still not accurately supported yet.
> >> >> >
> >> >> > I also received a couple of reports from other people claiming that
> >> >> > their
> >> >> > projects work and even encountered some people saying that it
> should
> >> >> > replace
> >> >> > the current npm2nix. :)
> >> >> >
> >> >> > Obviously, I do not want to claim that my implementation is the
> >> >> > perfect
> >> >> > solution as it (for example) is much slower than the vanilla
> npm2nix,
> >> >> > and it
> >> >> > composes the entire set of dependencies in one derivation as
> opposed
> >> >> > to
> >> >> > generating a Nix store path per NPM dependency. (I do this for a
> very
> >> >> > good
> >> >> > reason. For more details, please read my blog post).
> >> >> >
> >> >> > Furthermore, I have also spoken to people that suggested completely
> >> >> > different kinds of approaches in getting NPM supported in a Nix
> >> >> > environment.
> >> >> >
> >> >> > Something that I have not done yet is investigating whether this
> >> >> > reengineered solution could be a potential replacement for the NPM
> >> >> > packages
> >> >> > set in Nixpkgs.
> >

Re: [Nix-dev] Building mesos from git

2016-06-23 Thread Kamil Chmielewski

Hi,

setting zip_safe=False in
https://github.com/apache/mesos/blob/master/src/python/setup.py.in may
solve the issue, like in
https://github.com/noirbizarre/django-eztables/pull/17

--
Kamil

2016-06-23 14:17 GMT+02:00 Maarten Hoogendoorn :

> Hi there,
>
> I want to experiment a bit with some of the features of a unreleased mesos.
>
> I've copied the mesos package definition from nixpkgs to a separate dir,
> and have modified it to point to a git repository. The result is in a
> GitHub repo [1]
>
> The log [2] shows that it compiles all C++ stuff, but fails on creating a
> python egg:
> ValueError: ZIP does not support timestamps before 1980
>
> Makefile:11639: recipe for target 'python/dist/mesos-1.0.0-py2.7.egg' failed
> make[2]: *** [python/dist/mesos-1.0.0-py2.7.egg] Error 1
> make[2]: Leaving directory 
> '/tmp/nix-build-mesos-git-head.drv-0/mesos-d1b681f/src'
> Makefile:3175: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> '/tmp/nix-build-mesos-git-head.drv-0/mesos-d1b681f/src'
> Makefile:762: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> builder for ‘/nix/store/3h0hgqp70x0kzrwsx4v8imvi4g5ay3x4-mesos-git-head.drv’ 
> failed with exit code 2
> error: build of 
> ‘/nix/store/3h0hgqp70x0kzrwsx4v8imvi4g5ay3x4-mesos-git-head.drv’ failed
>
> I could use some tips on how to proceed. I'd like to keep python support
> in there, but I'm also open to some tips on how to disable python builds.
>
> Thanks,
> Maarten
>
>
> [1] https://github.com/moretea/nixops-mesos-git-head
> [2]
> https://raw.githubusercontent.com/moretea/nixops-mesos-git-head/master/log.txt
>
> ___
> 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] Rework goPackages

2016-06-17 Thread Kamil Chmielewski

Hi,

few days ago I started a PR called [WIP] Rework goPackages
https://github.com/NixOS/nixpkgs/pull/16017 which is now on master and can
leads to confusion for everyone creating goPackages before. I was also a
little surprised how fast it was merged but I thought it was the effect of
how many people feel the same pain as me, trying to manage or introduce new
goPackages so there wasn't a lot of discussion there. But now it starts in
few places and I think that this will be better place to make decisions
about Go packaging in Nix.

I want to start with the motivation which led me to this topic. Few months
ago I wanted to introduce Otto (https://www.ottoproject.io/) to Nix. I was
starting with Nix back then i tried to do things as they were in
go-packages.nix.
So I created otto as buildFromGithub[1] and use its bin output in
all-packages.nix[2]. Next nix-build -A otto and I got 23 dependencies
missing[3]. So I started to add dependencies manually doing nix-build -A
otto tens of times because each of them depends on new things that `go
build` tells me only when I add new sources for build... [4]
After many hours of doing nix-build and new edits in go-packages.nix I
ended up with otto done in 400 lines of Nix [5] I don't want do maintain.
Besides new packages I also need to change version of things that were
there before, potentially breaking other things. I can't even image how
many hours of work it'll cost me to update it to new version :( So there no
otto in nixpkgs.
Instead of making otto I've started go2nix[6] prototype where I want to use
Go toolchain because it can find out all transitive dependencies in one go.
It wasn't hard to write a prototype in Go because everthing for it is
there. So after a minutes I could automatically generate a list of all
dependencies that I need to build any Go binary! Next step was to generate
working Nix expression with this list of dependencies that can be used in
goPackages. How hard can it be? :) It turned out that it's impossible to do
this reusing goPackages in its current state. How could I know that:
* github.com/ugorji/go sould be ugorji.go [7]
* gopkg.in/flosch/pongo2.v3 should be pongo2 [8]
* google.golang.org/api should be google-api-go-client [9]
* github.com/odeke-em/google-api-go-client shoul be
odeke-em.google-api-go-client
[10]
* github.com/stathat/go should be stathat [11]
...

So there were 2 ways of dealing it:
* generate new goPackage without any imports from go-packages.nix and
abandon it completely
* change go-packages.nix into something that can be readable for something
that knows how packages are named in Go land
I thought that go-packages.nix, python-packages.nix .. says that we
want to reuse common dependencies somewhere but it should be possible to
override some of them if needed. And that was the beginning of [WIP] Rework
goPackages with go-packages.nix "converted" into libs.json that was also
influenced by temptation to make it possible to automate future updates[12].

As a troublemaker I want to involve all interested people to find out what
next moves we should do to make:
* master branch at least as usable as it was before rework
* working with Nix and Go the best experience for both Nixers and Gophers

So lets start with the first one. Most comments I see is related to
libs.json.
Does it mean we want go-packages.nix but in form that can be generated and
imported like libs.json or we don't want it at all moving all the
dependencies to separate derivations? Or maybe we want go-packages.nix as
it was before?

--
Kamil

[1]
https://github.com/kamilchm/nixpkgs/pull/3/files#diff-8631dcd3e45d5f2ceaedeb96a23bee6fR2214
[2]
https://github.com/kamilchm/nixpkgs/pull/3/files#diff-036410e9211b4336186fc613f7200b12R12219
[3]
https://gist.github.com/kamilchm/bec9483a111babafe965abcec9efb013#file-nix-build-a-otto
[4] https://gist.github.com/kamilchm/bec9483a111babafe965abcec9efb013
[5] https://github.com/kamilchm/nixpkgs/pull/3
[6] https://github.com/kamilchm/go2nix
[7]
https://github.com/kamilchm/nixpkgs/blob/otto-before/pkgs/top-level/go-packages.nix#L683
[8]
https://github.com/kamilchm/nixpkgs/blob/otto-before/pkgs/top-level/go-packages.nix#L2070
[9]
https://github.com/kamilchm/nixpkgs/blob/otto-before/pkgs/top-level/go-packages.nix#L861
[10]
https://github.com/kamilchm/nixpkgs/blob/otto-before/pkgs/top-level/go-packages.nix#L872
[11]
https://github.com/kamilchm/nixpkgs/blob/otto-before/pkgs/top-level/go-packages.nix#L2700
[12] https://github.com/NixOS/nixpkgs/pull/13819
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Running nix-build on Circle CI

2016-06-15 Thread Kamil Chmielewski

It works.
Awesome, thx!


--
Kamil

2016-06-15 22:27 GMT+02:00 Daniel Hlynskyi :

> Have you tried
> nix-channel --add https://nixos.org/channels/nixos-unstab
> le nixpkgs
> ?
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Running nix-build on Circle CI

2016-06-15 Thread Kamil Chmielewski

Hi,

I want to use nix-build as a build tool for go2nix. After bad experience I
have with Travis that fails for many nixpkgs PRs I choose Circle CI.
Everything worked fine when I not needed any special nixpkgs branch or
channel with these simple steps:

- sudo mkdir -p /nix
- sudo chown ubuntu /nix
- curl https://nixos.org/nix/install | sh
- echo "source ~/.nix-profile/etc/profile.d/nix.sh" >> ~/.circlerc
- nix-build

But after a recent changes in buildGoPackage I need to use unstable channel
now. I tried to add few lines before nix-build like:

- nix-channel --add https://nixos.org/channels/nixos-unstable
- nix-channel --update
- nix-env -u

but id doesn't change anything in build result that is saying it can't find
buildGoPackage https://circleci.com/gh/kamilchm/go2nix/30

What else can I do?

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

Re: [Nix-dev] Using gradle in netbeans

2016-06-14 Thread Kamil Chmielewski

Are you using gradlew wrapper? If so, try to remove /home/john/.gradle/,
install gralde from nix or use nix-shell -p gradle and use gradle to build
your project instead of provided ./gradlew.
I don't use Netbeans but there should be some option to use global gradle
instead of gradle wrapper.

--
Kamil


2016-06-14 14:52 GMT+02:00 moaxcp :

> Hello, I'm new to nixos and I'm having a problem getting gradle to work in
> netbeans. Somewhere along the way gradle has a .so file that cannot link to
> libstdc++.so. Is there anything I can do to fix this? Here is the error:
>
> Issue 1
> 
>
>   Requested project: /home/john/NetBeansProjects/awstest
>
>   Stack trace:
> org.gradle.tooling.GradleConnectionException: Could not create an
> instance of Tooling API implementation using the specified Gradle
> distribution '
> https://services.gradle.org/distributions/gradle-2.14-bin.zip'.
> at
> org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.create(DefaultToolingImplementationLoader.java:95)
> at
> org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:43)
> at
> org.gradle.tooling.internal.consumer.loader.SynchronizedToolingImplementationLoader.create(SynchronizedToolingImplementationLoader.java:42)
> at
> org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.onStartAction(LazyConsumerActionExecutor.java:99)
> at
> org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:82)
> at
> org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58)
> at
> org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38)
> at
> org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at
> org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
> at
> org.gradle.tooling.internal.consumer.DefaultModelBuilder.get(DefaultModelBuilder.java:49)
> at
> org.netbeans.gradle.project.model.GradleModelLoader.loadModelWithProgress(GradleModelLoader.java:558)
> at
> org.netbeans.gradle.project.model.GradleModelLoader.fixProjectLoadKey(GradleModelLoader.java:362)
> at
> org.netbeans.gradle.project.model.GradleModelLoader.access$700(GradleModelLoader.java:71)
> at
> org.netbeans.gradle.project.model.GradleModelLoader$6.run(GradleModelLoader.java:391)
> at
> org.netbeans.gradle.project.tasks.GradleDaemonManager.runNonBlockingGradleTask(GradleDaemonManager.java:35)
> at
> org.netbeans.gradle.project.tasks.GradleDaemonManager.access$100(GradleDaemonManager.java:22)
> at
> org.netbeans.gradle.project.tasks.GradleDaemonManager$2.execute(GradleDaemonManager.java:125)
> at
> org.jtrim.concurrent.AbstractTaskExecutorService$FunctionWrapper.execute(AbstractTaskExecutorService.java:270)
> at
> org.jtrim.concurrent.AbstractTaskExecutorService$TaskOfAbstractExecutor.execute(AbstractTaskExecutorService.java:340)
> at
> org.jtrim.concurrent.Tasks$RunOnceCancelableTask.execute(Tasks.java:342)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$QueuedItem.runTask(SingleThreadedExecutor.java:919)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$QueuedItem.access$1200(SingleThreadedExecutor.java:898)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$Impl$Worker.executeTask(SingleThreadedExecutor.java:815)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$Impl$Worker.processQueue(SingleThreadedExecutor.java:827)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$Impl$Worker.run(SingleThreadedExecutor.java:861)
> at
> org.jtrim.concurrent.SingleThreadedExecutor$Impl$1.run(SingleThreadedExecutor.java:453)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: net.rubygrapefruit.platform.NativeException: Failed to load
> native library 'libnative-platform.so' for Linux amd64.
> at
> net.rubygrapefruit.platform.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:49)
> at net.rubygrapefruit.platform.Native.init(Native.java:55)
> at
> org.gradle.internal.nativeintegration.services.NativeServices.initialize(NativeServices.java:74)
> at
> org.gradle.internal.nativeintegration.services.NativeServices.initialize(NativeServices.java:60)
> at
> org.g

[Nix-commits] [NixOS/nixpkgs] d73f5d: icon-lang, xgeometry-select: FIX accidental remove...

2016-06-10 Thread Kamil Chmielewski

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d73f5d69930fe7293f53548c682cc2ef6711cfbf
  
https://github.com/NixOS/nixpkgs/commit/d73f5d69930fe7293f53548c682cc2ef6711cfbf
  Author: Kamil Chmielewski 
  Date:   2016-06-10 (Fri, 10 Jun 2016)

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

  Log Message:
  ---
  icon-lang, xgeometry-select: FIX accidental remove after rebase in 
https://github.com/NixOS/nixpkgs/pull/16017 (#16121)


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

Re: [Nix-dev] How to use .nixpkgs/config.nix?

2016-06-06 Thread Kamil Chmielewski

Did you see nix pills by Lehtalman
http://lethalman.blogspot.it/2014/07/nix-pill-1-why-you-should-give-it-try.html
?

--
Kamil

2016-06-06 21:19 GMT+02:00 Mateusz Czaplinski :

> On Mon, Jun 6, 2016 at 11:30 AM, Kamil Chmielewski 
> wrote:
> > The '_pkgs : with _pkgs; {' part comes from
> > https://nixos.org/wiki/Howto_keep_multiple_packages_up_to_date_at_once.
>
> Yes, I've noticed. I know it works, and I'm very grateful to you for
> publicizing your solution in one of the "declarative user config"
> issues, so that I could adopt it. But I'd like to understand what it
> does and how it works. I've seen packageOverrides written in this way,
> as will as in other ways (e.g. the Nix manual uses 'rec' and doesn't
> use 'with'). I'd like to understand what's going on here, why is it
> needed, why sometimes one form sometimes other, and how and when to
> use one or the other. I tried to explore it with the manuals in hand,
> but to no success. So I thought maybe someone could help me with this?
>
> As to other perceived complications (esp. 'buildEnv'), I seem to have
> worked through them already,
>
> Thanks,
> /Mateusz.
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to use .nixpkgs/config.nix?

2016-06-06 Thread Kamil Chmielewski

Hi,

what did you find to be complicated in my config?
I started to use NixOS to have fully declarative user environment and it
was my first nix code, copied from wiki and diffrent places on github. It
may require some refactorings but it works for almost a year without big
changes so I don't have a lot of motivation to make it better :/ But I can
find some time to some changes if this will make it more approachable for
newcomers.
The '_pkgs : with _pkgs; {' part comes from
https://nixos.org/wiki/Howto_keep_multiple_packages_up_to_date_at_once.

--
Kamil


2016-06-05 15:46 GMT+02:00 Mateusz Czaplinski :

> Hi!
> I'd like to have my home dir & per-user set of packages managed
> declaratively. I've seen some suggestions, from which I seem to
> believe I could try to do that using .nixpkgs/config.nix. Is that
> possible? how could I do that the simplest way?
>
> I'm new to Nix/NixOS. I've set up a simple NixOS install on a laptop,
> but I'm having trouble understanding how to use local config.nix vs.
> global configuration.nix. The manuals seem very sparse on config.nix
> to me. The config.nix from Kamil Chmielewski [1] seems somewhat
> acceptable to me at first sight, but I still don't get why config.nix
> seems so much more complicated than configuration.nix? Is it possible
> to make it simpler?
>
> I'd like to start with a simplest config which would let me add some
> packages which would be available for my user immediately after login
> (also when logging in straight to an X session).
>
> [1] https://github.com/NixOS/nixpkgs/issues/1750#issuecomment-186385710
>
> Thanks,
> /Mateusz Czapliński.
> ___
> 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] upgrading packer

2016-05-13 Thread Kamil Chmielewski

A little sidenote ;). I want to make easier to create new or update
existing Go apps and its dependencies with tools like go2nix.
I need a feedback for my proposal
https://github.com/NixOS/nixpkgs/pull/13819#issuecomment-214992581
There'e a PoC of 2 packages generated with modified go2nix that shares same
dependencies in json file.

--
Kamil


2016-05-13 10:44 GMT+02:00 zimbatm :

> Sorry, I made it sound more easy that it was. For some reason I thought
> they had vendored all the dependencies.
>
> I took a stab at the update yesterday and here is the PR:
> https://github.com/NixOS/nixpkgs/pull/15426/files
>
> What I had to do was checkout packer at the specific tag, run `godep
> restore` and then `go2nix save`. Copy the generated `default.nix` to
> overwrite the `deps.nix` file. And then the tricky part was to get packer
> to build properly using all of this since they have a custom build pipeline.
>
> On Thu, 12 May 2016 at 17:36 Samuel  wrote:
>
>> What do you mean by upgrading packer itself? If I just bump the packer
>> reference in deps.nix, that cannot update the rest of the dependencies
>> (they are part of the expression, so they need to be evaluated before
>> building). Am I misunderstanding your suggestion?
>>
>>
>> On 11 May 2016 at 09:49, zimbatm  wrote:
>> > Did you try just upgrading packer itself? I believe those dependencies
>> are
>> > included during the build now
>> >
>> >
>> > On Wed, 11 May 2016 08:39 Samuel,  wrote:
>> >>
>> >> Hi,
>> >>
>> >> I took a brief look into upgrading packer in nixpkgs, but it seems
>> >> that it has a long list of hardcoded dependencies
>> >>
>> >> (
>> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/packer/deps.nix
>> ).
>> >> Is there any automation to bump those or is it a manual process?
>> >>
>> >> In the meanwhile I've written an expression that downloads the
>> >> official binaries:
>> >>
>> >>
>> >>
>> https://github.com/samuelrivas/monorepo/blob/packer/nix/pkgs/development/tools/packer/default.nix
>> >>
>> >> But I assume that's not a change that I should pull request. Just let
>> >> me know otherwise.
>> >>
>> >> Best
>> >> --
>> >> Samuel
>> >> ___
>> >> nix-dev mailing list
>> >> nix-dev@lists.science.uu.nl
>> >> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>>
>> --
>> Samuel
>>
>
> ___
> 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] Bootable ISO with automated NixOS installer

2016-05-06 Thread Kamil Chmielewski

Hi,

I've created nixos config for one of my digital signage project that boots
directly to brower. It works great when I use
config.system.build.vm/virtualBoxOVA/isoImage and run it from that image.
But the thing is that I need to produce some kind o bootable installer that
will install the same NixOS automatically (or after few "clicks") on
different computers that may not have network connection.
I've tried with installation-cd-base.nix providing my nixos config as
isoImage.contents but it downloads and builds many packages when I run
nixos-install.
Any clues how to make this kind of installer?

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

Re: [Nix-dev] bind and complete not found in nix-shell

2015-11-12 Thread Kamil Chmielewski

I found it. It was python virtualenvwrapper sourced from my .bashrc. It
worked well in user shell but cause problems in nix-shell.
Thank you all for your aid.

Cheers,
Kamil

2015-11-12 2:49 GMT+01:00 Anderson Torres :

> 2015-11-11 19:19 GMT-02:00 Kamil Chmielewski :
> >> Try to install pkgs.bashInteractive!
> >
> >
> > Same with bashInteractive installed :/
> >
> >>
> >> > If you think ~/.nixpkgs/config.nix is relevant, you could try moving
> >> > that file somewhere else to see if it was the problem.
> >
> >
> > It didn't help.
> >
> >>
> >> > If that doesn't work, can you give an example of a command that
> >> > doesn't work and the error it produces?
> >
> >
> > The simplest I'm trying  now is just nix-shell -A hello
> > $ nix-shell ~/nixpkgs -A hello
>
> bind and complete are Bash builtins as far as I can remember. They are
> activated in build time. Well, I clearly remember that when I have a
> similar problem I just downloaded bashInteractive.
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] bind and complete not found in nix-shell

2015-11-11 Thread Kamil Chmielewski

>
> Try to install pkgs.bashInteractive!
>

Same with bashInteractive installed :/


> > If you think ~/.nixpkgs/config.nix is relevant, you could try moving
> > that file somewhere else to see if it was the problem.
>

It didn't help.


> > If that doesn't work, can you give an example of a command that
> > doesn't work and the error it produces?


The simplest I'm trying  now is just nix-shell -A hello
$ nix-shell ~/nixpkgs -A hello
bind: command not found
bind: command not found
bind: command not found
bind: command not found
bind: command not found
complete: command not found
complete: command not found
complete: command not found
complete: command not found
complete: command not found
complete: command not found
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] bind and complete not found in nix-shell

2015-11-08 Thread Kamil Chmielewski

Hi,

when I try to use nix-shell I'm getting errors about missing bind and
complete commands:
bind: command not found
complete: command not found

It was working few weeks ago and probably it's an effect of some other
changes I made in my config. Not directly doing something with bind and
complete and I can't find out the exact place where these commands are used.
Any hints how to debug this kind of problems with nix-shell?

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

[Nix-dev] nix-hash/NAR specification?

2015-10-26 Thread Kamil Chmielewski

Hi,

I want to write simple tool to convert golang environments into Nix
derivations. Something that I can use same way as godep but producing Nix
derivation, similar to those created with go2nix.
I implemented small PoC that reads all packages from $GOPATH/src to
discover theirs repos and current revisions.
One final thing I need is package hash. I don't want to use nix-prefetch
because I  already have all sources there. I can't run nix-hash on sources
with .git directories in it.
I thought I can write nix-hash in Go to keep my code self-contained and
concise.
I found https://gist.github.com/jbeda/5c79d2b1434f0018d693 and saw Eelco
PhD thesis but I don't know if it's still valid?
So there's my question :) Is there any official nix-hash/NAR specification
that I can use?
Is nix-hash just a checksum of path archived with NAR?

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

Re: [Nix-dev] Building portable linux binaries on NixOS

2015-10-09 Thread Kamil Chmielewski

Unfortunately, I can't make patchelf works:
$ patchelf --set-interpreter /lib/ld-linux-x86-64.so.2 go-app
patchelf: patchelf.cc:693: void ElfFile::rewriteSectionsExecutable() [with
Elf_Ehdr = Elf64_Ehdr; Elf_Phdr = Elf64_Phdr; Elf_Shdr = Elf64_Shdr;
Elf_Addr = long unsigned int; Elf_Off = long unsigned int; Elf_Dyn =
Elf64_Dyn; Elf_Sym = Elf64_Sym]: Assertion `(off_t) rdi(hdr->e_shoff) >=
startOffset' failed.
Aborted

I try to buiild it in docker for now.
Thx for sugestions.

Cheers,
Kamil

2015-10-09 7:50 GMT+02:00 Bryan Gardiner :

> On Thu, 8 Oct 2015 00:03:23 +0200
> Kamil Chmielewski  wrote:
>
> > 2015-10-07 20:44 GMT+02:00 Bryan Gardiner :
> >
> > > > your shell does not find "./go-app".
> > > > What does ls -l say?
> > >
> >
> > The file path is right and exists for sure.
> >
> >
> > > Most likely Kamil is in the right directory, and this is just a known
> > > quirk: bash tries to exec the program, the exec fails because the
> > > binary's interpreter is set incorrectly, and bash incorrectly
> > > interprets the failure as the program not existing.  See
> > > https://nixos.org/patchelf.html (although, there is an open bug about
> > > patchelf not working on Go binaries, see
> > > https://github.com/NixOS/patchelf/issues/66).
> >
> > Looks like the issue. Any ideas what to do?
>
> I'm not sure if you've tried patchelf and hit that bug, or if you
> haven't...  If you haven't, then try something like the following:
>
> $ patchelf --set-interpreter /lib/ld-linux.so.2 go-app
> $ patchelf --set-rpath /lib:/usr/lib:/usr/local/lib go-app
> $ ./go-app  # (on Ubuntu)
>
> You should consult /etc/ld.so.conf on Ubuntu for the correct library
> directories (not on Ubuntu here, so I can't see what how it does
> things).
>
> I think though, wouldn't the correct thing to do (after setting the
> interpreter) actually be to *remove* the RPATH from the binary to have
> it work on non-NixOS, using the normal system library lookup?  I don't
> see a --remove-rpath option on patchelf though.  I can't recall
> whether RPATH inhibits normal lookup directories, if not then you
> wouldn't need to change it, or you could just set it to be empty...
> See ld.so(8).
>
> Cheers,
> Bryan
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Building portable linux binaries on NixOS

2015-10-07 Thread Kamil Chmielewski

2015-10-07 20:44 GMT+02:00 Bryan Gardiner :

> > your shell does not find "./go-app".
> > What does ls -l say?
>

The file path is right and exists for sure.


> Most likely Kamil is in the right directory, and this is just a known
> quirk: bash tries to exec the program, the exec fails because the
> binary's interpreter is set incorrectly, and bash incorrectly
> interprets the failure as the program not existing.  See
> https://nixos.org/patchelf.html (although, there is an open bug about
> patchelf not working on Go binaries, see
> https://github.com/NixOS/patchelf/issues/66).
>

Looks like the issue. Any ideas what to do?


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

Re: [Nix-dev] Building portable linux binaries on NixOS

2015-10-07 Thread Kamil Chmielewski

ldd go-app
linux-vdso.so.1 (0x7ffdeab7)
libpthread.so.0 =>
/nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libpthread.so.0
(0x7f9ae89e)
libc.so.6 =>
/nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libc.so.6
(0x7f9ae864)

/nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/ld-linux-x86-64.so.2
(0x7f9ae8bfd000)


2015-10-07 19:21 GMT+02:00 zimbatm :

> What is the output of `ldd go-app` ?
>
> Go binaries should be static unless you're using gccgo.
>
> On Wed, 7 Oct 2015 18:18 Kamil Chmielewski  wrote:
>
>> Hi,
>>
>> I'm trying to build Linux binaries from Go source code, but when I move
>> it to Ubuntu and I try to run it there all I get is:
>> -bash: ./go-app: No such file or directory
>>
>> Is there any simple way to patch Nix binary and make it runnable under
>> other distros?
>>
>> Cheers,
>> Kamil
>> ___
>> 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] Building portable linux binaries on NixOS

2015-10-07 Thread Kamil Chmielewski

Hi,

I'm trying to build Linux binaries from Go source code, but when I move it
to Ubuntu and I try to run it there all I get is:
-bash: ./go-app: No such file or directory

Is there any simple way to patch Nix binary and make it runnable under
other distros?

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

Re: [Nix-dev] /etc/nixos/configuration.nix vs ~/.nixpkgs/config.nix

2015-06-29 Thread Kamil Chmielewski

Thanks for your replies.
I've started to write nixpkgs with my dotfiles, and install it to
$out/dottfiles.
Then I make links to ~/.nix-profile/dotfiles/.dotfiles in my $HOME with one
commend.
Works for me now :)
I'll check your solutions to see how can I make it better.

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

[Nix-dev] /etc/nixos/configuration.nix vs ~/.nixpkgs/config.nix

2015-06-29 Thread Kamil Chmielewski

Hi,

I'm trying to setup NixOS on my laptop and I feel really confused with this
2 config files.
I would like to have base system configuration like hardware and system
services in /etc/nixos and other software and user configuration in
~/.nixpkgs.
I'm stuck on custom gtk theme now. I don't want to install my gtk theme
system wide, but in my user scope only. I searched everywhere and I can't
find an example ~/.nixpkgs that will setup my env analogous to Deian conf:
1. gtk theme in ~/.themes
2. custom ~/.gtkrc-2.0

I had a repo of dotiles for debian with many other things like .gitconfig,
.vimrc, .profile 
How to rewrite it to NixOS?

I really appreciate NixOS but without any example with dotfiles I can't
become its user :/

Best regards,
Kamil
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

46 matches

Mail list logo