[Nix-commits] [NixOS/nixpkgs] fa6fd3: github/pr-template: Add note about NixOS tests

[aszlig]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: fa6fd34fcca07c0762ef3bc44962e2dc49937454
  
https://github.com/NixOS/nixpkgs/commit/fa6fd34fcca07c0762ef3bc44962e2dc49937454
  Author: aszlig 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M .github/PULL_REQUEST_TEMPLATE.md

  Log Message:
  ---
  github/pr-template: Add note about NixOS tests

On several occasions I've seen people bumping packages which have NixOS
tests but without actually running them.

While this probably won't prevent such occasions entirely, at least it
serves as an additional checklist item so contributors don't forget
about these tests.

Signed-off-by: aszlig 


  Commit: 63fb845fcf6ea02db7933f503948a01fb2f6c2a4
  
https://github.com/NixOS/nixpkgs/commit/63fb845fcf6ea02db7933f503948a01fb2f6c2a4
  Author: aszlig 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M pkgs/applications/virtualization/virtualbox/hardened.patch

  Log Message:
  ---
  virtualbox: Rebase hardened.patch on top of 5.1.22

The merge of the version bump in
6fb9f892382b4b091fc9edcae00e2eb4c0729bda didn't take care of our patch
for the hardening mode and thus enabling VirtualBox without also
force-disabling hardening mode will result in a build error.

While the patch is largely identical with the old version, I've removed
one particular change around the following code:

if (pFsObjState->Stat.st_mode & S_IWOTH)
  return supR3HardenedSetError3(VERR_SUPLIB_WORLD_WRITABLE, pErrInfo,
"World writable: '", pszPath, "'");

In the old version of the patch we have checked whether the path is
within the Nix store and suppressed the error return if that's the case.

The reason why I did that in the first place was because we had a bunch
of symlinks which were writable.

In VirtualBox 5.1.22 the code specifically checks whether the file is a
symlink, so we can safely drop our change.

Tested via all of the "virtualbox" NixOS VM subtests and they now all
succeed.

Signed-off-by: aszlig 


Compare: https://github.com/NixOS/nixpkgs/compare/6fb9f892382b...63fb845fcf6e___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] f4b4ed: coreutils: fix tests depending on setuid/setgid bi...

[Franz Pletz]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: f4b4edc290377a402ad949c6c178785bebd6efe8
  
https://github.com/NixOS/nixpkgs/commit/f4b4edc290377a402ad949c6c178785bebd6efe8
  Author: Franz Pletz 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M pkgs/tools/misc/coreutils/default.nix

  Log Message:
  ---
  coreutils: fix tests depending on setuid/setgid bits

(cherry picked from commit 6a850d2b11f22a22729b49f012fc26ff3c602f3f)


  Commit: b972c0e6669ff26d8f91720ba1aa7b0641569696
  
https://github.com/NixOS/nixpkgs/commit/b972c0e6669ff26d8f91720ba1aa7b0641569696
  Author: Franz Pletz 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M pkgs/servers/mail/exim/default.nix

  Log Message:
  ---
  exim: patch CVE-2017-1000369 (stack clash)

(cherry picked from commit 16aa92305bf8141c71cd44bc9af688e246df84df)


  Commit: 6c026fe3d0e93f5398907f37ed79eb0810dbf802
  
https://github.com/NixOS/nixpkgs/commit/6c026fe3d0e93f5398907f37ed79eb0810dbf802
  Author: Franz Pletz 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M pkgs/os-specific/linux/kernel/patches.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  linux: patch CVE-2017-1000364 (stack clash)

(cherry picked from commit aab71b31d5030bea94804d3677a3ffbc60e1876a)


  Commit: b049392e16a98890dca2ab328a8f0fab1631b841
  
https://github.com/NixOS/nixpkgs/commit/b049392e16a98890dca2ab328a8f0fab1631b841
  Author: Franz Pletz 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
A pkgs/development/libraries/glibc/CVE-2017-1000366-rtld-LD_AUDIT.patch
A 
pkgs/development/libraries/glibc/CVE-2017-1000366-rtld-LD_LIBRARY_PATH.patch
A pkgs/development/libraries/glibc/CVE-2017-1000366-rtld-LD_PRELOAD.patch
M pkgs/development/libraries/glibc/common.nix

  Log Message:
  ---
  glibc: patch CVE-2017-1000366 (stack clash)

(cherry picked from commit 2296bf394ec419e111fd0ca80e9000fb819980da)


Compare: https://github.com/NixOS/nixpkgs/compare/9b948ea439dd...b049392e16a9___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] c4a486: virtualbox: 5.1.18 -> 5.1.22

[Tim Steinbach]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: c4a48600bf1441fdba94cee09402663763bee895
  
https://github.com/NixOS/nixpkgs/commit/c4a48600bf1441fdba94cee09402663763bee895
  Author: Pascal Bach 
  Date:   2017-04-30 (Sun, 30 Apr 2017)

  Changed paths:
M pkgs/applications/virtualization/virtualbox/default.nix
M pkgs/applications/virtualization/virtualbox/guest-additions/default.nix

  Log Message:
  ---
  virtualbox: 5.1.18 -> 5.1.22


  Commit: 6fb9f892382b4b091fc9edcae00e2eb4c0729bda
  
https://github.com/NixOS/nixpkgs/commit/6fb9f892382b4b091fc9edcae00e2eb4c0729bda
  Author: Tim Steinbach 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/virtualization/virtualbox/default.nix
M pkgs/applications/virtualization/virtualbox/guest-additions/default.nix

  Log Message:
  ---
  Merge pull request #25368 from bachp/virtualbox-5.1.22

virtualbox: 5.1.18 -> 5.1.22


Compare: https://github.com/NixOS/nixpkgs/compare/4e08459f9b98...6fb9f892382b___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 4e0845: linux-hardened-copperhead: 4.11.6c -> 4.11.6d

[Tim Steinbach]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 4e08459f9b98200949df65f2a4805e56a8d6b12e
  
