<{^_^}>
cannot import '/nix/store/acy8azc90lm6njrlr501x3ygarljlkrf-centos-7.4.1708-x86_64.nix', since path '/nix/store/wgzklc0dj4axkn6iig6xpj2l4lyawf6p-centos-7.4.1708-x86_64.nix.drv' is not valid, at /var/li...
<hoverbear>
hmm I get "error: cannot coerce a set to a string, at /nix/store/2574y0p5q6xlzqhzb8afg3m68pd6w7kl-nixos-20.09pre231646.4cdd64d9078/nixos/pkgs/build-support/release/rpm-build.nix:14:5"
<drakonis>
hydra still uses an older flake lock version?
<drakonis>
i'm updating my system but it is complaining about hydra's lock version
<FRidh>
gchristensen: those belong in a dev output
drakonis has quit [Quit: WeeChat 2.8]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
alp has quit [Ping timeout: 265 seconds]
alp has joined #nixos-dev
<lewo>
How could I know when staging-next will be merged?
<lewo>
Or to reformulate, how do you decide if it can go to master?
<FRidh>
lewo: if most of the job is built and if there do not seem to be any substantial issues, then it gets merged. We can be a bit more flexible with the former, and the latter can be quite difficult to determine, because the set is so big and there is no good overview to see which build failures matter and which don't. We should have a /tested for staging-next as well I think.
<lewo>
FRidh: ok thanks.
_ris has joined #nixos-dev
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
<lewo>
FRidh: I've been able to locally build https://hydra.nixos.org/build/122775374 which is responsible of a lot staging-next build failures. What about just restarting this build on Hydra? :-/
<FRidh>
lewo: done. Unfortunately it won't restart reverse dependencies
<lewo>
FRidh: if this build succeeds, what about restring all failed jobs of the staging-next jobset?
<lewo>
I think there is a "button" to do that
<lewo>
s/restring/restarting/
<lewo>
Maybe restarting all failing jobs is a bit excessive...
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
orivej_ has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
orivej_ has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
alp has joined #nixos-dev
hoverbear has joined #nixos-dev
<hoverbear>
(re: http://scg.unibe.ch/download/wasdett/wasdett2008-paper11.pdf page 4) .. So `rpmBuild` takes a `src` which is intended to be a `makeSourceTarball` output? I'm currently using `(makeRustPlatform ...).buildRustPackage` to create binaries, which is returning a `mkDerivation` result so I need to figure how that fits in. :think:
<hoverbear>
niksnut: This is a fantastically good paper btw
<makefu>
hoverbear: it is written by the power of two eelco *scnr*
<hoverbear>
Eelco^2
<makefu>
exactly
<hoverbear>
I'm struggling to use rpmBuild with buildRustPackage sadly :(
<delroth>
domenkozar[m]: any thoughts on tagging a new patchelf release for https://github.com/NixOS/patchelf/pull/216 ? I wanted to cherry-pick it in nixpkgs but unfortunately the patch doesn't apply cleanly on top of 0.11
<{^_^}>
patchelf#216 (by delroth, 6 days ago, merged): Improve the default section alignment choice (> 4K page size compat)
<domenkozar[m]>
might be good to bump unstable and try it out first
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-dev
<delroth>
is there a process for that? right now patchelfUnstable is just used by a few packages
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
<domenkozar[m]>
it's tricky since it's used by stdenv
<domenkozar[m]>
but buildInputs override that
<mdlayher>
looks like whatever the build problem was for nixos-unstable-small has cleared up? sorry, no idea how these things work :)
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
b1000101 has joined #nixos-dev
gilligan has joined #nixos-dev
abathur has quit [Quit: abathur]
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-dev
<urkk>
running the nix-daemon via nix-user-chroot fails when for users with: "changing owner of directory '/nix/var/nix/profiles/per-user/nobody': Invalid argument"
<urkk>
I guess the daemon sees the other user as nobody bc is from another user namespace
<NinjaTrappeur>
Quick survey: I need to symlink a conf file to /etc. Would use rather use environment.etc or a systemd tmpfile link?
<urkk>
how is the user determined from the daemon?
<NinjaTrappeur>
*would you
<gchristensen>
NinjaTrappeur: what exactly is the result?
<NinjaTrappeur>
Basically, I have a file in the store I want to symlink to /etc/nsd/nsd.conf. I have an associated systemd service that'll use this conf file.
<NinjaTrappeur>
(I don't fully undenstand your question, I'm not sure I correctly answered it)
<lewo>
NinjaTrappeur: when possible, I would prefer build time than execution time
<gchristensen>
NinjaTrappeur: so you put a file in /etc/foo and you want to make /var/lib/bar link to /etc/foo ?
<NinjaTrappeur>
gchristensen: I am generating a file in /nix/store/blablah-blahblah.conf, I want to link it to /etc/foo
<gchristensen>
environment.etc 100%
<NinjaTrappeur>
(generating the file during a nixos-rebuild)
<NinjaTrappeur>
ok, thanks to you both!
<gchristensen>
tmpfiles is muuuuch less atomic
<gchristensen>
and environment.etc is much clearer about intent and transparent of operation
<NinjaTrappeur>
👍
<LnL>
I think you can do that with environment.etc."foo".source
<NinjaTrappeur>
yup, exactly
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-dev
alp has quit [Quit: Leaving]
<hoverbear>
Oh no my `nix-shell` can't `cargo build` anymore but my `nix build` can Q_Q
rajivr has quit [Quit: Connection closed for inactivity]
alp has joined #nixos-dev
drakonis has joined #nixos-dev
<Profpatsch>
hoverbear: cargo clean
<hoverbear>
Profpatsch: I did =D
<Profpatsch>
maybe remove ~/.cargo as well
<hoverbear>
I seem to be not able to link my std c++ to leveldb :think: