<orivej>
jtojnar: re. totem, it is being built with vala plugins only for a short while; there are 3 builds on master, and 1 of them failed, so it's not rare after all
<jtojnar>
oj
<jtojnar>
*oh
<orivej>
jtojnar: re. #32296, I am going to try making gettext populate GETTEXTDATADIRS, if you not already doing this
<jtojnar>
orivej: I wonder if we do not want to use a separate hook akin to findXMLCatalogs
<jtojnar>
thanks, will try to test it but not sure if my laptop will be able to handle it
<orivej>
I will test it myself
taktoa has joined joined #nixos-dev
ma27 has joined joined #nixos-dev
ma27 has quit [(Ping timeout: 276 seconds)]
orivej has quit [(Ping timeout: 255 seconds)]
goibhniu has joined joined #nixos-dev
ckauhaus has joined joined #nixos-dev
orivej has joined joined #nixos-dev
FRidh has joined joined #nixos-dev
JosW has joined joined #nixos-dev
__Sander__ has joined joined #nixos-dev
jtojnar has quit [(Quit: jtojnar)]
jtojnar has joined joined #nixos-dev
JosW has quit [(Quit: Konversation terminated!)]
FRidh has quit [(Ping timeout: 260 seconds)]
ma27 has joined joined #nixos-dev
olto has joined joined #nixos-dev
FRidh has joined joined #nixos-dev
jtojnar has quit [(Remote host closed the connection)]
olto has quit [(Quit: hasta luego)]
yorick has joined joined #nixos-dev
FRidh has quit [(Remote host closed the connection)]
FRidh has joined joined #nixos-dev
<Profpatsch>
Sonarpulse: np, was just out of interest (a friend wanted to run gitit on a Raspi)
ma27 has quit [(Ping timeout: 255 seconds)]
vcunat has joined joined #nixos-dev
ma27 has joined joined #nixos-dev
{^_^} has joined joined #nixos-dev
{^_^} has quit [(Changing host)]
{^_^} has joined joined #nixos-dev
ma27 has quit [(Remote host closed the connection)]
ma27 has joined joined #nixos-dev
<gchristensen>
so I setup a sort of factoid thing to exercise the base of what I'm going to replace nix-gsc-io`bot with. here are the words it knows now: https://gist.github.com/grahamc/46fa51cc9adff2c0ea29d1c311e9e72a if y'all think this is silly, I haven't invested much of any time in to it yet, and it wouldn't hurt my feelings. if y'all'd like to add anything, let me know... but not with comments on that gist -- that
<gchristensen>
won't actually send me a notification. Here is an example:
<goibhniu>
I think that would be extremely useful ... I like the nick too :D
<gchristensen>
:) I originally selected `nix-build` for the nickname but MichaelRaskin pointed out overloading the term, even in cute ways, may be problematic
<goibhniu>
ah, heh
<gchristensen>
ok, also it is currently in ##nix-darwin #nixos-dev #nixos and #nixos-borg. if there are other channels I don't know about, I'd be happy to add them. I'll push source code in about 8hrs
<vcunat>
> Bug fixes to applications which, again, aren't major updates. Generally be cautious about these.
<vcunat>
I would mention that this isn't mandatory.
<vcunat>
(as I understand it now; contrary to security updates)
<goibhniu>
It occurs to me that the factoids would end up being an FAQ. I'd be inclined to point them at the relevant heading in wiki FAQ section, to make the other FAQs more discoverable.
<vcunat>
gchristensen: and we even have a nixpkgs-17.09-darwin channel, so that part is certainly wrong
<gchristensen>
lol
<gchristensen>
please feel free to send patches
<gchristensen>
or better, move these gists somewhere else
<gchristensen>
they're two links I regularly send to people when they ask questions and as noted, the factoids thing was just to exercise the base
<LnL>
I like the bot but agree that it probably shouldn't be the only place for the info :)
<LnL>
the wiki is back no?
<MoreTea>
gchristensen: what about adding this to the wiki?
<gchristensen>
by all means!
<vcunat>
I think such howto-parts could be part of the docbook documentation.
<gchristensen>
there is even a license on it to remove any doubt about if you're allowed to
<gchristensen>
and if y'all'd like to write one up, a set of guidelines on what content should be in the factoids and where it should link to, that'd be helpful for future contributors
<vcunat>
Currently the manual is primarily in a "descriptive" and not "howto" form, but both forms have their advantages and I would think it better to keep the same content in both forms close to each other.
<vcunat>
yes, there's also howto information on that link
<gchristensen>
please send exact wording and triggers to perhaps an issue on github.com/grahamc/ofborg
<gchristensen>
if you open an issue, I'll add it as a note to the gist
<vcunat>
Hmm, information is often there somewhere, but it's a bit scattered.
<gchristensen>
I wasn't ready for / anticipating this sort of feedback :o I don't really have much interest in actually maintain the triggers / content. I think all this feedback is really good and correct. I'd love it if somebody took point on making it happen. beyond that, factoids were just a simple stop along the way of my actual goals
<gchristensen>
also, the factoid component can be run on a completely different host of {^_^}, so I wouldn't mind to even quite literally hand that code off and not even run it, if that is the easiest thing to do
<MoreTea>
gchristensen: thanks for writing this in the first place :)
<MoreTea>
Great idea.
ma27 has quit [(Ping timeout: 255 seconds)]
<gchristensen>
<3
<vcunat>
Yes, I think we can just slightly adjust the gist for now. The rest were just suggestions for "future improvement" (some time, maybe).
<gchristensen>
btw, as with all the other tooling I've built, the raw events are available for anyone else who wants to build tools with the same data
<vcunat>
gchristensen: do you have a link to descriptions of what events are available?
<vcunat>
(mostly curiosity on my side, unlikely to implement such a tool very soon)
<gchristensen>
I can write that up, but right now I have every event (https://developer.github.com/v3/activity/events/types/) from the NixOS organization on GitHub (across all repos) and then each IRC message, in the format {"target": "person-or-channel", "body": "the message which was sent"}
<vcunat>
[hydra jobs] I also cancelled the staging jobs, as it was all Darwin, and many of them will get useless after master gets merged to staging. Darwin is far the worst bottle-neck for rebuilds during the last couple of weeks.
<gchristensen>
trusted people can even have {^_^} say things by sending back a message {"target": "person-or-channel", "body": "the thing to say"}
<vcunat>
gchristensen: that's certainly good-enough description for me
jtojnar has joined joined #nixos-dev
<LnL>
vcunat: did something change recently? I feel like it ok a while back
<vcunat>
LnL: perhaps it's just an unlucky combination. One thing is that there are only about six active mac slaves.
<vcunat>
And part of that is paralyzed by some build steps getting stuck for days.
<vcunat>
Also, we had some updates requiring a full darwin rebuild on both master and 17.09.
<orivej>
LnL: do you mind if I merge https://github.com/NixOS/nixpkgs/pull/32317 (remove host_zone_info)? I'm not going to test it better myself, but I'll be able to fix failures on Hydra, yet I do not expect any
<LnL>
nope, looks good :)
<LnL>
pretty unlikely that will break something and if it does that means it won't work in 10.13