https://github.com/NixOS/nixpkgs/commit/4e08459f9b98200949df65f2a4805e56a8d6b12e
  Author: Tim Steinbach 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/os-specific/linux/kernel/linux-hardened-copperhead.nix

  Log Message:
  ---
  linux-hardened-copperhead: 4.11.6c -> 4.11.6d


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

[Nix-commits] [NixOS/nixpkgs] 073735: openldap: 2.4.44 -> 2.4.45

[Tim Steinbach]

  Branch: refs/heads/staging
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 0737359dd083781ae103595daa31809f70f9ef65
  
https://github.com/NixOS/nixpkgs/commit/0737359dd083781ae103595daa31809f70f9ef65
  Author: Tim Steinbach 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/libraries/openldap/default.nix

  Log Message:
  ---
  openldap: 2.4.44 -> 2.4.45


  Commit: 56761c9b3d6f829a4f80e02d18fff30e8a6af1eb
  
https://github.com/NixOS/nixpkgs/commit/56761c9b3d6f829a4f80e02d18fff30e8a6af1eb
  Author: Tim Steinbach 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

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

  Log Message:
  ---
  minikube: 0.19.1 -> 0.20.0


Compare: https://github.com/NixOS/nixpkgs/compare/c3a8595276ee...56761c9b3d6f___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 0030c6: kdeFrameworks, plasma5: fix setup hooks

[Thomas Tuegel]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 0030c6610353b3706fe77d4cce06f1905a4aec43
  
https://github.com/NixOS/nixpkgs/commit/0030c6610353b3706fe77d4cce06f1905a4aec43
  Author: Thomas Tuegel 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/desktops/plasma-5/default.nix
M pkgs/development/libraries/kde-frameworks/default.nix

  Log Message:
  ---
  kdeFrameworks, plasma5: fix setup hooks

The setup hooks for many kdeFrameworks and plasma5 packages were erroneously
running before $outputDev was set. This lead to .dev outputs being propagated
into the user environment.


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

[Nix-commits] [NixOS/nixpkgs] 8f970d: ghcHEAD: Actually split docs into their own output

[John Ericson]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 8f970d09fe8e895b6bb7dbf52f80411a45504b19
  
https://github.com/NixOS/nixpkgs/commit/8f970d09fe8e895b6bb7dbf52f80411a45504b19
  Author: John Ericson 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/compilers/ghc/head.nix

  Log Message:
  ---
  ghcHEAD: Actually split docs into their own output

I put `outputs = ...` in the wrong spot in the last PR, oops. Sorry
about that.


  Commit: f571ad45955c21ac5b44820231d4c07867ac3564
  
https://github.com/NixOS/nixpkgs/commit/f571ad45955c21ac5b44820231d4c07867ac3564
  Author: John Ericson 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/compilers/ghc/head.nix

  Log Message:
  ---
  Merge pull request #26775 from obsidiansystems/ghc-head-docs

ghcHEAD: Actually split docs into their own output


Compare: https://github.com/NixOS/nixpkgs/compare/aba574c4faee...f571ad45955c___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] 5 somewhat related questions

[Judson Lester]

Klaas,

First, welcome to Nix! I hope you'll enjoy it as much as I've been.

Second, your questions seem like prime additions to
https://github.com/nixos-users/wiki/wiki/Documentation-Gaps which I hope
will inform future version of the Nix manuals.

I'll do my best to share my understanding vis-a-vis your questions, but
they highlight weaknesses in my own understanding as well.

On Thu, Jun 22, 2017 at 11:41 AM Klaas van Schelven 
wrote:

> Hello Nixians,
>
> I've installed NixOs a number of days ago. So far I really like it!
>
> I've read the documentation I could find, but I'm left with a number of
> questions; not so much "how to do X" but rather of a slightly more
> philosphofical (or cultural, a.k.a. "best practices") nature. I hope
> someone can enlighten me on the "Nix Way".
>
> 1. In NixOs /etc/nixos/configuration.nix is the single configuration file
> that determines the state of the system as a whole. How does this file
> relate to the existence of the nix-env command, either executed as root or
> by a single non-privileged user? In particular, I would assume that any
> nix-env is undone by the time the system is rebuilt from the configuration
> file. Assuming this is the case: should the usage of nix-env not be
> actively discouraged in NixOs? (perhaps it is, and I simply did not find
> the reference)
>
> The products of runinng nix-env --install live in profiles (as, in fact,
do nixos-rebuilds) - there's a diagram here
http://nixos.org/nix/manual/#sec-profiles that I found useful for
understanding how profiles work. Specificially, every user has their own
"~/.nix-profiles" directory, and the system as a whole has a collection of
profiles. System and user profiles are blended, using Unix pathing
mechanisms. If, for example, you check your PATH, you'll see references to
/home/username/.nix-profile/bin and /run/current-system/sw/bin.

nix-env --install is incredibly convenient to quickly install a program you
need in the moment. Even better is when the "not installed" warning are
working properly (which relies on your channel etc) and you can copy and
paste a nix-env command to get the tool you need _right then_, and take a
little maintenance time later to "purify" things.

I've found it useful from time to time to do a nix-env -q, and migrate the
list of installed packages to nix configuration.nix, and then delete my
local installs along the way. I sort of wish that there were a mechanical
way to do this, but it'd involve editing configuration.nix automatically
and triggering nixos-rebuild, which I'm loath to undertake myself.

Admittedly, there is some potential for confusion involved when you've
nix-env'd a package, since you e.g. won't see it update when nixos-build is
run. Also beware interactions like dmenu or neovim installed in one place
and programs or plugins installed in another.

