_ris has quit [(Ping timeout: 240 seconds)]
WilliButz has quit [(Quit: WeeChat 1.9.1)]
WilliButz has joined joined #nixos-dev
WilliButz has quit [(Client Quit)]
WilliButz has joined joined #nixos-dev
WilliButz has quit [(Client Quit)]
WilliButz has joined joined #nixos-dev
mbrgm has quit [(Ping timeout: 240 seconds)]
mbrgm has joined joined #nixos-dev
orivej has quit [(Ping timeout: 248 seconds)]
Sonarpulse has joined joined #nixos-dev
<Sonarpulse> bgamari: ah shit, gas doesn't support --enable-targets=all
<Sonarpulse> well it does
<Sonarpulse> but it doesn't do anything
ma27 has joined joined #nixos-dev
ma27 has quit [(Client Quit)]
orivej has joined joined #nixos-dev
ma27 has joined joined #nixos-dev
ma27 has quit [(Ping timeout: 276 seconds)]
<Sonarpulse> orivej: https://github.com/NixOS/nixpkgs/pull/32098 what do you think
<Sonarpulse> looking to merge this real fast :D
<orivej> Sonarpulse: sounds ok. In the contexts where stdenv.cc.prefix may clash with a local variable "prefex", it seems better to call the former "targetPrefix" rather then "binPrefix". On the other hand, couldn't you just "inherit cc" to use "cc.prefix" to avoid the clashes?
<Sonarpulse> orivej: the issue was making prefix a env var
<Sonarpulse> that hits the prefix bash variable
<Sonarpulse> in nix there is no conflict, but other packages do use prefix in the normal way
<Sonarpulse> as to binPrefix vs targetPrefix, I'm fine with either
<Sonarpulse> I went with "bin" because it could be an arbitrary string
<Sonarpulse> doesn't matter as long as its used consistently
<Sonarpulse> also, we don't prefix (yet!) in the native case
<orivej> Why does the cc.prefix has to be an env var?
<Sonarpulse> but it isn't like there's *no* target platform in the native case
<Sonarpulse> orivej: I use it in the setup script for binutils
<Sonarpulse> and the normal prefix is an env var for `install`
<orivej> If the use is so limited, why not provide cc.prefix under a different name for binutils? Do you expect this var to be needed in other derivations?
<Sonarpulse> orivej: this prefix?
<Sonarpulse> yes
<Sonarpulse> other compiles (especially GHC in some commits I ahve) will also have a binPrefix
<Sonarpulse> so I suspect both will be standard across distributions
<Sonarpulse> orivej: any final thoughts? hoping to go to sleep in a second :)
<Sonarpulse> I figure this at least makes things unambiguous for a future find+replace
<orivej> ok then. targetPrefix sounds better as it conveys the idea that it contains the target triplet. spell checking the commit message will do future readers a favor :)
<orivej> the places where it depends on "hostPlatform != buildPlatform" look suspicious since they do not depend on the target platform, but maybe they are correct; and this does affect your PR
<orivej> err, does not affect the PR
<Sonarpulse> orivej: I'll check those
<Sonarpulse> n.b. targetPrefix would be a mass rebuild, but happy to do
<Sonarpulse> next one is too, anyways
<Sonarpulse> so whatever
<Sonarpulse> orivej: ah, that is because it is from the perspective of the build-time comsumer of the compiler
<orivej> right
<Sonarpulse> orivej: ok rebased with targetPlatform and spellcheck
<Sonarpulse> orivej: thanks!
FRidh has joined joined #nixos-dev
<orivej> Sonarpulse: oops, pkgs/build-support/cc-wrapper/default.nix actually needs binPrefix in for `substitute`
<Sonarpulse> orivej: I did a treewide find and replace
<Sonarpulse> so I think good?
<Sonarpulse> maybe i forgot
<orivej> see pkgs/build-support/cc-wrapper/setup-hook.sh
<Sonarpulse> orivej: oh hmm i guess my find replace wasn't as good I as I thought :(
<orivej> I can fix this if you want to
<Sonarpulse> orivej: i got it
<Sonarpulse> i found old binutils-wrapper file hanging around
<Sonarpulse> pre revert in august!
<Sonarpulse> I'll fix both
<orivej> see also pkgs/build-support/cc-wrapper/macos-sierra-reexport-hack.bash and pkgs/build-support/binutils-wrapper/macos-sierra-reexport-hack.bash
<orivej> the latter should probably be deleted, but note that they are a little different
<orivej> (ah, it is the one that from the pre revert)
<Sonarpulse> orivej: yeah i rewote the whole thing on stable
<Sonarpulse> (need to forward part, have a PR open fo 17.09)
<Sonarpulse> so not too worried about little differences between old versions
goibhniu has joined joined #nixos-dev
phreedom has quit [(Ping timeout: 240 seconds)]
phreedom has joined joined #nixos-dev
<domenkozar> peti: btw, any reason we are using hackage-db instead of hackage-security?
<peti> domenkozar: We were using hackage-db since long before hackage-security existed and no-one ported the code.
<domenkozar> peti: ok, I'm going to do some digging
<domenkozar> cabal2nix takes ~0s on local cabal file
<domenkozar> but ~2s on cabal file from hackage index
<domenkozar> since I have a package set of 300, this yields a huge difference
Mic92 has joined joined #nixos-dev
<Profpatsch> > nix-instantiate -A postgresql.man ~/nixpkgs
<Profpatsch> /nix/store/8xwqcspkm0r07bcyif2wh56jha15w00x-postgresql-9.6.5.drv!man
<Profpatsch> uh, is it normal that !man is appended to the path like that?
<Profpatsch> The path doesn’t exist, only .drv does.
<Profpatsch> What is the information used for? And by which tool?
<LnL> that's the notation for drv outputs, but most stuff doesn't understand it yet
<Profpatsch> LnL: Is it guaranteed that a split on ! will only ever produce two results?
<adisbladis> Whats the policy on urgent security fixes? Push straight to master and backport or should everything go through review?
<Profpatsch> There’s so much that could go wrong there.
<Profpatsch> :((
<Profpatsch> names are not guaranteed to not contain ! iirc
<LnL> you can only select a single output AFAIK
<domenkozar> split on first !
<domenkozar> :P
<domenkozar> or do you mean package names?
<Profpatsch> Ah, package names cannot have !
<Profpatsch> Kind of flaky, still.
<Profpatsch> Hm, how long has that been in 1.11?
<Profpatsch> Because that’s a rather big breaking change, no?
<Profpatsch> Why introduce it now, when 1.12 is coming soon?
<domenkozar> Profpatsch: we backported a lot of stuff from 1.12
<domenkozar> Profpatsch: but I'm not certain this was part of the bugfixes really
<Profpatsch> hehe. :)
<domenkozar> Profpatsch: are you using the nix-diff?
<Profpatsch> Just starred it for when I need it.
<Profpatsch> Haven’t had a use-case yet.
<domenkozar> lucky you :)
<Profpatsch> Let’s hope that lasts! :P
<domenkozar> lasts for a week with me
<Profpatsch> Hm, I basically never have to look inside drv files.
<Profpatsch> But I don’t do any build supervision of stuff I didn’t break, so there’s that.
<domenkozar> it's mostly for figuring out
<Profpatsch> Might be really handy in those casee
<Profpatsch> *s
<domenkozar> WHY IS IT BUILDING FROM SOURCE AGAIN
<Profpatsch> Ah, right.
<domenkozar> if you stick to nixpkgs, it's not useful
<domenkozar> but outside nixpkgs it's still chaos
<Profpatsch> I’m mostly over that, somehow trained myself to know which branches in which version I’m on by intuition.
<domenkozar> Profpatsch: it's not just git
<Profpatsch> But yeah, custom repos sound like pain.
<domenkozar> it's nix itself that often breaks the promise
<domenkozar> or suble bugs with inputs
<Profpatsch> That’s why I hate the fact that fetchgit is a cheating fixed-output derivation now.
<Profpatsch> One more source of grey hair.
<domenkozar> its cheating?
<Profpatsch> You can leave out the hash
<Profpatsch> And if I understood correctly it just runs with it?
<domenkozar> it has to be fixed-output to get networking
FRidh has quit [(Remote host closed the connection)]
vcunat has joined joined #nixos-dev
FRidh has joined joined #nixos-dev
<Profpatsch> domenkozar: Concerning splitting on !, I guess this pattern will never let me go
<Profpatsch> I wonder how verbose it gets when written in C++
<Profpatsch> Just found out that it’s completely by chance man(1) works inside nix shells.
<Profpatsch> It basically searches for ../man and ../share/man
<Profpatsch> And iff the binary is in the same derivation as the manpage, it will be found in the nix shell
<Profpatsch> If the manpages are split into their own output, that doesn’t happen.
<Profpatsch> So we should probably set that?
<aminechikhaoui> Hi, is there a way I can delete a path from an s3 binary cache ?
<aminechikhaoui> something like nix-store --delete but with an s3 store
<Profpatsch> aminechikhaoui: You could ask in #nixos, there’s more people there.
<aminechikhaoui> Profpatsch: sure
orivej has quit [(Ping timeout: 240 seconds)]
ma27 has joined joined #nixos-dev
<vcunat> jtojnar: I finally got a bit more time to look at the changes, so all gnome-2.26 stuff is staged now, unless I missed something
ma27 has quit [(Ping timeout: 276 seconds)]
ma27 has joined joined #nixos-dev
ma27 has quit [(Quit: WeeChat 1.9.1)]
ma27 has joined joined #nixos-dev
bgamari has quit [(Ping timeout: 246 seconds)]
gleber_ has quit [(Ping timeout: 240 seconds)]
orivej has joined joined #nixos-dev
ma27 has quit [(Ping timeout: 276 seconds)]
ma27 has joined joined #nixos-dev
phreedom has quit [(Ping timeout: 240 seconds)]
phreedom has joined joined #nixos-dev
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
phreedom has joined joined #nixos-dev
ckauhaus has joined joined #nixos-dev
ma27 has quit [(Quit: WeeChat 1.9.1)]
ma27 has joined joined #nixos-dev
ma27 has quit [(Client Quit)]
ma27 has joined joined #nixos-dev
<jtojnar> see the ready column
<jtojnar> but the blocking one are merged, thanks
ma27 has quit [(Quit: WeeChat 1.9.1)]
ma27 has joined joined #nixos-dev
ma27 has quit [(Client Quit)]
<jtojnar> though I do not understand why GitHub did not close the pull requests
<orivej> jtojnar: GitHub will close them once they are in the default branch, which is "master"
<orivej> vcunat: why do you prefix some update commits with the word "maintenance"? does it signify a mass rebuild?
<vcunat> jtojnar: I discoverd those in the meantime
<vcunat> orivej: no, that's orthogonal to the amount of rebuild
ma27 has joined joined #nixos-dev
<vcunat> maintenance updates are those that only contain bugfixes, basically
<vcunat> I think some upstreams use this exact word
bgamari has joined joined #nixos-dev
gleber_ has joined joined #nixos-dev
<gchristensen> anyone available to merge #32107?
<vcunat> gchristensen: I can merge
<vcunat> but I have no idea what the package is about
<jtojnar> thanks
<gchristensen> :) it is a mega-package from Chef with a million tools in it %)
<vcunat> gchristensen: I meant I can't really review it, but I can "push the button" if you think it's safe enough
<gchristensen> I just can't commit or push green buttons during my work day. that said, it isn't really critical it happen now.
<vcunat> understood
bgamari has quit [(Ping timeout: 276 seconds)]
bgamari has joined joined #nixos-dev
JosW has joined joined #nixos-dev
<domenkozar> now with README
ma27 has quit [(Ping timeout: 276 seconds)]
<gchristensen> whooaa
ma27 has joined joined #nixos-dev
<makefu> awesome
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
phreedom has joined joined #nixos-dev
<ckauhaus> that's cool
<ckauhaus> gchristensen: fpletz: time for another vulnix-powered security roundup?
<gchristensen> yes plz :)
<ckauhaus> I'd like to start with the output derivation of release-small.nix
<ckauhaus> and then we'll see how much it is
<gchristensen> sounds great
<ckauhaus> the progress on the last one was really encouraging
<ckauhaus> perhaps I'll even find some time this evening to revamp the broken whitelist thing
<ckauhaus> (no promises though)
<gchristensen> :) one step at a time
<ckauhaus> sure
<ckauhaus> I've found https://github.com/NixOS/nixpkgs/issues/15660 to be lingering since last year
<ckauhaus> I think there is now a solution
<gchristensen> seenoevil.gif
<gchristensen> I think you're right
<ckauhaus> just fixing the tests and committing the code
goibhniu has quit [(Ping timeout: 276 seconds)]
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
goibhniu has joined joined #nixos-dev
orivej has quit [(Ping timeout: 260 seconds)]
ma27 has quit [(Ping timeout: 252 seconds)]
ma27 has joined joined #nixos-dev
<Profpatsch> So I wrote a simple helper tool for calling manpages that are not necessarily in the system path.
<Profpatsch> nman postgresql initdb
<Profpatsch> grabs postgresqsl.man and opens the page for initdb.
<Profpatsch> also works with sections (nman hello 1 hello) and with a short version, as long as the attribute is the same as the program (nman hello)
<Profpatsch> Think it’s pretty handy for day-to-day DevOps work.
JosW has quit [(Quit: Konversation terminated!)]
<gchristensen> whoa, Profpatsch
vcunat has quit [(Ping timeout: 258 seconds)]
<ckauhaus> gchristensen: fpletz: https://github.com/NixOS/nixpkgs/issues/32117 - Vulnerability Roundup 29
<gchristensen> w00t
<ckauhaus> scanned on release-small.nix
<adisbladis> Profpatsch: Useful stuff :)
<ckauhaus> not that much today
<ckauhaus> next time, I'll tackle release.nix
<gchristensen> wow, not a bad list at all
<ckauhaus> I left out everything that has already made it into roundup 28
<ckauhaus> also release vulnix-1.4.0 with the new CVE patch autodetection feature
<ckauhaus> time to get something to eat...
<gchristensen> nice
phreedom has joined joined #nixos-dev
<disasm> ckauhaus gchristensen: just came in on oss-sec an hour ago https://github.com/NixOS/nixpkgs/pull/32116
<gchristensen> "error: build of ‘/nix/store/ib44vpxk9fifbb968i4smas4gwsv8srm-powerdns-4.0.5.drv’ failed" weird
<Profpatsch> adisbladis: ikr
<pstn> I'm trying to bump linux-testing to 4.15-rc1 in nixos but get the error "/tmp/nix-build-linux-4.15-rc1.drv-0/linux-4.15-rc1/Makefile:926: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop." What should I do add the dependency or disable the option?
<pstn> It seems to be a debugging tool but I'm not familiar with it.
<Dezgeg> add libelf probably
vcunat has joined joined #nixos-dev
<vcunat> wouldn't it be better to utilize nix-index
<vcunat> ?
<vcunat> (so you don't have to type the attribute name)
<pstn> vcunat: Is this comment directed at me?
<vcunat> no
<vcunat> that for the "nman" tool
<pstn> Alright. I was a bit confused what I should do with nix-index anyway :-)
<vcunat> (I lost an hour or two of history)
ckauhaus has quit [(Quit: Leaving.)]
taktoa has quit [(Remote host closed the connection)]
orivej has joined joined #nixos-dev
<samueldr> pstn: can you ping me when you have 4.15 building? yes libelf will add the missing elfutils stuff, but the build fails around `AR drivers/built-in.o` for me
<samueldr> possibly I'm missing an earlier error message in the log, from parallel build, or that there is no error message
<gchristensen> I think I'd like to rename grahamcofborg now that it is sort of a thing, it feels a bit awkward to talk about it :$
_ris has joined joined #nixos-dev
<gchristensen> if anyone has recommendations, I'd love to hear them :P
michaelpj has quit [(Quit: ZNC 1.6.5 - http://znc.in)]
michaelpj has joined joined #nixos-dev
<LnL> why not keep it? :)
<gchristensen> well I picked grahamcofborg when it wasn't anything but a hack, and now it feels self-centered :P
<vcunat> I'm not sure if that matters at all
<vcunat> most of us use Linux anyway
<gchristensen> LOL
<gchristensen> it'd be fun to pick a cute name like Bors
<pstn> samueldr: Do you have your stuff pushed somwhere? I'd like to have a look at how you added it.
<samueldr> it's not a clean thing, it's in an overlay for a kernel fork, with cherrytrail support, but I did test using an upstream revision, ensuring the issue happened there too
<pstn> Ah, alright
_ris has quit [(Remote host closed the connection)]
_ris has joined joined #nixos-dev
mbrgm has quit [(Quit: ZNC 1.6.5 - http://znc.in)]
mbrgm has joined joined #nixos-dev
orivej has quit [(Ping timeout: 260 seconds)]
<domenkozar> gchristensen: I'd name it snowflakesborg so I'd keep what we have
<gchristensen> haha
<MichaelRaskin> Avalanche?
<domenkozar> nofalsepositivesbot
<domenkozar> evaluatedammit
<domenkozar> ok I'll stop
<vcunat> If you want to choose from Pluto's moons again, I think Styx isn't taken yet.
<domenkozar> it is
<vcunat> bad luck
<vcunat> Kerberos would be confusing, too.
<domenkozar> I know all Pluto's moons
<domenkozar> what have you done :D
<vcunat> Maybe some haven't been discovered yet.
<vcunat> But probably not large enough to be called moons anymore.
<domenkozar> should have picked saturn, we'd never run out of projects
<domenkozar> it has 62 moons
<gchristensen> a friend suggests something around "leafcutter": "Next to humans, leafcutter ants form the largest and most complex animal societies on Earth."
<vcunat> (Our Nix started before the moon of the same name was dicovered.)
<pstn> Is 4.15-rc1 versionAtLeast 4.15?
<gchristensen> that explains Chcaron (nixops) https://en.wikipedia.org/wiki/Charon_(moon)
<vcunat> pstn: yes, nix will order that even after 4.15
<MichaelRaskin> domenkozar: as someone who have chosen Saturn for the same reason (for local-scope names), I would advise against Saturn for global names.
<vcunat> :-)
<domenkozar> that's why we picked pluto? :D
<MichaelRaskin> And ran out of names immediately.
<vcunat> MichaelRaskin: what was wrong with Saturn's moons.
<MichaelRaskin> vcunat: nothing for local scope.
<vcunat> and for global one?
<gchristensen> I assume they're all taken
<MichaelRaskin> vcunat: doesn't every one has a VM called tethys somewhere?
<vcunat> I don't.
<vcunat> So now you use hashes, like for your GitHub username?
<vcunat> Going (pseudo)random is probably the best way of avoiding collisions on global uncoordinated scope.
<gchristensen> for people really in to FP, is there some sort of combinator that could describe merging PRs?
<MichaelRaskin> vcunat: well, when I needed a name, it turned out I can pick two words that make sense in context and are not well-known together.
<MichaelRaskin> gchristensen: have you read approximately entire design documentation of Darcs?
<MichaelRaskin> (I guess Pijul is fine, too)
<vcunat> heh, thought of Darcs as well :-)
<gchristensen> hahaha no I haven't, but I'm thinking maybe some FP-ey term might be a cute name
<vcunat> but it doesn't do a real merge
<vcunat> more like a rebase
<vcunat> (IIRC)
<MichaelRaskin> There is no such thing as a real merge.
<vcunat> I don't expect Pijul changed that, but I don't know.
<vcunat> I'd hope for non-linear history at least.
<MichaelRaskin> That exists even in SVN
<vcunat> (Not sure what "real merge" should mean anyway.)
<gchristensen> @prcombinator
infinisil has quit [(Quit: ZNC 1.6.5 - http://znc.in)]
<MichaelRaskin> vcunat: history is one thing; calculating a state combining the changes from some operations is a different thing.
infinisil has joined joined #nixos-dev
<vcunat> yes
vcunat has quit [(Quit: Leaving.)]
ma27 has quit [(Ping timeout: 264 seconds)]
phreedom has quit [(Ping timeout: 276 seconds)]
phreedom has joined joined #nixos-dev
<pstn> This is what I've got so far: https://github.com/pstn/nixpkgs/commit/57eea1f747f07dc43bf9f1b0ab431c01c9b8127b It breaks because nix wants to mkdir the config file and breaks because it isn't a directory. Anybody know where that is coming from?