Synthetica has quit [Quit: Connection closed for inactivity]
jtojnar has quit [Ping timeout: 256 seconds]
jtojnar_ is now known as jtojnar
mbrgm has quit [Ping timeout: 268 seconds]
mbrgm has joined #nixos-dev
pie_ has quit [Ping timeout: 256 seconds]
Lisanna has quit [Quit: Lisanna]
Lisanna has joined #nixos-dev
Lisanna has quit [Client Quit]
pxc has joined #nixos-dev
orivej has joined #nixos-dev
jtojnar_ has joined #nixos-dev
jtojnar has quit [Ping timeout: 260 seconds]
jtojnar_ is now known as jtojnar
lopsided98 has quit [Ping timeout: 245 seconds]
lopsided98 has joined #nixos-dev
pxc has quit [Ping timeout: 240 seconds]
jtojnar has quit [Remote host closed the connection]
MichaelRaskin has quit [Quit: MichaelRaskin]
jtojnar has joined #nixos-dev
<makefu>
hey ho, is there a chance to stop receiving mails from hydra for certain packages? today i received like a million mails for a kernel module i maintain with "dependency failed". however these alerts are not actionable for me, same goes for the next "success" mails i will receive
obadz- has joined #nixos-dev
obadz has quit [Ping timeout: 260 seconds]
obadz- is now known as obadz
<obadz>
is staging going to be merged to 18.03 at some point—there are a bunch of version bumps in there (cc vcunat)
<sphalerite>
Surely this gcc breakage shouldn't have made it into master
ma27 has joined #nixos-dev
__Sander__ has joined #nixos-dev
<shlevy>
sphalerite: which breakage?
<sphalerite>
shlevy: gcc is apparently broken which is causing hydra to spam basically all the maintainers because all of the packages are getting failed dependencies
<sphalerite>
But yeah I got an email for each package I maintain about this
<shlevy>
So that's why it made it through :)
<sphalerite>
is staging not built for aarch64?
<shlevy>
Erm
<shlevy>
I don't even see any failure in that gcc log
<shlevy>
Going to restart the gcc build
<shlevy>
sphalerite: Not sure, but I don't think it's a blocker either way.
<sphalerite>
breaking the world on aarch64 maybe should be a blocker?
pie_ has quit [Ping timeout: 256 seconds]
<shlevy>
I think that's only reasonable if some devs with access to aarch64 boxes are willing to commit to debugging failures. Similar to what we have for darwin.
<shlevy>
I have no realistic way of fixing most issues... Sometimes I can guess and let hydra validate, but that's only in a few cases.
<sorear>
i imagine the problem is getting people to commit time to working on the aarch64 test failure, not giving them access
<sphalerite>
Sure, but "I have no realistic way of fixing most issues... Sometimes I can guess and let hydra validate, but that's only in a few cases." at least is solved :)
<shlevy>
sphalerite: Ah, well that's better
<shlevy>
I think we can make a committment as a community or not then
<shlevy>
erm, make a committment or not as a community
<shlevy>
But I'd rather that be explicitly decided and scoped
<sphalerite>
I don't really mind that much, but what's really not great is hydra spamming like that
<sphalerite>
Also AFAIU 18.03 is supposed to support aarch64?
Jackneilll has quit [Read error: Connection reset by peer]
Jackneill has joined #nixos-dev
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-dev
jtojnar_ has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar_ has quit [Remote host closed the connection]
jtojnar has joined #nixos-dev
jtojnar has quit [Remote host closed the connection]
jtojnar has joined #nixos-dev
pie_ has joined #nixos-dev
ma27 has joined #nixos-dev
ma271 has quit [Ping timeout: 245 seconds]
FRidh has joined #nixos-dev
FRidh has quit [Remote host closed the connection]
orivej_ has quit [Ping timeout: 260 seconds]
pie_ has quit [Ping timeout: 248 seconds]
ma27 has quit [Ping timeout: 260 seconds]
ma27 has joined #nixos-dev
<gchristensen>
sorry for the bad eval failures :(
disasm has quit [Remote host closed the connection]
<genesis>
anyway, how do you get avoid to break all your qt apps with the xcb bug ?
__Sander__ has quit [Quit: Konversation terminated!]
romildo has joined #nixos-dev
sonarpulse has quit [Quit: Leaving]
sonarpulse has joined #nixos-dev
<dtz>
re:18.03--I have a few PR's fixing failures--I've tagged the ZHF issue, but unsure if I should leave open (so release team knows they need attention) or should merge when "ready" (so release team knows they're at least suitable for master)? Is there a preference here?
<gchristensen>
dtz: according to vcunat's email, merge them and backport them to 18.03, I _think_ based on the critieria in his email
<vcunat>
+1
<dtz>
aye o7! Reading that now, I didn't see that information vs the one on ZHF. Thanks!
romildo has left #nixos-dev ["Leaving"]
sonarpulse has quit [Ping timeout: 240 seconds]
sonarpulse has joined #nixos-dev
sonarpulse has quit [Remote host closed the connection]
Synthetica has quit [Quit: Connection closed for inactivity]
sonarpulse has joined #nixos-dev
sonarpulse has quit [Ping timeout: 256 seconds]
<gchristensen>
github can require signed commits now ...
<lassulus>
is slim in the default configuration.nix? not sure right now
<gchristensen>
don't think so
<lassulus>
ah its sddm and plasma5
pie__ has joined #nixos-dev
pie_ has quit [Ping timeout: 252 seconds]
<LnL>
has anybody looked at the metrics build? I suspect 18.03 will have the same issue
<sphalerit>
lassulus: it is the default display manager though so if you uncomment the xserver.enable line but none of the display manager lines you get slim
<lassulus>
yes, thats right, but most people (at least which i know) comment out both lines. but yeah, we still should switch the default display-manager
taktoa has quit [Remote host closed the connection]
<lassulus>
also: it would be cool if the configuration.nix generated by nixos-generate would more resemble the default values of each option, just to be a little bit more transparent for beginners.