2. (Context: Assuming for a moment there _is_ in fact a use-case for
> nix-env; e.g. the scenario where you're not running NixOs, but are using
> Nix on top of another distribution). nix-env uses an "imperative style" of
> manipulating your environment, i.e. using a sequence of commands in a
> particular order. I understand that after each succesful manipulation the
> _resulting_ environment becomes available as a separate generation. As far
> as I understand there's even a "half-product", the so called "derivation"
> that is available per generation, although I did not study those yet. My
> question is, however, whether the original commands that led to these
> constructions can somehow be retrieved. The reason for this question is the
> observation that the sequence of nix-env (and potentially other similar)
> commands can be seen as a transactional log that could simply be replayed
> to reconstruct the resulting generations (assuming that the commands fully
> express the information needed to construct the associated environments;
> this assumption might not actually hold in practice. Question 2b: does the
> assumption hold?).
>

 That intuition holds modulo your Q3 - replaying a sequence of nix-env
commands would only reproduce the same generations if a) the states of all
channels involved were retained (i.e. you'd need to know which
nixpkgs-stable you installed from with each command) and b) all the builds
were reproduce-able or cached. Nix assumes reproduce-able builds, and so
retains the outcomes of building derivations based on a digest of the
derivation itself - but if you replayed the same nix-env commands from
scratch, you might get (trivially) different outcomes.

>
> 3. In the scenario where I use the single configuration file
> /etc/nixos/configuration.nix but I'm also subscribed to a channel, the
> state of this channel may influence the outcome of nixos-rebuild (This is
> by design, it allows us to stay up to date with e.g. security updates). The
> consecutive states of the channel, as seen by my system when rebuilding,
> are valuable pieces of information in their own 

[Nix-commits] [NixOS/nixpkgs] d1b9c9: erlang: refactor: build packages per Erlang/OTP.

[Daiderd Jordan]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: d1b9c9d2cddf2e57964fde7e4f468c8767a77b3b
  
https://github.com/NixOS/nixpkgs/commit/d1b9c9d2cddf2e57964fde7e4f468c8767a77b3b
  Author: Gleb Peregud 
  Date:   2017-06-19 (Mon, 19 Jun 2017)

  Changed paths:
M pkgs/development/beam-modules/build-hex.nix
M pkgs/development/beam-modules/default.nix
M pkgs/top-level/all-packages.nix
M pkgs/top-level/beam-packages.nix

  Log Message:
  ---
  erlang: refactor: build packages per Erlang/OTP.

This change introduces a fixpoint, which allows to do deep override when
building packages defined in pkgs/development/beam-modules/default.hex.
This allows to provide beam.packages.erlang{,R16,R17,R18,R19} which
contains the same packages built with different Erlang/OTP versions.

Top-level attribute beamPackages points at beam.packages.erlangR18, the
same applies to other top-level Erlang packages.

TODO:
- beam.packages.erlang{R16,R17} is almost useless, since rebar/rebar3
  does not build using these versions;
- all packages in beam.packages which use buildMix are actually built
  with erlangR18;
- update documentation.


  Commit: f66b0186dc9764b83ad76f9dcaec341b0f6f83a0
  
https://github.com/NixOS/nixpkgs/commit/f66b0186dc9764b83ad76f9dcaec341b0f6f83a0
  Author: Gleb Peregud 
  Date:   2017-06-19 (Mon, 19 Jun 2017)

  Changed paths:
M pkgs/development/tools/build-managers/rebar3/rebar3-nix-bootstrap

  Log Message:
  ---
  erlang: fix rebar3-nix-bootstrap in Erlang < R18.


  Commit: 7797e1a1dda661476dbb312b1f26896d32831ef5
  
https://github.com/NixOS/nixpkgs/commit/7797e1a1dda661476dbb312b1f26896d32831ef5
  Author: Gleb Peregud 
  Date:   2017-06-19 (Mon, 19 Jun 2017)

  Changed paths:
M pkgs/development/beam-modules/default.nix
M pkgs/development/beam-modules/lib.nix
M pkgs/top-level/beam-packages.nix

  Log Message:
  ---
  erlang: put Elixir/LFE into per-OTP packageset.

This makes beam.package.erlangR19.abnf to be actually built with R19,
instead of the default R18. It means that Elixir and LFE are provided in
two versions, one built with R18 and with R19.

Please note that Elixir does not build with R16 and R17 - trying to
access beam.packages.erlang{R16,R17}.elixir will throw an error.


  Commit: 0fccd5bba40ce903ff25bb8f2ca09e86f3bef19d
  
https://github.com/NixOS/nixpkgs/commit/0fccd5bba40ce903ff25bb8f2ca09e86f3bef19d
  Author: Gleb Peregud 
  Date:   2017-06-19 (Mon, 19 Jun 2017)

  Changed paths:
M doc/languages-frameworks/beam.xml
M pkgs/development/beam-modules/mix-bootstrap
M pkgs/development/tools/build-managers/rebar3/rebar3-nix-bootstrap

  Log Message:
  ---
  erlang: update documentation.

The documentation got a bit stale compared to actual contents of
nixpkgs. This commit focuses on updating existing docs, not on making
sure all details of beam packages are covered.


  Commit: 505508a813d7680d8ada10eb8875a62de79e5aac
  
https://github.com/NixOS/nixpkgs/commit/505508a813d7680d8ada10eb8875a62de79e5aac
  Author: Eric Bailey 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M doc/default.nix
M doc/languages-frameworks/beam.xml

  Log Message:
  ---
  Update BEAM docs

Improve beam docs:
 * correct spelling
 * update per pandoc changes
 * capitalize titles
 * capitalize BEAM throughout and use "the BEAM" when referring to the virtual 
machine.
 * tweak grammar and phrasing
 * reformat build-tools-rebar3 section
 * add more links
 * re-wrap s

Also update s
* normalize whitespace
* don't double quote homepage
* use $ in all shell snippets


  Commit: aba574c4faeed0a359324d9fb89c7aeffb08314d
  
https://github.com/NixOS/nixpkgs/commit/aba574c4faeed0a359324d9fb89c7aeffb08314d
  Author: Daiderd Jordan 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M doc/default.nix
