<jtojnar> gchristensen: testing patched daps.nix, it misses docbook_xsl (docbook5_xsl = docbook_xsl_ns)
<gchristensen> oh?
<gchristensen> oh one sec
<gchristensen> oh I don't know
<gchristensen> it works for me? `git pull` then run `daps -d ./test/DC-nixos-docs html`
<jtojnar> you manually set the docbook4 to docbook5 prefix
<jtojnar> nevermind
<jtojnar> the duplicate was actually confusing it
<gchristensen> I do?
<gchristensen> oh
<gchristensen> I get the impression you grok XML
<jtojnar> not really
<jtojnar> I did some digging when working on https://github.com/NixOS/nixpkgs/pull/30457
<gchristensen> ah
<gchristensen> well I'd be super happy to receive your PRs :P
<jtojnar> the main problem is xmlcatalog does not support XML_CATALOG_FILES despite it being mentioned in its manpage
<gchristensen> nice
<jtojnar> it is ugliness
<gchristensen> :)
<jtojnar> the best solution would be to patch libxml2
<gchristensen> it has been a real struggle to make this work
<jtojnar> but apps would never use it
Sonarpulse has quit [(Ping timeout: 255 seconds)]
<jtojnar> while patching autoconf, I was wondering if there is worse language than m4
<jtojnar> now I am patching bash
<gchristensen> ha
<gchristensen> wow!
<jtojnar> should I open a PR with just the docbook5?
<gchristensen> I'll have to look in the morning, sorry, I'm a bit sick tonight
<jtojnar> as for root_catalog.patch, the second half can probably be upstreamed with little cleanup, the autoconf part is just too ugly, though
<jtojnar> gchristensen: fixed the SVG catalog
ris has quit [(Ping timeout: 248 seconds)]
<jtojnar> I have created an upstream issue
orivej has quit [(Read error: Connection reset by peer)]
orivej has joined joined #nixos-dev
phreedom has joined joined #nixos-dev
mbrgm has quit [(Ping timeout: 260 seconds)]
mbrgm has joined joined #nixos-dev
<jtojnar> gchristensen: Also opened libxml2 bug https://bugzilla.gnome.org/show_bug.cgi?id=790746
<jtojnar> it would allow us to clean up the patches at least
vcunat has joined joined #nixos-dev
vcunat has quit [(Client Quit)]
ma27 has joined joined #nixos-dev
ma27 has quit [(Ping timeout: 255 seconds)]
vcunat has joined joined #nixos-dev
orivej has quit [(Ping timeout: 248 seconds)]
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
orivej has joined joined #nixos-dev
phreedom has joined joined #nixos-dev
<orivej> this is still relevant: all remaining nixpkgs:staging:*.x86_64-linux builds at https://hydra.nixos.org/machines are hung. may you cancel them?
<orivej> vcunat: ^
orivej has quit [(Ping timeout: 240 seconds)]
orivej has joined joined #nixos-dev
<vcunat> One build step is reportedly running for 26 days.
<vcunat> I think these long-term hangs only started appearing recently.
<vcunat> Previously it seemed that Hydra was time-outing them all properly.
<vcunat> I cancelled steps running around day or more, where I had rights (nixos and nixpkgs projects).
<vcunat> Some disappeared from the list, but most didn't.
FRidh has joined joined #nixos-dev
<LnL> yeah, the macs had a similar problem a week or so ago
_ts_ has joined joined #nixos-dev
<vcunat> I'm afraid that the remaining 3.8k x86_64-linux jobs in that evaluation won't continue, ever.
<fpletz> vcunat: we're also seeing this on our private hydra instance, looks like a recent hydra upstream change
<fpletz> restarting hydra-queue-runner fixes the issue temporarily, though
<fpletz> niksnut: ping :)
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
<domenkozar> sigh
<domenkozar> determinism is really hard
<domenkozar> that's one hell of a heisenbug
<domenkozar> fpletz: I just restart hydra-queue-runner every 1h
<domenkozar> due to many bugs like that :)
<domenkozar> I like not to be bothered, hehh
<vcunat> :-D
<vcunat> We already had at least one error that depended on hash in the $out string.
<vcunat> Such hacky pattern matches are evil.
<fpletz> domenkozar: thanks :)
<fpletz> ah, sorry, misunderstood
<fpletz> domenkozar: but that's not ideal either because builds that take longer than 1h never succeed :)
<domenkozar> yeah I have quick builds
<domenkozar> but just restarting once per day would do
<fpletz> yup
<vcunat> +1, for now
<Mic92> zimbatm: cargo finally supports vendored git respositories: https://blog.rust-lang.org/2017/11/22/Rust-1.22.html
FRidh has quit [(Quit: Konversation terminated!)]
FRidh has joined joined #nixos-dev
<zimbatm> nice!
<zimbatm> time to upgrade :)
<MichaelRaskin> ni
fpletz has quit [(Ping timeout: 264 seconds)]
srhb has joined joined #nixos-dev
fpletz has joined joined #nixos-dev
<srhb> Hi! I'm looking to apply for merge rights. I've done mostly small driveby contributions, but I've begun taking over maintainership on some smaller modules, and I think I'm a responsible and cautious person with regards to NixOS. :-)
<gchristensen> cc domenkozar ^ can you give srhb and jtojnar commit bit? :)
bkchr has joined joined #nixos-dev
phreedom has joined joined #nixos-dev
fpletz has quit [(Ping timeout: 240 seconds)]
fpletz has joined joined #nixos-dev
rsa has joined joined #nixos-dev
<fpletz> yeah, also in favour of giving srhb & jtojnar push access :)
fpletz has quit [(Changing host)]
fpletz has joined joined #nixos-dev
<orivej> I also nominate adisbladis, if he wants to.
<gchristensen> oh yeah
<MichaelRaskin> Or the vanity script could be run to see if someone got forgotten.
<adisbladis> orivej: I'd love to :)
<fpletz> ack! :)
<gchristensen> heads up y'all: @grahamcofborg can take another command, "eval", to re-trigger evals. editing a PR description will no longer trigger a new eval check. please see: https://github.com/grahamc/ofborg#commands
ma27 has joined joined #nixos-dev
<gchristensen> another problem to solve is getting more workers for the eval checks, that is often bottlenecked
vcunat has quit [(Ping timeout: 246 seconds)]
<Mic92> gchristensen: how can I see, it this was a success? https://github.com/NixOS/nixpkgs/pull/27513#issuecomment-346621671
<gchristensen> unfortunately you can't :( _I_ can, by looking at the log and confirming the job was put in the queue
<gchristensen> let me see if I can figure out an easy thing to do
<gchristensen> ideally I'd have more runners on the eval checker so it would immediately pick it up and start
<gchristensen> Mic92: oops, I meant to link you to https://github.com/NixOS/nixpkgs/pull/27513#issuecomment-346621671
<Mic92> gchristensen: I was already confused :)
<gchristensen> zimbatm: are you around to fix the eval issue from the inginious commit?
<zimbatm> my commit introduces an eval issue O_O
<zimbatm> ?
<domenkozar> gchristensen: could we get to eval commits to branches as well? :)
<gchristensen> zimbatm: when calling nix-instantiate ./nixos/release.nix -A options
<gchristensen> domenkozar: on all commits? hmm I'd need to scale my evaluator :P but ... yes?
<zimbatm> well it's marked as broken, which is intended
<zimbatm> shouldn't the bot ignore the broken packages?
<gchristensen> the issue is we can't make options
<gchristensen> so we can't release
<zimbatm> hmm, can modules be marked as broken as well?
<zimbatm> damn, looks like I will have to fix that package :/
<gchristensen> I don't know, this is the problem: default = "${inginious}/lib/python2.7/site-packages/inginious/tasks";
<gchristensen> which IIRC we don't like to put drv paths in defaults?
<FRidh> won't building the manual then start depending on that store path?
<domenkozar> we have a wrapper for that
<domenkozar> example = literalExample
<gchristensen> yes, that is why the broken package broke options / eval
<gchristensen> domenkozar: what about `default`?
<domenkozar> we set it in config section
<domenkozar> if it depends on pkgs
<gchristensen> mind opening that fix PR?
<domenkozar> services.riak.package = mkDefault pkgs.riak;
<domenkozar> will do, have to finish something first
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
<gchristensen> I think I have a patch
<gchristensen> does this look right? https://github.com/NixOS/nixpkgs/pull/31973
<domenkozar> yes
* gchristensen waits for borg
<gchristensen> good timing on the `eval` command, for the failed PRs :P
<domenkozar> does it merge it to master first?
<gchristensen> yeah
<domenkozar> nice :)
goibhniu1 is now known as goibhniu
olto has joined joined #nixos-dev
shlevy has quit [(Ping timeout: 250 seconds)]
shlevy has joined joined #nixos-dev
<zimbatm> gchristensen: went down the rabbit hole https://github.com/NixOS/nixpkgs/pull/31975
<gchristensen> :o
phreedom has joined joined #nixos-dev
ma27 has quit [(Ping timeout: 255 seconds)]
orivej has quit [(Ping timeout: 240 seconds)]
Sonarpulse has joined joined #nixos-dev
<Sonarpulse> I'm trying to decide whether https://hydra.mayflower.de/build/108568 is just a random failure, or because I messed up gfortran
<gchristensen> :D
<jtojnar> I love it when I want to fix a bug and then find out it was already fixed upstream
orivej has joined joined #nixos-dev
Sonarpulse has quit [(Ping timeout: 252 seconds)]
<gchristensen> domenkozar: any thoughts on granting merge bit to adisbladis, jtojnar, srhb?
<domenkozar> sure
<gchristensen> we should probably have a celebration every time we get new commiters
<domenkozar> I have wine here, what else is missing?
<gchristensen> party hats maybe
<domenkozar> true
<domenkozar> I know what's missing
<domenkozar> mayflower office
<gchristensen> !
<MichaelRaskin> At some point there was an attempt to run vanity counter periodically, and keep track of who was invited to ask but declined.
<MichaelRaskin> Keeping track didn't work out, and I am never in the mood to try again…
<jtojnar> thanks for the invite
<jtojnar> now I am part of eight GH orgs :)
<gchristensen> showoff ;)
aminechikhaoui has quit [(Ping timeout: 260 seconds)]
aminechikhaoui has joined joined #nixos-dev
<jtojnar> well, I use it as an overflow buffer for my to-do list
ma27 has joined joined #nixos-dev
FRidh has quit [(Remote host closed the connection)]
vcunat has joined joined #nixos-dev
FRidh has joined joined #nixos-dev
orivej has quit [(Ping timeout: 248 seconds)]
<jtojnar> gchristensen: could I also get borg access?
<gchristensen> jtojnar: I don't see why not
<gchristensen> :)
<jtojnar> thanks
<gchristensen> go forth and merge lots of PRs
<jtojnar> once the GNOME 3.26 is done, I need to rename all GNOME packages to use dashes instead of underscore
<jtojnar> s
<gchristensen> nice
<jtojnar> now half uses the former and the other half latter
<jtojnar> btw what do you think about merging the gnome branch?
<gchristensen> is it ready?
<jtojnar> yes
<gchristensen> I don't see why not :)
<jtojnar> I wanted someone to review https://github.com/NixOS/nixpkgs/pull/31683
<gchristensen> not to overload him, but I'd cc vcunat on stuff like that
<adisbladis> Should I have received some kind of invite?
<vcunat> gchristensen: I was just peeking at it when you pinged me :-)
<gchristensen> oh cool :)
<gchristensen> adisbladis: I think so ... domenkozar?
FRidh has quit [(Remote host closed the connection)]
<vcunat> there are 98 members in the nixpkgs team ATM. Who will win the jackpot?
bkchr has quit [(Quit: Konversation terminated!)]
<vcunat> jtojnar: I'll do it during the weekend, most likely
<gchristensen> gotta go
<vcunat> the current staging will go to master first anyway
<vcunat> (not meant as reaction to Graham)
<jtojnar> okay, let's wait with gnome
<vcunat> If GNOME is ready, let's merge those two at the same moment to staging, for the next merge cycle.
<vcunat> The reactions seemed to suggest that the state might be significantly better than the current one.
<vcunat> GNOME has been a bit undermaintained in a period before jtojnar picked it up.
<vcunat> great
<LnL> staging should be good to go
<jtojnar> vcunat there is also https://github.com/NixOS/nixpkgs/pull/31453
<LnL> the darwin builds even caught up somehow
<vcunat> Only those 3.8k x86_64-linux build are stuck, probably forever.
<LnL> oh :/
<vcunat> Or until someone restarts the queue-runner.
<jtojnar> both are also contained in the gnome branch
<vcunat> I haven't really done anything with meson yet.
<vcunat> (I'm actually willing to invest significant time into meson, though probably this weekend already.)
<vcunat> *not* this weekend...
<jtojnar> well the meson thing works for now
<jtojnar> we can always change it when we find a better way
<vcunat> well, almost no other package uses it now, I guess :-)
<vcunat> so it should be safe, at least in the short term
<jtojnar> signifciant fraction of GNOME does
<jtojnar> since 3.26
<jtojnar> :)
<vcunat> and systemd will soon have to
<vcunat> (AFAIK it's in short transition period where both ways are supported and we don't build it with meson in nixpkgs yet)
vcunat1 has joined joined #nixos-dev
vcunat has quit [(Ping timeout: 240 seconds)]
vcunat1 has quit [(Client Quit)]
vcunat has joined joined #nixos-dev
<jtojnar> vcunat: do you think it is okay to add gnome3.gsettings_desktop_schemas as gtk dependency?
<vcunat> build-time-only? seems OK.
<jtojnar> vcunat as a propagatedBuildInput
<vcunat> well, yes, that's build-time only
<vcunat> (i.e. only reachable from $dev output)
<vcunat> the dependency on gnome-backgrounds seems a little weird, though
<jtojnar> so a derivation is only added to the runtime closure when the path can be grepped in the package?
<vcunat> 15MB of images seem a bit strange to justify as a build helper
<vcunat> jtojnar: the notion of runtime closure is defined by mutual references
<vcunat> (of the hash-parts, those after /nix/store/)
<vcunat> It doesn't always work, like for *.jar but it's surprisingly good in practice.
<jtojnar> so if I understand it correctly the wrapGAppsHook will then add it to the runtime closure of packages depending on gtk3 but gtk3 itself will be free?
goibhniu1 has joined joined #nixos-dev
<vcunat> well, the point is that the gtk3 build creates several "outputs"
<vcunat> but only the one with libraries remains in most closures
goibhniu has quit [(Ping timeout: 264 seconds)]
<vcunat> $dev will typically only be used during builds
<vcunat> (but some derivations do "misbehave" and keep a reference to $dev outputs)
<jtojnar> yes, but if I add the schemas to propagatedBuildInputs, it will be stored to nix-support/propagated-build-inputs
<jtojnar> from there added to buildInputs of packages depending on gtk3
<jtojnar> and there picked up by wrapGAppsHook
<jtojnar> the backgrounds are needed by one of the schemas to get the path to the default background, there is an issue about it https://github.com/NixOS/nixpkgs/issues/29766
olto has quit [(Quit: hasta luego)]
<jtojnar> If we do not want to add backgrounds to every GTK application we could split the schemas package (but that will probably be nasty)
<jtojnar> or we could eschew the default backgrounds, since they are replaced anyway by the nixos module
<jtojnar> vcunat: and now I am really confused by nativeBuildInputs
<jtojnar> if the mutual reference is what decides on inclusion to the closure
taktoa has quit [(Remote host closed the connection)]
<jtojnar> s/closure/runtime closure/
<vcunat> jtojnar: you don't need to distinguish between native and non-native inputs
<vcunat> as long as you don't want to cross-compile
<jtojnar> I keep moving the build tools like meson, ninja, gobjectIntrospection to nativeBuildInputs
<vcunat> "(non)native" is much more about whether it should be run by the builder or the target system, which matters e.g. if they have different architectures
<vcunat> yes, correct
<vcunat> well, not for the introspection
<vcunat> most likely
<vcunat> That contains libs to be used during runtime, does it not?
<vcunat> But anyway, who is going to cross-compile gnome apps? I don't think we need to worry at this point.
<jtojnar> I meant when generating the gir files
<jtojnar> for apps that use the library, I am keeping it in buildInputs
<vcunat> OK
<vcunat> Then it's a package that might need to be in both in some cases, as it is packaged now.
<vcunat> But I haven't seen people cross-compiling such big apps anyway.
ma27 has quit [(Ping timeout: 246 seconds)]
ris has joined joined #nixos-dev
<vcunat> (for anyone iterested in our CDN)
ma27 has joined joined #nixos-dev
vcunat has quit [(Ping timeout: 264 seconds)]
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev
<sphalerite> great to see that project's still making progress!
ma27 has quit [(Ping timeout: 258 seconds)]
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev
phreedom has quit [(Quit: No Ping reply in 180 seconds.)]
phreedom has joined joined #nixos-dev
jtojnar has quit [(Remote host closed the connection)]
jtojnar has joined joined #nixos-dev