M doc/languages-frameworks/beam.xml
M pkgs/development/beam-modules/build-hex.nix
M pkgs/development/beam-modules/default.nix
M pkgs/development/beam-modules/lib.nix
M pkgs/development/beam-modules/mix-bootstrap
M pkgs/development/tools/build-managers/rebar3/rebar3-nix-bootstrap
M pkgs/top-level/all-packages.nix
M pkgs/top-level/beam-packages.nix

  Log Message:
  ---
  Merge pull request #26668 from gleber/fixpoint-erlang-packages

erlang: refactor: build packages per Erlang/OTP version.


Compare: https://github.com/NixOS/nixpkgs/compare/86dc6469baa6...aba574c4faee___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 90b2d0: maintainers: add roberth

[Robert Hensing]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 90b2d06268971aea52aa254df6c4458792986d88
  
https://github.com/NixOS/nixpkgs/commit/90b2d06268971aea52aa254df6c4458792986d88
  Author: Robert Hensing 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M lib/maintainers.nix

  Log Message:
  ---
  maintainers: add roberth


  Commit: 86dc6469baa652c111437ac8f3e124e1d1ed8f86
  
https://github.com/NixOS/nixpkgs/commit/86dc6469baa652c111437ac8f3e124e1d1ed8f86
  Author: Robert Hensing 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
A pkgs/development/python-modules/arelle/default.nix
M pkgs/top-level/all-packages.nix
M pkgs/top-level/python-packages.nix

  Log Message:
  ---
  arelle: init at 2017-06-01


Compare: https://github.com/NixOS/nixpkgs/compare/1f6518227280...86dc6469baa6___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] 5 somewhat related questions

[David Izquierdo]

I'll try to answer what I think I know...


On 22/06/17 20:40, Klaas van Schelven wrote:

Hello Nixians,

I've installed NixOs a number of days ago. So far I really like it!

I've read the documentation I could find, but I'm left with a number of
questions; not so much "how to do X" but rather of a slightly more
philosphofical (or cultural, a.k.a. "best practices") nature. I hope
someone can enlighten me on the "Nix Way".

1. In NixOs /etc/nixos/configuration.nix is the single configuration file
that determines the state of the system as a whole. How does this file
relate to the existence of the nix-env command, either executed as root or
by a single non-privileged user? In particular, I would assume that any
nix-env is undone by the time the system is rebuilt from the configuration
file. Assuming this is the case: should the usage of nix-env not be
actively discouraged in NixOs? (perhaps it is, and I simply did not find
the reference)
They're mostly independent, but AFAIK nix-env binaries have priority 
over conf.nix. Nothing gets undone, since whatever you install to your 
user profile stays in the nix store (because your user profile is a gc 
root). For me, the use of n-e is because it's faster to test or use 
oneshot software installing it imperatively than adding-then-removing to 
conf.nix. I guess `nix-shell -p` would be more "correct", but it's a 
matter of not forgetting you've used it.


2. (Context: Assuming for a moment there _is_ in fact a use-case for
nix-env; e.g. the scenario where you're not running NixOs, but are using
Nix on top of another distribution). nix-env uses an "imperative style" of
manipulating your environment, i.e. using a sequence of commands in a
particular order. I understand that after each succesful manipulation the
_resulting_ environment becomes available as a separate generation. As far
as I understand there's even a "half-product", the so called "derivation"
that is available per generation, although I did not study those yet. My
question is, however, whether the original commands that led to these
constructions can somehow be retrieved. The reason for this question is the
observation that the sequence of nix-env (and potentially other similar)
commands can be seen as a transactional log that could simply be replayed
to reconstruct the resulting generations (assuming that the commands fully
express the information needed to construct the associated environments;
this assumption might not actually hold in practice. Question 2b: does the
assumption hold?).

3. In the scenario where I use the single configuration file
/etc/nixos/configuration.nix but I'm also subscribed to a channel, the
state of this channel may influence the outcome of nixos-rebuild (This is
by design, it allows us to stay up to date with e.g. security updates). The
consecutive states of the channel, as seen by my system when rebuilding,
are valuable pieces of information in their own right when I want to debug
a problem. Take the following example:

t=0, my system is good.
t=1, I want to install some extra package, I modify configuration.nix, and
run nixos-rebuild
t=2, system broken.

I understand that I always have the ability to roll back the system _as a
whole_, even using Grub if needed. This is awesome of course. The question
is: do I also have the ability to debug the parts that lead to that whole?
In particular: the precise state of the channel[s] on each rebuild? And
preferably also: the state of /etc/nixos/configuration.nix on each build?


I think you want `nix-channel --rollback`, and 
`system.copySystemConfiguration = true` (for c.nix). Note however that 
at some point it will probably be in your best interest to modularise 
your c.nix into several files, and that option only copies c.nix, not 
any imports. You can check this message for a fairly elegant method to 
have your /etc/nixos tree be a part of each generation.


https://mailman.science.uu.nl/pipermail/nix-dev/2017-April/023403.html


4. Is a "single declarative file per user" (e.g. for dotfiles, but
potentially also to make it possible to declare which user-specific
packages are installed) available? I understand there some options exist,
but how do they relate? Is there convergence on a "one way to do it"?

5. In the commit linked below, the nix file for VTE 2.91 adds the following
2 propagatedBuildInputs: pcre2 & gnutls. As far as I understand this might
be not good practice. The reason I've added them is because pkg-config,
when run in the build context of xfce.terminal, cannot otherwise find the
package vte-2.91 because of a dependency error. Ignoring for a moment the
rationale of the commit itself (I've been convinced that adding this
particular version of xfce4-terminal to the repo by itself is not a good
idea) can someone tell me what the proper way to handle this particular
situation would be?

[Nix-commits] [NixOS/nixpkgs] 1f6518: electrum: Unify protobuf dependencies

[aszlig]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 1f65182272800122917f5ad25479ac618f7fd100
  
https://github.com/NixOS/nixpkgs/commit/1f65182272800122917f5ad25479ac618f7fd100
  Author: aszlig 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/misc/electrum/default.nix
M pkgs/development/python-modules/keepkey/default.nix

  Log Message:
  ---
  electrum: Unify protobuf dependencies

Since 9c57f3b5c05621f0d1c207aa80f20ccc1d79ebfb bumped the protobuf
version because the new upstream requires it, electrum now gets
protobuf3_0 *and* protobuf3_2 instead of just one version.

This leads to the following build errer:

Found duplicated packages in closure for dependency 'protobuf':
  protobuf 3.0.2 (...-python2.7-protobuf-3.0.2/lib/python2.7/site-packages)
  protobuf 3.2.0 (...-python2.7-protobuf-3.2.0/lib/python2.7/site-packages)

Using protobuf3_2 for keepkey and electrum fixes the build.

Signed-off-by: aszlig 
Cc: @np


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

[Nix-dev] 5 somewhat related questions

[Klaas van Schelven]

Hello Nixians,

I've installed NixOs a number of days ago. So far I really like it!

I've read the documentation I could find, but I'm left with a number of
questions; not so much "how to do X" but rather of a slightly more
philosphofical (or cultural, a.k.a. "best practices") nature. I hope
someone can enlighten me on the "Nix Way".

1. In NixOs /etc/nixos/configuration.nix is the single configuration file
that determines the state of the system as a whole. How does this file
relate to the existence of the nix-env command, either executed as root or
by a single non-privileged user? In particular, I would assume that any
nix-env is undone by the time the system is rebuilt from the configuration
file. Assuming this is the case: should the usage of nix-env not be
actively discouraged in NixOs? (perhaps it is, and I simply did not find
the reference)

2. (Context: Assuming for a moment there _is_ in fact a use-case for
nix-env; e.g. the scenario where you're not running NixOs, but are using
Nix on top of another distribution). nix-env uses an "imperative style" of
manipulating your environment, i.e. using a sequence of commands in a
particular order. I understand that after each succesful manipulation the
_resulting_ environment becomes available as a separate generation. As far
as I understand there's even a "half-product", the so called "derivation"
that is available per generation, although I did not study those yet. My
question is, however, whether the original commands that led to these
constructions can somehow be retrieved. The reason for this question is the
observation that the sequence of nix-env (and potentially other similar)
commands can be seen as a transactional log that could simply be replayed
to reconstruct the resulting generations (assuming that the commands fully
express the information needed to construct the associated environments;
this assumption might not actually hold in practice. Question 2b: does the
assumption hold?).

3. In the scenario where I use the single configuration file
/etc/nixos/configuration.nix but I'm also subscribed to a channel, the
state of this channel may influence the outcome of nixos-rebuild (This is
by design, it allows us to stay up to date with e.g. security updates). The
consecutive states of the channel, as seen by my system when rebuilding,
are valuable pieces of information in their own right when I want to debug
a problem. Take the following example:

t=0, my system is good.
t=1, I want to install some extra package, I modify configuration.nix, and
run nixos-rebuild
t=2, system broken.

I understand that I always have the ability to roll back the system _as a
whole_, even using Grub if needed. This is awesome of course. The question
is: do I also have the ability to debug the parts that lead to that whole?
In particular: the precise state of the channel[s] on each rebuild? And
preferably also: the state of /etc/nixos/configuration.nix on each build?

4. Is a "single declarative file per user" (e.g. for dotfiles, but
potentially also to make it possible to declare which user-specific
packages are installed) available? I understand there some options exist,
but how do they relate? Is there convergence on a "one way to do it"?

5. In the commit linked below, the nix file for VTE 2.91 adds the following
2 propagatedBuildInputs: pcre2 & gnutls. As far as I understand this might
be not good practice. The reason I've added them is because pkg-config,
when run in the build context of xfce.terminal, cannot otherwise find the
package vte-2.91 because of a dependency error. Ignoring for a moment the
rationale of the commit itself (I've been convinced that adding this
particular version of xfce4-terminal to the repo by itself is not a good
idea) can someone tell me what the proper way to handle this particular
situation would be?

https://github.com/NixOS/nixpkgs/pull/26742/commits/5e566d3c8a078f6cd6304e7cf0b409a8260ee71c#diff-52903c4477fc53869e7e92148494cbe5R17

Hope this isn't too overwhelming a wall of text - feel free to answer only
partly if you see fit.

Thanks in advance,
Klaas

-- 
Klaas van Schelven
+31 6 811 599 10
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 9b948e: pypi2nix: 1.6.0 -> 1.8.0

[Rok Garbas]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9b948ea439ddbaa26740ce35543e7e35d2aa6d18
  
https://github.com/NixOS/nixpkgs/commit/9b948ea439ddbaa26740ce35543e7e35d2aa6d18
  Author: Rok Garbas 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/tools/pypi2nix/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  pypi2nix: 1.6.0 -> 1.8.0


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

[Nix-commits] [NixOS/nixpkgs] 1a8797: update script for jetbrains products

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 1a879759103df812fae9d47b8e7773b6185522d9
  
https://github.com/NixOS/nixpkgs/commit/1a879759103df812fae9d47b8e7773b6185522d9
  Author: Volth 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix
A pkgs/applications/editors/jetbrains/update.pl

  Log Message:
  ---
  update script for jetbrains products


  Commit: d1eefba3a48828590a08389e14939c1cb5f4bfaf
  
https://github.com/NixOS/nixpkgs/commit/d1eefba3a48828590a08389e14939c1cb5f4bfaf
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/update.pl

  Log Message:
  ---
  jetbrains: use nix-shell shebang in update script


  Commit: 9cc023a9b448b2c2ae5d7e95bf2d9409f8fbab26
  
https://github.com/NixOS/nixpkgs/commit/9cc023a9b448b2c2ae5d7e95bf2d9409f8fbab26
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix
A pkgs/applications/editors/jetbrains/update.pl

  Log Message:
  ---
  Merge pull request #26769 from volth/jetbrains-update-script

jetbrains: update script


Compare: https://github.com/NixOS/nixpkgs/compare/32ef253269f8...9cc023a9b448___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 32ef25: tmate: minor cleanup

[Peter Hoeg]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 32ef253269f88fd5d33c80c6b463375c07d5130a
  
https://github.com/NixOS/nixpkgs/commit/32ef253269f88fd5d33c80c6b463375c07d5130a
  Author: Peter Hoeg 
  Date:   2017-06-23 (Fri, 23 Jun 2017)

  Changed paths:
M pkgs/tools/misc/tmate/default.nix

  Log Message:
  ---
  tmate: minor cleanup


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

[Nix-commits] [NixOS/nixpkgs] 633d04: clion1: remove package

[Volth]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 633d046590703f5e5ccbff5fcf686c8b884f8a37
  
https://github.com/NixOS/nixpkgs/commit/633d046590703f5e5ccbff5fcf686c8b884f8a37
  Author: Vasiliy Solovey 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  clion1: remove package
It is no longer present on JetBrains download servers and is
very outdated.

(cherry picked from commit d41dee0a9f3f85eec872171565ebb81e1f4b6bb2)


  Commit: eea3211bb4ca296f5628f68da882053f3afacffa
  
https://github.com/NixOS/nixpkgs/commit/eea3211bb4ca296f5628f68da882053f3afacffa
  Author: Jiri Danek 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  idea-community: 2017.1.1 -> 2017.1.3

(cherry picked from commit ccef4810caf740198a8428a7734771dcbd9e4c98)


  Commit: aae153cae4a4a79b4871499f8ac02934153021f8
  
https://github.com/NixOS/nixpkgs/commit/aae153cae4a4a79b4871499f8ac02934153021f8
  Author: Gauthier POGAM--LE MONTAGNER 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  idea.webstorm: 2017.1 -> 2017.1.3

(cherry picked from commit 282fba7f0c777f2acd023133d4a8b4fa842dd12d)


  Commit: 011192b5f4bf3aa967720262c28c18601b7dd8e2
  
https://github.com/NixOS/nixpkgs/commit/011192b5f4bf3aa967720262c28c18601b7dd8e2
  Author: Volth 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  jetbrains.{webstorm,phpstorm}: 2017.1 -> 2017.1.4

(cherry picked from commit bf5c57e1b8e243565469196d033bb61ab0055307)


Compare: https://github.com/NixOS/nixpkgs/compare/6ed463b0585b...011192b5f4bf___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] bf5c57: jetbrains.{ruby-mine, webstorm, datagrip, phpstorm}: ...

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: bf5c57e1b8e243565469196d033bb61ab0055307
  
https://github.com/NixOS/nixpkgs/commit/bf5c57e1b8e243565469196d033bb61ab0055307
  Author: Volth 
  Date:   2017-06-21 (Wed, 21 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  jetbrains.{ruby-mine,webstorm,datagrip,phpstorm}: 2017.1 -> 2017.1.4


  Commit: c89efa3cbce9f5534e3d24ec61788c4dc4813399
  
https://github.com/NixOS/nixpkgs/commit/c89efa3cbce9f5534e3d24ec61788c4dc4813399
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/applications/editors/jetbrains/default.nix

  Log Message:
  ---
  Merge pull request #26753 from volth/jetbrains-update-2017.1.4

jetbrains.{ruby-mine,webstorm,datagrip,phpstorm}: 2017.1 -> 2017.1.4


Compare: https://github.com/NixOS/nixpkgs/compare/dfeea018b68e...c89efa3cbce9___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 6ed463: slock: Avoid chmod u+s (#26600)

[mingchuan]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 6ed463b0585b2fd068271522a44a88c5a5b433a2
  
https://github.com/NixOS/nixpkgs/commit/6ed463b0585b2fd068271522a44a88c5a5b433a2
  Author: mingchuan 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/misc/screensavers/slock/default.nix

  Log Message:
  ---
  slock: Avoid chmod u+s (#26600)

(cherry picked from commit 722d61c2f251595c5021aeef13564082c5bd2923)


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

[Nix-commits] [NixOS/nixpkgs] 722d61: slock: Avoid chmod u+s (#26600)

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 722d61c2f251595c5021aeef13564082c5bd2923
  
https://github.com/NixOS/nixpkgs/commit/722d61c2f251595c5021aeef13564082c5bd2923
  Author: mingchuan 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/misc/screensavers/slock/default.nix

  Log Message:
  ---
  slock: Avoid chmod u+s (#26600)


  Commit: dfeea018b68ee66eb958ba8ec19196acf4526c54
  
https://github.com/NixOS/nixpkgs/commit/dfeea018b68ee66eb958ba8ec19196acf4526c54
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/misc/screensavers/slock/default.nix

  Log Message:
  ---
  Merge pull request #26768 from sifmelcara/fix/slock-cap

slock: Avoid chmod u+s


Compare: https://github.com/NixOS/nixpkgs/compare/05f94c8c13db...dfeea018b68e___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixops] 8fc7d0: Make virtualbox stop-start test less flaky.

[Rob Vermaas]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixops
  Commit: 8fc7d0f26e33e0ba4ae4fbcb937d17a183f0b487
  
https://github.com/NixOS/nixops/commit/8fc7d0f26e33e0ba4ae4fbcb937d17a183f0b487
  Author: Rob Vermaas 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M nixops/backends/virtualbox.py

  Log Message:
  ---
  Make virtualbox stop-start test less flaky.


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

[Nix-commits] [NixOS/nixpkgs] 05f94c: hydra: 2017-06-21 -> 2017-06-22

[Domen Kožar]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 05f94c8c13dbe4084faea98c62b99d40c7f97acf
  
https://github.com/NixOS/nixpkgs/commit/05f94c8c13dbe4084faea98c62b99d40c7f97acf
  Author: Domen Kožar 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/tools/misc/hydra/default.nix

  Log Message:
  ---
  hydra: 2017-06-21 -> 2017-06-22


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

[Nix-commits] [NixOS/hydra] 803833: Disable the build-queued hook

[Eelco Dolstra]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/hydra
  Commit: 803833aba77e1082c14857aa26933fc7fe5ae190
  
https://github.com/NixOS/hydra/commit/803833aba77e1082c14857aa26933fc7fe5ae190
  Author: Eelco Dolstra 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M src/script/hydra-eval-jobset

  Log Message:
  ---
  Disable the build-queued hook

This can take an excessive amount of time. For example, on
hydra.nixos.org, a call to hydra-notify takes 0.7s even if there are
no plugins. So for an eval with ~45K new builds, the calls to
hydra-notify add up to about 9 hours.

The proper fix would be to pass a list of build IDs, or an eval ID.


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

[Nix-commits] [NixOS/nixpkgs] 496c1f: haskellPackages: make configuration-{nix, common}.n...

[Domen Kožar]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 496c1f3f7d9900cff85ba56b37f0ed1c10c44189
  
https://github.com/NixOS/nixpkgs/commit/496c1f3f7d9900cff85ba56b37f0ed1c10c44189
  Author: Domen Kožar 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/haskell-modules/default.nix

  Log Message:
  ---
  haskellPackages: make configuration-{nix,common}.nix configurable

The motivation is to be able to get rid of common configuration
when initial packages differs since common configuration assumes
a very specific version set.

cc @jmitchell @peti

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


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

[Nix-commits] Failed: Hydra job nixpkgs:trunk:tarball on x86_64-linux

[Hydra Build Daemon]

Hi,

The status of Hydra job ‘nixpkgs:trunk:tarball’ (on x86_64-linux) has changed 
from "Success" to "Failed".  For details, see

  https://hydra.nixos.org/build/54677998

This may be due to 28 commits by José Romildo Malaquias , 
Jörg Thalheim , Pascal Wittmann , 
Peter Hoeg , armijnhemel  
or dywedir .

Go forth and fix it.

Regards,

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

[Nix-commits] [NixOS/nixpkgs] 9c57f3: python-modules/trezor: Fix build

[aszlig]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9c57f3b5c05621f0d1c207aa80f20ccc1d79ebfb
  
https://github.com/NixOS/nixpkgs/commit/9c57f3b5c05621f0d1c207aa80f20ccc1d79ebfb
  Author: aszlig 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/python-modules/trezor/default.nix

  Log Message:
  ---
  python-modules/trezor: Fix build

Regression introduced by 76beb0831384b5ae53592513507524990017e973.

With version 0.7.15 a few additional dependencies are needed by trezor,
mainly a newer version of protobuf bindings and requests.

Signed-off-by: aszlig 
Cc: @np


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

[Nix-commits] [NixOS/nixpkgs] 5041df: doc/languages-frameworks/vim: add custom vimrc & p...

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 5041df441112a4533c62091799d864e61dbda3de
  
https://github.com/NixOS/nixpkgs/commit/5041df441112a4533c62091799d864e61dbda3de
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M doc/languages-frameworks/vim.md

  Log Message:
  ---
  doc/languages-frameworks/vim: add custom vimrc & packages


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

[Nix-commits] [NixOS/nixpkgs] bb9e23: haskellPackages: make configuration-{nix, common}.n...

[Domen Kožar]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: bb9e23837a3c4334133efa9976cd822b2bf333e3
  
https://github.com/NixOS/nixpkgs/commit/bb9e23837a3c4334133efa9976cd822b2bf333e3
  Author: Domen Kožar 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/haskell-modules/default.nix

  Log Message:
  ---
  haskellPackages: make configuration-{nix,common}.nix configurable

The motivation is to be able to get rid of common configuration
when initial packages differs since common configuration assumes
a very specific version set.

cc @jmitchell @peti


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

[Nix-dev] Setup hook evaluation order

[Thomas Tuegel]

Hi nix-dev,

My package has a setup hook which needs $outputDev, $outputLib, etc. to be 
set. In other words, I need the multiple-outputs.sh setup hook to be loaded 
before my setup hook is evaluated. However, multiple-outputs.sh is part of 
defaultNativeBuildInputs and is always loaded *after* any packages in 
buildInputs or nativeBuildInputs.

How can I make my setup hook be evaluated after multiple-outputs.sh is loaded?

Thanks,
Tom
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 3d5220: sshd.nix: Added nixops usage warning of openssh.au...

[Joachim Schiele]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 3d52203ab2a2aa31df8ae52efda3b14e75628a57
  
https://github.com/NixOS/nixpkgs/commit/3d52203ab2a2aa31df8ae52efda3b14e75628a57
  Author: Joachim Schiele 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M nixos/modules/services/networking/ssh/sshd.nix

  Log Message:
  ---
  sshd.nix: Added nixops usage warning of openssh.authorizedKeys.keys usage


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

[Nix-commits] [NixOS/nixpkgs] f12006: hound: 20160919 -> 20170324

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: f12006bd962188762c37f34dc8416c03ba026835
  
https://github.com/NixOS/nixpkgs/commit/f12006bd962188762c37f34dc8416c03ba026835
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/tools/misc/hound/default.nix

  Log Message:
  ---
  hound: 20160919 -> 20170324


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

[Nix-commits] [NixOS/nixpkgs] 95c98b: unifont: 9.0.06 -> 10.0.01

[Michael Raskin]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 95c98b9bf511d3ff618e4143de6943e2a1784a27
  
https://github.com/NixOS/nixpkgs/commit/95c98b9bf511d3ff618e4143de6943e2a1784a27
  Author: Lancelot SIX 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/data/fonts/unifont/default.nix

  Log Message:
  ---
  unifont: 9.0.06 -> 10.0.01

See http://lists.gnu.org/archive/html/info-gnu/2017-06/msg9.html
for release information


  Commit: a06c5123b352c9735d4f5502192abe3c1aee24ed
  
https://github.com/NixOS/nixpkgs/commit/a06c5123b352c9735d4f5502192abe3c1aee24ed
  Author: Michael Raskin <7c6f4...@mail.ru>
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/data/fonts/unifont/default.nix

  Log Message:
  ---
  Merge pull request #26759 from lsix/update_unifont

unifont: 9.0.06 -> 10.0.01


Compare: https://github.com/NixOS/nixpkgs/compare/744bdac78ec4...a06c5123b352___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 744bda: Re-add iolib subsystems

[Michael Raskin]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 744bdac78ec49b517c3285b24d3cccf5e2be6ed0
  
https://github.com/NixOS/nixpkgs/commit/744bdac78ec49b517c3285b24d3cccf5e2be6ed0
  Author: Michael Raskin <7c6f4...@mail.ru>
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/lisp-modules/quicklisp-to-nix-overrides.nix

  Log Message:
  ---
  Re-add iolib subsystems


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

[Nix-commits] [NixOS/nixpkgs] 3e430a: dale: fix linking against llvm libs

[Jörg Thalheim]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 3e430a8ee55813f5d2b128316bf599924f084908
  
https://github.com/NixOS/nixpkgs/commit/3e430a8ee55813f5d2b128316bf599924f084908
  Author: Jörg Thalheim 
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M pkgs/development/compilers/dale/default.nix
A pkgs/development/compilers/dale/link-llvm.patch

  Log Message:
  ---
  dale: fix linking against llvm libs


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

Re: [Nix-dev] canon printer drivers (cnijfilter)

[Nawal Husnoo]

Sample code from my attempts might help:

mkdir -p $out/
cp -r $src/* $out/


chmod 777 -R $out/*


patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)" \
--set-rpath $libPath:$out/lib \
$out/bin/cnijnpr

ln -sv $out/lib/libcnbpcmcm356.so.8.0.1 $out/lib/libcnbpcmcm356.so

LIBTIFF=$(pkg-config --libs-only-L libtiff-4 | sed -e
's/-L//g')/libtiff.so.5
ln -s $LIBTIFF $out/lib/libtiff.so.4

ldd $out/lib/cups/filter/pstocanonij


The latter looks inside the binary and tries to link it (dynamically) - it
should show what's still missing. The tiff business just makes tiff
available to the canon driver.


The rpath bit in the patchelf command is probably what you're looking for
initially.

hth

Nawal









On 22 Jun 2017 03:24, "Matt McHenry"  wrote:

> Okay, patchelf seemed promising.  I just pushed
> https://github.com/jerith666/nixpkgs/commit/237a52ca24026f2e
> 4d8a5543eb7aa98f610f642c to add it to my expression.  However, it doesn't
> seem to have helped.  :-(
>
> Looking at the source code, the "Error: CNCL_SetParam" is coming from
> ./cnijfilter/src/bjfilter.c line 661.  The CNCL_SetParam() function is not
> defined in any of the provided source code, though -- rather, it looks like
> it's in ./328/libs_bin/libcnbpcnclapi328.so.3.3.0.
>
> I have a gdb trace laying around from last time I worked on this, and it
> has this stack trace:
>
> Catchpoint 1 (call to syscall open), 0xf7fd8da9 in __kernel_vsyscall ()
> eax is -38
> (gdb) where
> #0  0xf7fd8da9 in __kernel_vsyscall ()
> #1  0xf7d65f23 in __open_nocancel () from /nix/store/bgmm5m6q04fl5myf831
> c73l1xmbl38xw-glibc-2.24/lib/libc.so.6
> #2  0xf7cf9fd6 in __GI__IO_file_open () from /nix/store/bgmm5m6q04fl5myf831
> c73l1xmbl38xw-glibc-2.24/lib/libc.so.6
> #3  0xf7cfa1d1 in __GI__IO_file_fopen () from
> /nix/store/bgmm5m6q04fl5myf831c73l1xmbl38xw-glibc-2.24/lib/libc.so.6
> #4  0xf7cedd31 in __fopen_internal () from /nix/store/bgmm5m6q04fl5myf831
> c73l1xmbl38xw-glibc-2.24/lib/libc.so.6
> #5  0xf7cedd9e in fopen@@GLIBC_2.1 () from /nix/store/bgmm5m6q04fl5myf831
> c73l1xmbl38xw-glibc-2.24/lib/libc.so.6
> #6  0xf7fd1b08 in BJVSOpenFile () from /nix/store/9ci3apl3d8spw0zdp20
> 2cwr325n8hz28-cnijfilter-2.80/lib/libcnbpcmcm328.so
> #7  0xf7fcafa3 in CommandComp2Ext_Open () from
> /nix/store/9ci3apl3d8spw0zdp202cwr325n8hz28-cnijfilter-2.80/
> lib/libcnbpcmcm328.so
> #8  0xf7fce059 in CommandComp2 () from /nix/store/9ci3apl3d8spw0zdp20
> 2cwr325n8hz28-cnijfilter-2.80/lib/libcnbpcmcm328.so
> #9  0xf7e60d4d in CNCL_SetParam () from /nix/store/9ci3apl3d8spw0zdp20
> 2cwr325n8hz28-cnijfilter-2.80/lib/libcnbpcnclapi328.so
> #10 0x0804b3c8 in main ()
>
> I think this means that it's trying to open some file and failing.  My
> *guess* is that it's trying to open one of these files, but doesn't have
> the proper nix store path:
>
> $ file /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/
> lib/bjlib/*
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifip3500.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifip4500.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifmp140.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifmp210.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifmp520.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cifmp610.conf:
> ASCII text
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3150.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3160.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3190.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3260.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3270.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnb_3280.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname315.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname316.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname319.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname326.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname327.tbl:
> TrueType font data
> /nix/store/g1gdd81qh6dskjalg6icg56yw74rb03b-cnijfilter-2.80/lib/bjlib/cnbpname328.tbl:
> TrueType font data
>
> that's what my https://github.com/jerith666/
> 
>